I have theme Sydney (free version by ATHEMES) activated in my WordPress site www.hamrolagi.com. Since a few days, the customization menu returns only one menu-item which is empty and the no page is loaded in the adjacent frame.
When I deactivated the siteorigin widget bundle plugin and then again open the customization menu everything works fine, and the problem appears again on activation.
Hi Prabhakar,
That sounds like you’ve reached the memory limit. You need to apply a pretty hands on fix to resolve this issue. This article would be a good read as it’ll outline how to change it. You’ll need to edit wp-config.php. If you’re unfamiliar with FTP, I would recommend asking your hosting provider for help with editing this file.
Hey Alex,
Thanks for your kind reply, but it didn’t solve the problem. I still get the same thing. I guess other (even heavier) plugins have not caused the problem since deactivating or activating doesn’t have any effect. It is just SiteOrigin Widgets Bundle. And if I have to do any customization, I will have to deactivate the plugin which completely distorts the page.
Hope to hear from you soon.
Hi Prabhakar,
To clarify, does this issue occur if only SiteOrigin Page Builder and the Siteorigin Widgets Bundle are the only active plugins with a default theme? I ask as there is no known compatibility between the plugins and both plugins are designed specifically to work together so a conflict between just those two plugins is very unlikely.
If it helps, here’s our typical plugin conflict test instructions:
Can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.
If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.
Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.
If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.
The problem occurs even if SiteOrigin Widgets Bundle is the only plugin active. And, it doesn’t occur when I use other themes, not even when I use the parent theme.
Hi Prabhakar,
Would it be possible for you to create a temporary admin account for us so we can log in and take a look?
This is a private message.
I am afraid I can’t.
Could provide any kind of assurance?
Hi Prabhakar,
Assurance? Uh, we’ve never had such a request before so I’m not too sure what I can say or do.
Unfortunately, we need to inspect your website set up to work out what is causing this issue. As you’re the only person who has reported this time of issue we have nothing to really go on. If it helps, the first thing I’ll do is run a plugin conflict test to ensure the previous tests have been run correctly.
I mean assurance regarding the use of an admin id. It is always risky to let others use it.
Hi Prabhakar,
I understood, but there’s really nothing we can offer you outside of giving you our word that we won’t. We want to resolve this issue and we have no interest in harming your website as we don’t gain anything from doing this outside of negatively impacting our reputation.
This is a private message.
Hi Prabhakar,
Thanks. Please disable CONCATENATE_SCRIPTS. This will require editing wp-config.php again.
Hey Alex,
I haven’t tried it on the live site, but when I tried it on my localhost in WAMP, it didn’t work. I even tried clearing the cache and cookies of the browser but to no help. It still shows the same customization screen.
Actually, after editing the wp-config file, the problem occurs regardless of whether the Widgets Bundle Plugin is activated or not.
Hi Prabhakar,
Thanks. That rules out SiteOrigin Widgets Bundle as the cause for this issue. I’ve run a few additional tests and this issue is an issue specific to your child theme. Something in your child theme is causing this issue. You can verify this by temporarily changing to your parent theme. I suspect it may be the PHP deferring certain scripts.
Thanks for the help, Alex. I had deferred the parsing of javascript, which was causing the problem. When I removed the code from the child theme’s functions.php, the conflict was resolved.
But is there another way to defer the parsing of Javascript, without causing the problem?
Hi Prabhakar,
Unfortunately, that’s not really something I can assist with. I would recommend using something like Autoptimzie that will handle deferring assets for you and also minify the assets.