Hi – The SO Widget Bundle on my site is throwing up PHP errors and causing problems when editing pages. Everything is up to date on the site, and PHP is also up to date. This has been going on for a while.
These are the kind of errors I’m seeing when I try to edit a page:
Warning Undefined array key “marker_positions” wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php:412
Plugin: so-widgets-bundle
Warning Undefined array key “custom_map_styles” wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php:412 Plugin: so-widgets-bundle
I’ve got 13 errors at the moment. I’m using Query Monitor to track what’s going wrong and it seems to be the widgets Bundle.
Any recommendations about how to fix this?
My Versions
Wordpress – 6.8.2
PHP – 8.3
SO Widgets Bundle – 1.69.2
SO Page Builder – 2.33.1
Karen
Thanks for posting your question, Karen.
To clarify what you’re seeing in Query Monitor:
– **Notices**: Minor issues, like using a variable that’s not set. They don’t break anything but flag potential code improvements.
– **Warnings**: Not errors, just a warning to the developer such as non-existent array keys (e.g., `marker_positions` or `custom_map_styles` in your case). If the widget in question is functioning normally, the issue isn’t connected to functionality in such a way as to make it noticeable.
– **Errors**: Critical problems that stop code from running, like fatal errors. You’re seeing warnings, not errors, which is why your site still works.
Let’s investigate further:
1. Open your browser’s console while editing a page in WordPress:
– On Chrome: Right-click the page, select “Inspect,” then click the “Console” tab (https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis).
– On Firefox: Right-click, select “Inspect,” then go to “Console.”
2. Look for any errors in **red text**. These might give more details about what’s going wrong with the Google Maps Widget.
3. Reply with any red-text errors or messages you see, and we’ll go from there. If you’d like send screenshots, please do so by uploading to any cloud site like Dropbox or similar and sharing the link here.
Thanks
Hi Andrew – Thanks for your reply.
I’m getting the same errors no matter which page I am editing. I have uploaded screenshots to DropBox. It looks like I have one warning and six errors. They are the same for any page.
https://www.dropbox.com/scl/fo/xg44o8raucivv1xk3mnt7/AC8MSPqgjixYphS_pTROers?rlkey=toochho4c1ibmfdtgzoea6066&st=5mkijtd4&dl=0
Karen
Thanks. The browser console shows no errors or warnings relating to SiteOrigin.
To confirm; SiteOrigin Widgets and Page Builder are functioning normally on the front-end and in the site admin?
Hi Andrew – Ok, thanks for the reply. The Page Builder isn’t functioning reliably when making edits.
I just went in to quickly make a minor edit in one of the SiteOriginEditor blocks, and when I update, I get a Critical Error Warning. This is a recurring issue. (see other screenshot). https://www.dropbox.com/scl/fi/qh462ow7eim6t5xmffhpo/Screenshot-2025-08-08-at-12.27.25.png?rlkey=yi1tj6p0zfnl58tzkv4nocija&st=zbt6s75b&dl=0
Karen
The site is displaying correctly from the front end
Thanks. If you have access to your Hosting File Manager or a FTP app you can adjust your WordPress debug settings to find out what that PHP error is. Here is how Page: Debugging in WordPress. Without the debug log it’s hard to know what the problem is.
Thanks for the warnings report. A fix has been submitted for review https://github.com/siteorigin/so-widgets-bundle/pull/2240. Once approved, the fix will be included in the following Widgets Bundle release.
The critical error screenshot will ideally need to be investigated via the WordPress debug.log file. If any steps in the above link aren’t clear, please let me know and I’ll try to lend a hand from there.
Ok will see what I can find.
General question about the warnings that were shown. Do those get fixed in the next release?
In the next release most likely. Once the GitHub issue linked above has been changed to a merge status, the next release after that.
OK thanks so much for your help Andrew. I'll come back to you if I need more help.
Sounds good. The debug log will explain the error if you activate debugging and recreate the critical error: Page: Debugging in WordPress.