Conversation
supportAfter updating the plugin the website crashes. If we deactivate and try to reactive the plugin, it wouldn’t active either. Is anyone else facing this same issue? Hope the developer will fix this issue ASAP. Fatal error: Uncaught InvalidArgumentException: Invalid output style "scss_formatter". in .../wp-content/plugins/wp-scss/scssphp/src/Compiler.php:5444 Stack trace: #0 .../wp-content/plugins/wp-scss/class/class-wp-scss.php(29): ScssPhp\ScssPhp\Compiler->setOutputStyle('scss_formatter') #1 .../wp-content/plugins/wp-scss/wp-scss.php(189): Wp_Scss->__construct('/nas/content/li...', '/nas/content/li...', 'scss_formatter', 'SOURCE_MAP_NONE') #2 .../wp-admin/includes/plugin.php(2286): include_once('/nas/content/li...') #3 .../wp-admin/plugins.php(191): plugin_sandbox_scrape('wp-scss/wp-scss...') #4 {main} thrown in .../wp-content/plugins/wp-scss/scssphp/src/Compiler.php on line 5444
So the issue is from plugin version 2.3.0 onwards. Kept on trying downgrading the plugin to a version lower. No luck till 2.3.0, but when the plugin was downgraded to version 2.2.0 everything on the website looked how it was supposed to look. The moment plugin is upgraded to version 2.3.0 or higher, the website looks funny :). Hope the developers will look into it and resolve it quickly.
Line 5444 throws an exception, this means that there is invalid scss somewhere in your styles. I have the same issue on a site (multi-site enabled) and it only crashes on my sub-sites. I have changed line 5444 to break; and commented out the thrown exception. To the WP-SCSS Team: Can you please adjust the compiler to log an error and throw a site-crashing fatal exception? This would be much more helpful.
Found the root of the problem, while the above mentioned was a band-aid, I did find that we have bad (old) setting for Compiling Mode – the issue we have is that there are over 800 sub-sites and some are good, others not. We can address that internally. There is a database cleanup routine, my suggestion for the plugin team is to simply replace any non-valid option rather than replacing previously-known options in wpscss_plugin_db_cleanup() routine. For any others with this issue, as noted in another thread, deleting the option works… https://wordpress.org/support/topic/2-3-2-fatal-error-on-save-settings/ Also noted that the current version of SCSSPHP is v 1.10, whereas this plugin uses 1.5, so maybe get that up to date, although it still contains the same exception handler.
So the issue is from plugin version 2.3.0 onwards. Kept on trying downgrading the plugin to a version lower. No luck till 2.3.0, but when the plugin was downgraded to version 2.2.0 everything on the website looked how it was supposed to look. The moment plugin is upgraded to version 2.3.0 or higher, the website looks funny :). Hope the developers will look into it and resolve it quickly.
Line 5444 throws an exception, this means that there is invalid scss somewhere in your styles. I have the same issue on a site (multi-site enabled) and it only crashes on my sub-sites. I have changed line 5444 to break; and commented out the thrown exception. To the WP-SCSS Team: Can you please adjust the compiler to log an error and throw a site-crashing fatal exception? This would be much more helpful.
Found the root of the problem, while the above mentioned was a band-aid, I did find that we have bad (old) setting for Compiling Mode – the issue we have is that there are over 800 sub-sites and some are good, others not. We can address that internally. There is a database cleanup routine, my suggestion for the plugin team is to simply replace any non-valid option rather than replacing previously-known options in wpscss_plugin_db_cleanup() routine. For any others with this issue, as noted in another thread, deleting the option works… https://wordpress.org/support/topic/2-3-2-fatal-error-on-save-settings/ Also noted that the current version of SCSSPHP is v 1.10, whereas this plugin uses 1.5, so maybe get that up to date, although it still contains the same exception handler.