- This topic has 22 replies, 5 voices, and was last updated 3 years, 4 months ago by Tom.
January 19, 2016 at 5:14 am #166657Tom
I’ve recently migrated my site over from a staging site but now the Customizer won’t load unless I deactivate GP Premium. Can you think of any reason why that would happen?
Thanks in advance.January 19, 2016 at 5:26 am #166658Sven
I suppose, your problem correlates with mine…
because there is some issue with the customizer, too. Could you please have a look and confirm/decline, so we do not produce double work load for (GP-) Tom!?
Deactivating the premium plug-in: and the error is gone! But I need the Premium add-on!!!
Hope, (GP-) Tom can help us both!
Regards, SvenJanuary 19, 2016 at 5:41 am #166662Tom
Hmm yes that definitely sounds like it could be part of the same problem. I’ve deactivated Sections as I don’t use them and am still encountering the problem though.January 19, 2016 at 5:42 am #166663Sven
please have a look at my support post: error after update to 1.3.23: strpos(): empty needle in /media.php on line 1088/
I have just solved my problem, perhaps that’s a solution for you, too!?
Best regards, SvenJanuary 19, 2016 at 5:58 am #166668Tom
Thanks Sven – upon further digging I realised this seems to be a problem with wpDiscuz, so I’ve disabled it for now. Thanks for your help.January 19, 2016 at 11:12 am #166731TomLead DeveloperLead Developer
wpDiscuz is well reviewed, so that’s very weird. If you switch to a core theme (Twenty Sixteen) and only have wpDiscuz activated, does the issue persist?January 20, 2016 at 5:09 am #166905Tom
No – if I switch to 2016 with just wpDiscuz and GP premium activated it loads as normal.January 20, 2016 at 11:11 am #167005TomLead DeveloperLead DeveloperJanuary 20, 2016 at 10:46 pm #167099TomLead DeveloperLead Developer
So I activated the plugin and tried to load the Customizer.
I received this error from inside one of wpDiscuz’s files:
Uncaught TypeError: Cannot read property 'trim' of undefined
I then activated TwentySixteen and it worked.
Then I re-activated GeneratePress and the Customizer is working.
Very strange, but I do believe it’s something in the plugin.
Can you try re-activated GP and seeing if the Customizer loads after having TwentySixteen activated?October 12, 2017 at 4:28 am #401836Jay
I’m having a similar issue when trying to activate GP premium on another site. Not sure what’s causing the conflict. The customiser is working fine with the current child theme but not with GP or even Twenty Fifteen.October 12, 2017 at 9:03 am #402037TomLead DeveloperLead Developer
Have you tried deactivating your plugins one by one to test?October 12, 2017 at 11:03 am #402114Jay
Yes, I did, and still no luck I’m afraid.October 12, 2017 at 11:07 am #402119TomLead DeveloperLead DeveloperOctober 12, 2017 at 2:05 pm #402235Jay
I essentially deactivated individual plugins 1 by 1 but was unable to establish if/what plugin (if any) is preventing the customizer from loading. It’s only loading with the child theme that was originally used for the site. Both GP and Twenty Fifteens customizer’s are inaccessible. Sometimes I get a 500 error message.October 12, 2017 at 3:36 pm #402276
- You must be logged in to reply to this topic.