Warning and Notice in debug.log

Hi there,

Thank you for reaching out!

Can you please provide us with more details of your inquiry?

Best,

Good day,
to reproduce the problem:

1) Activate the debug mode in WordPress by writing the debug.log file
2) Enter administration – BACKEND –
3) Enter Simple Share Buttons administration – BACKEND –
4) Open file debug.log and see the dozens of Warning and Notice errors.
Tested on both local MAMP development and web server.

Note: There are no errors in the FRONTEND.

Claudio_

Hi there,

Thanks for your reply!

Can you please verify for me if you are still experiencing this issue on your end?

Regards,

Hi :-),
yes, it seems strange to me that you are not able to reproduce it on your installation.
Tested on both local MAMP development and web server.
Claudio_

Hi there,

Thank you for your reply!

Our services were under maintenance on the last days as per some optimization updates that were made in order to improve all of our users’ experience and therefore the platform hiccuped a bit.

Check out the latest version and let us know if the issue persists,

Best,

Hello,
the problem has not been resolved.

I changed plugins.

Thanks, anyway, Claudio_

Hi there,

Thank you for your reply!

I apologize for any inconvenience this may have caused you and
let me inform you that we are on version 8.1.1 now, this version should be working properly and solved this problem.

Best,

I can confirm this is still happening in 8.1.2

The same warnings that k15lmk98 has been receiving. I am not using debug.log but actually showing these errors in development environments.

It makes the site unusable. I prefer to develop with errors noticeable to prevent myself from creating any of these issues. So silencing the errors with display_errors or wp_debug_display is not an option

@ehlovader I’m sorry you’re seeing those old errors. In 8.1.2 we are checking if each of those indexes exist before using them so there should be no reason for the errors to persist. If you could send any information specific to your site’s errors I’d be happy to do another once over.

Sorry for my delay in response. I don’t check in over here often, and tbh this resolved itself on my staging server but just found that it had returned on my local.

it appears that the warnings are occurring in the class-styles.php with all of the ssba_* keys on arr_settings and may be the result of an un accepted terms value somewhere, not sure why the default styles wouldn’t be set, but I was able to get it all working when I accepted terms in the admin.

Hope this helps.

Glad to hear you were able to resolve the error on your stage environment. Your additional information is appreciated. I’ll go ahead and see if I can replicate the local error that returned on your local on my end, but for now we’ll mark this as resolved. Feel free to create a new support ticket if you run into anything else. Thanks.

-Scott