ibaker
Well-known member
Bummer. That means my secondary sites are devaluednoindex means google isn't supposed to index that thread so it will always show the origin as the forum/site where it was actually indexed. In your case the main site.
Bummer. That means my secondary sites are devaluednoindex means google isn't supposed to index that thread so it will always show the origin as the forum/site where it was actually indexed. In your case the main site.
You can choose what the primary nodes are, which is content original to that site, and make it so only shared forums are noindex.Bummer. That means my secondary sites are devalued
Bummer. That means my secondary sites are devalued
Hello everyone,
This is the next release of XenCentral Multisite System fixing the support for the latest version of [bd] Widget Framework.
All owners of active licenses can download the package from their Client's Area.
Thank you!
@XCentral
Hi, thanks for the update however there seems to be a bug. When clicking on a site on the Manage Domains page the result is a blank page.
XF 1.5.7 updated XenCentral Multisite System 1.6.4 to XenCentral Multisite System 1.6.5
So i have added the salt for the multi site login so i can login once, and be logged into to the other site too (and i do have mcrypt installed) but yet it doesn't work. It asks me to login on the other side regardless. Any hints as to what i can check more/verify?
Two-step verification isn't supported yet, but we are working on it and should have the fix developed soon.
Answered in the ticket as well. Please use the version from developer's website, I guess the developer just doesn't update the version on xenforo.com anymore.
Thank you!
Good to see quick responses. Thanks.
I don't understand though why you're forcing people to use the latest widget framework which is in beta and has known issues and killing support for the official release.
We have got many requests saying our product has error with Widget Framework, and they all used the newer version. We will check if it possible to implement backward-compatibility for this one and will inform you in your ticket.
Thank you!
Its a bit of a catch22. Both 2.5.9 and 2.6.0 have known issues. WF doesn't seem to be actively maintained ATM. Version 2.5 has not received any updates since 2014 and I highly doubt it will. Version 2.6 has been out since last year and most people are using that now.I don't understand though why you're forcing people to use the latest widget framework which is in beta and has known issues and killing support for the official release.
We use essential cookies to make this site work, and optional cookies to enhance your experience.