a2034487

Same here: lots of sites, upto 85% of them, disconnecting when synchronising. Also downgraded to get things back to normal again. Client upgrade to 4.4.1.2 we’ll keep, problems appears to be in the dashboard

Hi Kris,

thanks for asking. All is working, we believed it was due to your plugin but we had a firewall issue amongst our servers, resulting in sites being unreachable.

Kind regards,
John

Hi,

I’ve uploaded the plugin 2.8.2, and tried export from one site and import into another site again. It doesn’t work yet, sorry.

The export-file contains the correct value for $label_username, but for some reason it’s not imported into the new site. After import it still shows the default ‘Username or email-address’ instead of the value of the export file

The same for the export and import of the login screen background.

We’re using a background image that is stored on a central domain name :
for example : https://www.central.com/background-image.jpg
On the website where it’s added manually (via From URL) it is correctly.
So on site1.com the field Background Image shows the full url as it should : https://www.central.com/background-image.jpg
On site2.com, where we are importing the settings file, this is replaced by the local URL : https://www.site2.com/background-image.jpg.

And because this image is stored locally, and not on each domain, it doesn’t exist on the new domain.
So the domain-name part of the full url in the export file is replaced by the domain-name of the target site instead of leaving it untouched.

Hope this makes it clear for you,

Thanks

And a 2nd question please: As Background Image we’re using ‘From URL’, so not from the Media Library. That way we can use a centrally stored background image on various sites. So the image is stored on one domain, and is called in the various other domains where we have WP sites using your plugin.
When using the Import function to correctly set all the settings, this URL isn’t imported correctly. Instead of placing the full URL in the Background Image box, the domainname (of the central domain where the image is stored) is replaced by the domainname where the WordPress site is installed.

Hope you have a moment to get back about this,

Thanks in advance,
John

“Can someone please help me test it in advance?”
We’re all testing in advance at the moment :-O

The 2.05 can, amongst others, be found here :
https://nhulieu.com/p/201406/huong-dan-display-widgets-ban-2-05.html?lang=en

May not be the only source, but at least it works.

Here too, nothing visible anymore… back to the old version that worked without problems. Sometimes those 200.00 users may not be well served with new stuff that doesn’t work :-S

True, we also installed the new version and can’t find stuff anymore in the user interface. If it’s not broken, no need to fix it.

Let’s conclude: what a mess… we’re staying on the 2.05 (no need for slow sites, huge plugins and tracking us), and hopefully the ‘old’ owners will somehow get this under control again…

Still nothing ??

I think it’s related to the most recent upgrade of WordPress itself… this theme usually crashes whenever there is a WordPress upgrade ??

We’ve had the same issue (error 500) on several sites that don’t use this plugin. We restored the sites from backup, and added more rights to the public_html directory. Apparently the update needs to write one or more files.

I’m using Striking theme, also not visible here… Same solution: switching to twenty-twelve helps, and then switching back.

This happened already a few times before… be VERY Carefull when updating this plugin, it might just stop working (grey squares). Support apparently is then limited to ‘go update some other plugins’…

Perhaps best to move away from this plugin

Happened here too… after I installed an admin theme and deactivated it again.

Solved it by deleting admin user and creating another…