Backoffice blocked and weird header

Hello,
After updating plugin yesterday my website turn wrong,
On top of the header it says:

    • Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/operations.class.php on line 2858
    • Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/operations.class.php on line 2862
    • Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/output.class.php on line 3708
    • Warning: Cannot modify header information - headers already sent by (output started at /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/operations.class.php:2858) in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/themes/x-child/header.php on line 9
    • Warning: Cannot modify header information - headers already sent by (output started at /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/operations.class.php:2858) in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/themes/x-child/header.php on line 10

And when i tried to log on the back office it says:

    • Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/operations.class.php on line 2858
    • Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/operations.class.php on line 2862
    • Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/output.class.php on line 3708
    • Warning: Cannot modify header information - headers already sent by (output started at /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-content/plugins/revslider/includes/operations.class.php:2858) in /homepages/38/d469253020/htdocs/mes-sites/inspiral/wp-includes/pluggable.php on line 1223

Please let me know where does it come from and how bad is it!

THK you very much for your help!

Ok I worked on it and i deactivate all plugin via php, it allowed me to enter in wordpress back office, then I activate all the plugin 1 by 1 and the slider revoltion slider is responsable of this mess! I don’t know how to fix this… I still need your help please :slight_smile:

Is it possible Slider Revolution is not compatible with PHP 7.3?
I tried it and came back to 7.2 when I noticed issues but it didn’t come back to normal.

Hi Jibb,

Thanks for reaching out.

These aren’t error but just warning, they are usually visible of your Wordpress WP_DEBUG is toggle on. To turn it off, please edit your site’s wp-config.php through FTP or your hosting’s file manager then set WP_DEBUG to false.

More about editing wp-config.php https://www.wpbeginner.com/beginners-guide/how-to-edit-wp-config-php-file-in-wordpress/, but it’s not related to the issue but will help you a lot navigating the file and its code.

Hope this helps.

Hi Rad,
Thk U for your answer but WP_DEBUG was already set to false… Any other ideas? Could it be a PHP issue?

Hey Jibb,

Please try setting WP Debug to true and add the additional lines posted below below the define( 'WP_DEBUG', true ); line. These are just taken from the Example wp-config.php for Debugging in WordPress’ debugging documentation at https://codex.wordpress.org/Debugging_in_WordPress. Please visit the link for more details.

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Hope that helps.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.