This just started appearing in the server logs from a task started by cron. Running on a centos server with php 8.0 and mysql 8.0.
All plugins are current.
[08-Sep-2021 16:05:15 UTC] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/qwerty/public_html/wp-content/plugins/so-widgets-bundle/widgets/button/button.php:433
Stack trace:
#0 /home/qwerty/public_html/wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php(172): SiteOrigin_Widget_Button_Widget->modify_instance(”)
#1 /home/qwerty/public_html/wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php(386): SiteOrigin_Widget->widget(Array, ”)
#2 /home/qwerty/public_html/wp-content/plugins/so-widgets-bundle/widgets/cta/tpl/default.php(10): SiteOrigin_Widget->sub_widget(‘SiteOrigin_Widg…’, Array, ”)
#3 /home/qwerty/public_html/wp-content/plugins/so-widgets-bundle/base/siteorigin-widget.class.php(219): include(‘/home/qwerty/…’)
#4 /home/qwerty/public_html/wp-content/plugins/siteorigin-panels/inc/widget-shortcode.php(57): SiteOrigin_Widget->widget(Array, Array)
#5 /home/qwerty/public_html/wp-includes/shortcodes.php(356): SiteOrigin_Panels_Widget_Shortcode::shortcode(Array, ‘<input type="hi…', 'siteorigin_widg…')
#6 [internal function]: do_shortcode_tag(Array)
#7 /home/qwerty/public_html/wp-includes/shortcodes.php(228): preg_replace_callback('/\[(\[?)(siteor…', 'do_shortcode_ta…', '<div id="pl-103…')
#8 /home/qwerty/public_html/wp-content/plugins/all-in-one-seo-pack-pro/app/Common/Traits/Helpers/Shortcodes.php(79): do_shortcode('doShortcodes(‘doAllowedShortcodes(‘doShortcodes(‘scanPost(Object(stdClass))
#13 /home/qwerty/public_html/wp-includes/class-wp-hook.php(303): AIOSEOPluginCommonSitemapImage->scanPosts()
#14 /home/qwerty/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(”, Array)
#15 /home/qwerty/public_html/wp-includes/plugin.php(518): WP_Hook->do_action(Array)
#16 /home/qwerty/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/actions/ActionScheduler_Action.php(22): do_action_ref_array(‘aioseo_image_si…’, Array)
#17 /home/qwerty/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(65): ActionScheduler_Action->execute()
#18 /home/qwerty/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(162): ActionScheduler_Abstract_QueueRunner->process_action(28577, ‘WP Cron’)
#19 /home/qwerty/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_QueueRunner.php(132): ActionScheduler_QueueRunner->do_batch(25, ‘WP Cron’)
#20 /home/qwerty/public_html/wp-includes/class-wp-hook.php(303): ActionScheduler_QueueRunner->run(‘WP Cron’)
#21 /home/qwerty/public_html/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(”, Array)
#22 /home/qwerty/public_html/wp-includes/plugin.php(518): WP_Hook->do_action(Array)
#23 /home/qwerty/public_html/wp-cron.php(138): do_action_ref_array(‘action_schedule…’, Array)
#24 {main}
thrown in /home/qwerty/public_html/wp-content/plugins/so-widgets-bundle/widgets/button/button.php on line 433
Hi.
I’ve had a look at the flagged line and it hasn’t been adjusted in a number of years so the cause of this issue must be specific to the cron. I have an idea of a possible fix, but I’m not able to directly confirm it due to the cause of it being quite specific. I’ve prepared you a modified version of the SiteOrigin Widgets Bundle plugin that contains a potential fix.
Before proceeding, do a backup.
Navigate to PluginsInstalled Plugins and deactivate SiteOrigin Widgets Bundle, then delete it. Scroll to the top of the page and click Add New, Upload Plugin. Upload this file and when prompted, activate SiteOrigin Widgets Bundle. Does this error still occur?
Kind regards,
Alex
Installed and everything looks ok.
Manually executed cron with no errors. I’ll check the error log again the afternoon, but so far it looks ok.
Thanks for updating it!
Hi,
That’s great to hear! :)
I’ve let the rest of the team know about this fix and submitted it for further testing.
Kind regards,
Alex