Hi Alex
Thanks for reporting this warning; we’ll resolve it in the next update. In the meantime, you can set WP_DEBUG to false in your WordPress wp-config.php file. Alternatively, you can add:
define( 'WP_DEBUG_DISPLAY', false );
Plugin Contributor
alexgso
(@alexgso)
Hi Alex,
This type of error is related to a third-party plugin and we’ve come up with a possible fix for you to try. You can download it by clicking here.
Before proceeding, do a backup.
Navigate to Plugins > Installed Plugins and deactivate SiteOrigin Widgets Bundle. Delete it and then scroll to the top of the page and click Add New, Upload Plugin. Upload so-widgets-bundle.1.35.2-beta.zip and when prompted, activate it.
Kind regards,
Alex
I UNINSTALLED THE OLD PLUGIN BY INSERTING THE BETA
so-widgets-bundle.1.35.2-beta.zip
THE ERROR HAS MOVED BUT REMAINS
Warning: Undefined array key “1” in /web/htdocs/www.site.it/home/wp-content/plugins/so-widgets-bundle/so-widgets-bundle.php on line 844
I tried to deactivate all plugins except ‘ESTATIK’ which is the main one and makes it a strong point of your plugin
The mistake remains, greetings and thanks for what you do
I have tested,
define (‘WP_ALLOW_REPAIR’, ‘false’);
Unfortunately it doesn’t fix it, it only fixes by moving to an old PHP 7.4 configuration
Greetings and many thanks
Following the error and modifying the following lines on PHP 8.1 The error disappears
844 Before if ( empty( $widget_object ) || ! $widget_object->has_form( ‘settings’ ) ) {
844 After if ( empty( $widget_object ) || $widget_object->has_form( ‘settings’ ) ) {
1685 Before if ( ! empty( $num_match ) && isset( $num_match[1] ) ) {
1685 After if ( empty( $num_match ) && isset( $num_match[1] ) ) {
Of course I don’t know if it affects other code, I hope I’ve been of some help
Plugin Contributor
alexgso
(@alexgso)
Hi Alex,
Thanks for trying.
I tried to deactivate all plugins except ‘ESTATIK’
Due to that being the only third-party plugin not being disabled during the test and the issue still occurring it points to that plugin as introducing the widget experiencing this issue. There’s an older less supported way of adding widgets in WordPress that technically still works (it’s very much no longer supported) but it’s quite prone to issues. If that plugin is using that method it would explain why this notice is occurring. To confirm, is this the correct plugin?
Unfourtantly, the suggested edits will greatly negatively affect compatibility with third-party widgets in general so I don’t recommend using them.
Kind regards,
Alex
Yes the plugin is this, but I use the paid Pro version so I bought it, I also submitted to them these threads that we are compiling inviting them to follow them also because they support the substance on the siteorigin plugin, I hope I have been of help.
Thank you and greetings.
