- This topic has 10 replies, 3 voices, and was last updated 6 years ago by Tom.
May 7, 2015 at 1:44 pm #106431rtomc
I’m using GP (WP 4.2.2 + BuddyPress 184.108.40.206)
Just today I have boight GO-Premium.
Before use GP-premium I upload WP version to the last one: 4.2.2, and only then I tried to use my new GP Premium but then customize options do not charge.
Can be caused by the last version of WP?
Somebody it knows?
RMRMay 7, 2015 at 2:35 pm #106452TomLead DeveloperLead Developer
I’m using GP Premium with 4.2.2. with no issues.
What do you mean by them not changing? You change the option, and nothing happens at all? Does the area on the right reload but nothing is changed?
Can you link me to your site so I can take a look?
Let me know 🙂May 7, 2015 at 2:53 pm #106455rtomc
Thansk for your answer.
Now I’m sure that the last version of WP isn’t the problem because in other WP that I’ve running with GP all is ok.
I publish a screenshoot of the problem in a hide page: http://eldesvandelasletras.com/costumize-options-do-not-load/
When I go to “costumize” I can’t see the options that I need to change the header, the layout, colour, blog options, widget options… that normally are in the left column.
I tried deactivating the plugins, but I do’nt found any incompatibility.
I deleted and reinstal·let the theme… nothing.
I tried too with “FreeLAncer” theme and the situation it’s the same.
I tried with other themes and all runs perfect 🙁
RMRMay 7, 2015 at 2:58 pm #106456TomLead DeveloperLead Developer
Can you try increasing your PHP memory?: http://generatepress.com/knowledgebase/increasing-memory-limit/
Let me know – we’ll get it fixed! 🙂May 7, 2015 at 3:06 pm #106457rtomc
I tried it editing wp-confing without success
Then I sent a ticket to hosting provider.
I’ll tell you the answer
RMRMay 7, 2015 at 3:20 pm #106458TomLead DeveloperLead Developer
If you’d like you can send me a temporary admin login to firstname.lastname@example.org and I’ll take a look to see if I can see the problem 🙂May 8, 2015 at 12:50 pm #106670TomLead DeveloperLead Developer
This turned out to be a bug with the SiteOrigin Widget Bundle plugin.
When the Google maps widget is active, it causes a JS error in the Customizer.
This is happening with the core TwentyFifteen theme as well, so it’s more than likely a bug in the plugin.
Thanks!May 9, 2015 at 1:15 am #106731Greg Priday
Sorry to jump in here, but would it be possible for you to give me the JS error you’re seeing with the maps widget? I’d love to get this fixed up ASAP, but I haven’t been able to recreate the error on my side.May 9, 2015 at 7:21 am #106788TomLead DeveloperLead Developer
Here’s the error:
TypeError: f.state is not a function
How to reproduce:
1. Using TwentyFifteen (or any theme), activate PageBuilder and the Widgets bundle.
2. Enable the Google maps widget.
3. Add the widget to any widget area, and add a location into the widget.
4. Now go into the Customizer – it won’t fully load, and Firebug spits out the above error.
Let me know if you need more info 🙂May 9, 2015 at 9:34 am #106808Greg Priday
There we go, thanks a million Tom. Not sure why I couldn’t recreate that before. I’ve managed to fix this, I’ll release a hotfix update some time tomorrow.May 9, 2015 at 9:35 am #106809
- You must be logged in to reply to this topic.