WP Version: 4.9.8
Page Builder: 2.5.1.0
Post Grid PRO: 3.3.1 and 3.3.4
Background
We have a site origin panel where we link a Post Grid Pro grid to our page.
This is working perfectly.
To setup we do the following
Pages => Target Page => The Post Grid Pro Panel (edit)
This brings up a dialog with the following
A Title
A dropdown where we can select the Post Grid Pro Grid we want to use on this page
All Good
As soon as we upgrade to 2.9.x (Page Builder) we lose the ability to change the Post Grid Pro Grid.
The Dashboard works – if we try to change the option in the dropdown the new value does not “stick”. After saving, the drop down always reverts back to “Select One” and the front end is blank.
If you update the title – that value is saved – but not the Post Grid Pro value.
Reverting back to 2.5.1.0 of Page Builder restores the functionality.
Hi Julian,
Does this issue occur if you disable the Sidebar Emulator? You can disable the Sidebar Emulator by navigating to WP AdminSettingsPage Builder. Open the General tab and untick Sidebar Emulator.
Yes that fixes it but we are still seeing this when the page loads
Notice: Undefined index: option_name in /home/domain/public_html/wp-content/plugins/siteorigin-panels/inc/sidebars-emulator.php on line 120
Hi Julian,
Sorry for the delay.
You can fix this issue by saving the page where that error message is present.
With that said, I would recommend disabling WP_DEBUG as it ideally shouldn’t be running on a production site.
Thanks Alaex,
I am not clear on your suggestion – “saving the page where that error message is present”?
As this is a siteorgin error I was hoping someone here could give us some indication of what the issue is.
Secondly, we only use WP_DEBUG in our stage environments – this is enabled so we can see any errors that might be generated by the site. We then try to fix those errors before implementing on live.
Hi Julian,
This is a SiteOrigin Page Builder specific notice. It can be avoided by saving the affected page (as it’s page specific, rather than a global issue), or by temporarily disabling the Sidebar Emulator – this notice will be moved in an upcoming update. You can disable the Sidebar Emulator by navigating to WP AdminSettingsPage Builder and open the General tab, the untick Sidebar Emulator.
I’m sorry for the misunderstanding. We typically mention this as we’ve found a number of users have WP_DEBUG enabled on a production site.
Hi Alex,
Thank you for your time on this – hopefully this will be the last post.
We had already disabled the Sidebar Emulator which fixed the original problem – however I am still not clear by what you mean by “Save the specific page” – probably missing something obvious here – in which case I apologise.
Hi Julian,
Ah, my mistake
This notice is page specific rather than a global notice. This notice appears when you view a page with SiteOrigin Page Builder enabled, specifically while the sidebar emulator is setting up. The Sidebar Emulator tries to load an id that’s generated when the page is saved and if that id isn’t saved, this notice will appear. To fix this notice, you simply need to save the page (read: the page the notice is appearing on) and that will allow for the missing widget id to be generated and stored.
If you’re seeing this notice in an error log, unfortunately, there’s no specific way to know which page this notice is related to. This notice is safe to ignore and will be removed shortly.
Thanks Alex,
I think the confusion came from the fact that the error first appeared when we saved the page.
Possibly something in the timing but I have just repeated the process and I cannot replicate so I am going to close this out.
Thank you for your time and patience – it is appreciated.