Over the last few days, I’ve tried to edit the SiteOrigin Hero widget I have on my homepage and it is not working. When the widget is open each slide is labeled as “Frame” which is not how they are typically named and I cannot open any of the slides or tabs to update or edit anything.
All the plugins are updated, so I’m not sure how to figure out what the issue is.
SiteOrigin Hero Widget on Homepage not Editable
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi Molly
It sounds like there is an error on the page. When you have a moment, please try checking for a plugin conflict. Temporarily deactivate all plugins except for Page Builder and the Widgets Bundle. Does the issue persist?
Hi Andrew,
When I deactivated all other plugins except for Page Builder and the Widgets Bundle, the issue was solved, and the Hero widget was functional. However, when I reactivated all of the other plugins the issue returned. What would be the next step to resolve this issue without having to deactivate other plugins that the website is using?
Hi, that’s good news. The next step would be to reactivate your plugins either one by one or in groups to isolate when the issue reoccurs with the final test being Page Builder, the Widgets Bundle and the issue plugin activated to confirm the conflict.
Hi, the problem appears to be with this plugin “Google Analytics Dashboard for WP (GADWP)”. When this one is activated it causes the Hero widget to break. I reactivated all other widgets except this one and the Hero widget is functional. How do I resolve the conflict with the Google Analytics plugin?
To confirm, the issue occurs with only the following plugins activated:
SiteOrigin Widgets Bundle
SiteOrigin Page Builder
Google Analytics Dashboard for WP (GADWP)
If so, you can try checking your console for an error in red text. Any distinct error would be useful when reporting the issue to the conflicting author.
https://developer.wordpress.org/advanced-administration/debug/debug-javascript/
Correct. I just submitted the issue to their support team, so hopefully they’ll be able to help resolve the issue on their end.