Started encountering an issue with saving widgets, changes made are not saved and the following message is shown at the top of the widget:
There is a newer version of this widget’s content available.
Clicking Restore will replace the current widget contents. You can revert by refreshing the page before updating.
The plugins that were updated were:
Thanks for reaching out.
When able, please, try running a quick plugin conflict test. Does the issue persist if you temporarily deactivate all plugins except for the Widgets Bundle and Page Builder?
Hi Andrew, thank you for your reply.
I’ve tried uninstalling all plugins apart from Page Builder by SiteOrigin and SiteOrigin Widgets Bundle and found that the problem is my custom plugin where I create my widgets.
The versions I am using are 2.15.3 & 1.26.1 respectively.
However if I revert my repo back to before I ran plugin updates then the problem goes away, so this seems to be related to be updating to those, the versions I am reverting back to are 2.15.0 & 1.26.0 respectively.
Has something changed which now makes my custom plugin break? Any suggestions for what I could try welcome.
Glad to hear you’re making progress.
When the issue occurs, please, try checking the console in your browser for any errors. It’s also worth checking PHP error logs to see if anything noteworthy is being printed there.
Checking for console errors:
PHP error logs:
This error is showing in the console when I open a widget for editing:
siteorigin-panels.min.js?ver=2.15.3:8 Uncaught TypeError: Cannot read properties of undefined (reading ‘disable_widget’)
And when loading a page the PHP logs show:
Notice: wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the case-studies-listing handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /var/www/wp-includes/functions.php on line 5663
I’ve had a look at the provided information and over the reported lines, and I’m having trouble identifying a possible cause. Can you please provide me with a copy of the custom widget you’re using? This will allow me to identify what line in the custom widget is specifically linked to this issue and that’ll allow me to identify this issue is.
WeTransfer.com, Dropbox, Drive, any similar service can be used. Thanks.
Hi again, thanks for this.
I have uploaded the custom plugin here -> https://file.io/SMRevgB6Mhdo
The problematic widget seems to be case_study_listing.
Thanks. I’ve run a few tests with the provided plugin and I’m having trouble replicating this. Can you please send me an export of a page where this issue is occurring? This will allow me to test against the widget using values that have resulted in this error so it should make it quite easy. To export a page, open up the page in the editor and click the Layout button in the Page Builder toolbar. Click import/export and then click download. Please upload the export to a 3rd party file hosting site such as WeTransfer (no email is required).
Are you able to replicate this issue on a different website?
I have exported one of the pages here -> https://we.tl/t-Gk3GwC2u0p
Bear in mind this error occurs when creating a new page also, I have replicated the problem on 2 separate environments with the same site, but I haven’t tried using the custom plugin on a different site, I’ll give this a go now.
Thanks. The provided layout doesn’t contain the case_study_listing widget. Can you please clarify which widget is facing this issue in the provided layout? I’ve run a few tests and haven’t been able to replicate this issue with any of the widgets in the provided layout. It’s possible I need to test a specific widget more heavily to cause this issue.
Let me know how you go mate. :)
We can discount the PHP error, sorry about this, it was unrelated to this issue it just appeared to be connected.
I’m looking into the JS error as this is persisting and happens when any widget is opened, and doesn’t occur with the older versions of the plugin, so I think this could be related.
It looks like this new ‘disable_widget’ was added to siteorigin-panels.js in the update I ran FYI.
The line you’re referring to was introduced in 2.15.0 but a minor change made in 2.15.3 could potentially result in an issue. I’ve been unable to replicate this error, but I’ve identified an additional check that may help. I’ve prepared a build for you to try. You can download it by clicking here.
Before proceeding, do a backup.
Navigate to PluginsInstalled Plugins and deactivate Page Builder by SiteOrigin, and then delete Page Builder by SIteOrigin. Scroll to the top of the page and click Add New, Upload Plugin and upload siteorigin-panels.2.15.4-beta.zip. When prompted, activate Page Builder by SiteOrigin.
Hi Alex, thanks for your help on this.
You have fixed the issue, the plugin is now working correctly and edits can be made.
Much appreciated sir
Great to hear that helped! The provided fix will be included in the next WordPress update. :)
Please feel free to post a new thread if anything else comes up.