Last update error

Hi Alex

Thanks for reaching out. Looking at the last reply from Alex here https://www.ads-software.com/support/topic/php-8-0-8-1-version/, it sounds like the warning relates to a widget on the page not authored by SiteOrigin. Were you able to set WP_DEBUG to false in your WordPress wp-config.php file?

Thanks Andrea Misplon
yes I did it without success, but accurate, as per the previous post!
https://www.ads-software.com/support/topic/php-8-0-8-1-version/
that by applying the following change, everything works, including the widgets why?
The error also disappears on PHP 8 | 8.1`

————————————————————————————–

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

————————————————————————————-

Thanks for trying.

Notices, warnings, or errors shouldn’t be printed on the front end of a live, non-development site. Please, try asking your hosting company if they can please disable PHP error reporting.

Is this the plugin involved? https://www.ads-software.com/plugins/estatik/.

It appears as though the above plugin is using an older less supported way of adding widgets in WordPress that technically still works (it’s very much no longer supported), but it’s pretty prone to issues.

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.

Hi Andrew and Alex,

It appears as though the above plugin is using an older less supported way of adding widgets in WordPress that technically still works (it’s very much no longer supported), but it’s pretty prone to issues.

@misplon Could you please show us where can you see “the older less supported way of adding widgets in WordPress” – so we could fix that?

And how did changing the php version solve this problem then? ??

Thank you.

it is very simple to pass the modified file to you with a personal download.
Download> https://www.apdigital.it/Mod%20Alex%20-%20so-widgets-bundle.zip
Edit Lines > >

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`

Excuse me https: //

it is very simple to pass the modified file to you with a personal download.
Download> https://www.apdigital.it/Mod%20Alex%20-%20so-widgets-bundle.zip
Edit Lines > >

Hi alexbyby,

I do not recommend using the modified files you’ve made as that can and will cause compatibility issues with certain third party widgets.

Could you please show us where can you see “the older less supported way of adding widgets in WordPress” – so we could fix that?

That was initially said in a different thread made by Alex and Andrew was providing a summary of that thread in the new thread. It was said prior to be aware of the specific plugin being used and was suggested as a hypothetical. I’m currently doing an analysis of your plugin to identify the direct cause of this issue and should have more information soon. It’s going to take a little bit to identify it directly so I don’t currently have a direct answer.

Kind regards,
Alex

RE: Alexgso
I thank you for the advice not to modify the Plugin files but when the error is constant you have to repair yourself, better than the error on the screen is
However today 22 June 2022 I received the new update the error continues.
I also continue with my modification until the error disappears
Please note:
I personally outside of this error have no other errors on any service widgets, everything seems to work

Hi Alex,

Can you please confirm which Estatik widget you’re using on the page this issue is warning on? I’ve done some general testing of the free plugin and I haven’t been able to replicate the notice so I suspect it might be a premium widget. I will however note that the hypothetical I mentioned previously is not the case and the widgets are set up using more modern methods of setting up methods.

Unfortunately, while the fix works for you and your setup it will cause issues for other users so we’re not able to use the suggested fix. To move forward we really need to replicate the warning as that’ll allow us to identify a fix that won’t break compatibility for other users.

I strongly recommend reaching out to your hosting provider about disabling error output on your website. Not only for this warning but other warnings, notices and errors in general.

Kind regards,
Alex

The error is in the screenshot is clear!
I have also replicated a new solution with your latest update, see Screenshot.
The error is replicated in line 843
Correction to line 838
I have removed the callback from 0 to 1
Everything seems to work, I can not help you more than that, I hope it will be useful to you.
Screenshot Download:
https://www.apdigital.it/SCREENSHOT.jpg

Hi Alex

As previously discussed, we can’t use the fix you’ve provided without disrupting other websites. To resolve the issue, we have first to replicate it locally. Please send us your home page layout if you’d like to assist further. This can be done from within Page Builder by going to Layouts > Import/Export > Download Layout. You can upload the JSON file to WeTranfer.com or any online location and post the link here. Once we’ve replicated the issue, we’ll be able to advise further.

To avoid editing the Widgets Bundle after the next update, we recommend contacting your hosting company to request that PHP display errors be set to false https://www.php.net/manual/en/errorfunc.configuration.php#ini.display-errors.

—

Hi @estatik

Thanks for posting. We’ve sent you a form submission requesting access to your pro plugin version for testing purposes. If you could perhaps drop us a reply when able, that would be most appreciated!

Thanks

Andrew

Hi Alex and @estatik

Estatik kindly provided us access to their pro version. Contrary to our previous feedback, we couldn’t find any issues with the widget implementation in the Estatik plugins. We’ve been unable to replicate the undefined array key warning reliably.

Alex, when you have a moment, kindly send us your page layout JSON file so we can attempt to replicate the issue locally. You can download your layout from Layouts > Import/Export > Download Layout. The JSON file can be uploaded to any online location like WeTransfer.com. To confirm, we cannot use the fix you’ve suggested without impacting existing Page Builder installations.

To prevent notices, warnings, and errors printing to your site front-end you can try adding the following below define( ‘WP_DEBUG_DISPLAY’, false ); in your WordPress wp-config.php file:

@ini_set( 'display_errors', 0 );

If WP_DEBUG_DISPLAY set to false and ini_set display_errors set to 0 aren’t effective, kindly contact your hosts.

Thanks

Andrew

The skeleton appears punctually with each update
mistake:

Warning: Undefined array key “1” in /web/htdocs/www.vendicompraffitta.it/home/wp-content/plugins/so-widgets-bundle/so-widgets-bundle.php on line 844
—————————————————————————-
Screenshot
https://www.apdigital.it/ScreenShot.JPG

Today
https://www.apdigital.it/ScreenShot_2.JPG
—————————————————————————-
Screenshot of my solution to buffer the problem, I cannot stay with the website in error for life

https://www.apdigital.it/ScreenShot_3.JPG
—————————————————————————-
Moving the call to 1
the problem disappears
I have pointed out the same problem to you many times.
Test PHP 8.0 | 8.01
I apologize very much to you for this tone, however, every time the Plugin is updated on time, the problem arises
Thanks for what you do
Greetings.

Hi Alex

Please, could you confirm that you’ve read the following message? https://www.ads-software.com/support/topic/last-update-error-8/#post-15771608.