Undefined function siteorigin_panels_setting()

I had to switch off all the plugins through FTP and then switch them back on one by one. And guess what? The website works (although poorly, without proper grid and not showing certain elements wothin the grid) UNTIL I switch om the Page Builder 2.2.2. Then, when I activate the PB, the site crashes including WP admin panel, so I have to go back to FTP and start the mess all over again.

I’ve spent hundreds of hours building the site and now it looks like crap due to the plugin unexpected failure. Please help!!!

Hi fiorita

It appears as if some files might have been damaged at some point. The function siteorigin_panels_setting should be part of Page Builder. I’d suggest deleting the siteorigin-panels folder through FTP (in the wp-content/plugins folder), then reinstalling it.

Please let me know how this works out.

Hi Greg,

Thanks a lot for your response. I tried another solution which actually worked fine so far. I downloaded the WP 4.4.1. installation .zip folder and changed /wp-admin and /wp-includes through FTP. And I also reloaded Vantage theme I use.

I avoid deleting the PB plugin as the whole structure of the pages is corrupted when I reload it.

So, I guess the issue was with some corrupt files in WP and I wonder if it could be a malware or hackers’ attack.

Great plugin by the way. And theme.

With best regards, Fiorita

New problem here

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘siteorigin_panels_basic_widgets_init’ not found or invalid function name in /www/doc/www.fiorita.cz/www/wp-includes/plugin.php on line 525

PB was the ONLY switched plugin when the message appeared. Vantage theme

Please help

When trying to change a theme to twenty sixteen with PB active this is what I get:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘siteorigin_panels_basic_widgets_init’ not found or invalid function name in /www/doc/www.fiorita.cz/www/wp-includes/plugin.php on line 525

Warning: Cannot modify header information – headers already sent by (output started at /www/doc/www.fiorita.cz/www/wp-includes/plugin.php:525) in /www/doc/www.fiorita.cz/www/wp-includes/pluggable.php on line 1228

When trying to activate bundle:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘siteorigin_panels_basic_widgets_init’ not found or invalid function name in /www/doc/www.fiorita.cz/www/wp-includes/plugin.php on line 525

Warning: Cannot modify header information – headers already sent by (output started at /www/doc/www.fiorita.cz/www/wp-includes/plugin.php:525) in /www/doc/www.fiorita.cz/www/wp-includes/pluggable.php on line 1228

Warning: Cannot modify header information – headers already sent by (output started at /www/doc/www.fiorita.cz/www/wp-includes/plugin.php:525) in /www/doc/www.fiorita.cz/www/wp-includes/pluggable.php on line 1228

reloading the plugin page gives me white screen with this message:

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘siteorigin_panels_basic_widgets_init’ not found or invalid function name in /www/doc/www.fiorita.cz/www/wp-includes/plugin.php on line 525

Warning: Cannot modify header information – headers already sent by (output started at /www/doc/www.fiorita.cz/www/wp-includes/plugin.php:525) in /www/doc/www.fiorita.cz/www/wp-includes/pluggable.php on line 1228

Warning: Cannot modify header information – headers already sent by (output started at /www/doc/www.fiorita.cz/www/wp-includes/plugin.php:525) in /www/doc/www.fiorita.cz/www/wp-includes/pluggable.php on line 1228

reloading the plugin page gives me white screen with this message:

Fatal error: Call to undefined function siteorigin_widget_register() in /www/doc/www.fiorita.cz/www/wp-content/plugins/so-widgets-bundles/widgets/so-button-widget/so-button-widget.php on line 270

OK, I reinstalled both PB and bundle. Seems it works

Hi fiorita

Glad to hear you resolved this issue. Yeah, from the sounds of things something was damaged with the files. Files shouldn’t be getting damaged like this, so it’s worth investigating the issue with your web hosts.