Hi @eduardo,
I hope you’re well today! 🙂
Sorry if you’ve had any trouble with that. It’s a strange one for sure, seems like something is somehow hiding the divs with the cs-half class.
I can’t replicate that locally though, it seems like you could have something adding styling to your admin area that would hide those elements.
Could I ask for you to try deactivating all other plugins and letting us know how it works with that?
Thanks,
David
I have deactivated all plugins (except Akismet) and the situation is the same than before. With WP debug activated in wp-config.php, there’s no error or conflict warning.
It’s quite strange, because when the popup window starts to load, the “hidden” options are shown for an instant.
Hi @eduardo,
Thank you for your reply.
Make sure you have selected the option “Allow this sidebar to be replaced” for at least one sidebar as displayed in the following screenshot.
View post on imgur.com
Also please note we are fixing some issues reported in the current version of Custom Sidebars plugin, some of them are mentioned in the following reply.
http://wordpress.org/support/topic/problems-after-update-from-16-to-205?replies=6#post-5786340
Best Regards,
Vinod Dalvi
Thanks for your help, Vinod.
I have selected the option “Allow this sidebar to be replaced” as indicated, but the problem persists.
Anyway, I’ll wait for next releases.
Hi @eduardo,
In the meanwhile you can also use the previous stable release of the plugin that is version 1.6 by downloading it from the following page.
http://wordpress.org/plugins/custom-sidebars/developers/
Cheers,
Vinod Dalvi
I am using Custom Sidebars in two differents sites: the first one is only for tests; so, I can wait for next releases. In the second one, my personal blog, I haven’t updated Custom Sidebars to version 2.0.7. The last version which works fine is 2.0.3.
Hello, I have the same identical issue. Options are hidden and I cannot select them. I’m using WP 3.9.1 with Architecto 1.0 theme.
I’m having the same problem, WP 3.9.1 and CS 2.0.7. I can’t select any options for the custom sidebars. Also, after I select the option “Allow this sidebar to be replaced” it appears checked, but when I refresh the page it’s always unchecked, no matter how many CS options I save.
Hey there everyone, the plugin’s been updated to fix that issue with the “Allow this sidebar to be replaced” setting not saving.
Could you please update and let us know how that works for you?
Looking forward to ensuring that’s all sorted for ya! 🙂
Cheers,
David
Version 2.8 works fine, but there’s something weird with Custom Sidebars (or WordPress, or other plugins), because new version has been able to save the value of “Allow this sidebar to be replaced” checkbox only after clicking Ctrl+F5 in Google Chrome.
After forcing upgrade of /wp-admin/widgets.php page, plugin options are displayed properly, and so they can be selected and saved. A CSS issue, maybe?
I suggest to add this trick to Custom Sidebars FAQ, or investigate the issue.
Anyway, thanks for your help, David and WPMU DEV Support Staff.
Sorry for the typo. It is version 2.0.8 which works fine.
Hi @eduardo,
Could you please try using our latest Custom Sidebars released version 2.0.9 which contains many fixes?
Regards,
Vinod Dalvi
Thanks for the update, @vinod.
Everything seems to work fine in version 2.0.9, except localization. In spite of having updated the custom-sidebars-es_ES.mo file (spanish translation) in /lang subdirectory, the plugin is not translated to spanish.
There’s another thread in these forums about this issue: https://wordpress.org/support/topic/translation-via-localisation-issues. In his response, Jack Kitterhing says: “Just wanted to let you know, that the update we released today, fixes this issue.”; however, version 2.0.9 doesn’t solve the problem.
Hi @eduardo, thanks for having updated us on that and I see you’ve posted to that other thread on that particular matter.
We’ll take a look with you on that one there. 🙂
Thanks,
David
In version 2.0.9.6, everything seems to work fine, including translations.
Thanks for your help, @david.
