Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Widget customizer in WP 3.9 #300

Open
szakee opened this issue Apr 17, 2014 · 4 comments
Open

Widget customizer in WP 3.9 #300

szakee opened this issue Apr 17, 2014 · 4 comments

Comments

@szakee
Copy link

szakee commented Apr 17, 2014

Hi guys!
I just tried the wp 3.9 now with my Meet-GavernWP based theme and the widget live customizer is not working for me. I added the

add_theme_support('widget-customizer');

to the base.php but nothing changed.

First, I thought something wrong with my theme, so I installed a latest version of the Meet-GavernWP 1.9.3 on a fresh and clean wordpress 3.9. But the widget customizer is still not showed up. Can you guys check this?

@dziudek
Copy link
Contributor

dziudek commented Apr 17, 2014

Hello,

We have detected the same problem, and currently we have no idea what is the problem. We will work on solution, but most probably it will be released in Meet GavernWP v.1.10 not in the upcoming Meet GavernWP 1.9.* minor update.

@szakee
Copy link
Author

szakee commented Apr 17, 2014

Ok, I understand. Thank you Tomasz!

@szakee
Copy link
Author

szakee commented Apr 17, 2014

Might be I found a possible problem. By default

.control-section[id^="accordion-section-sidebar-widgets-"], 
.customize-control-sidebar_widgets .hide-if-js, 
.customize-control-sidebar_widgets label { 
display: none;
}

and the customize-widgets.js is can't load because look like this in the gavernwp page source:
screenshot_18

that is should be:
screenshot_17

If you have a little time, please take a look for this. Thanks

@dziudek
Copy link
Contributor

dziudek commented Apr 18, 2014

In our installations we didin't detected similar problems - we are still investigation this problem. Of course solution on the github will be available much sooner than the 1.10 release :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants