Kev-H

Yeah, I hadn’t had any issues until the 2.x version. Some of the recent updates have added features I don’t need, so many of my sites are just running older versions (generally a bad practice, but I haven’t seen any recent security fixes, so should be safe in this context).

You can always pull an older version from GitHub and then rename it (WP-SCSS-NO-UPDATE) or bump the version (“Version: 999” in wp-scss.php) to block the update prompts.
https://github.com/ConnectThink/WP-SCSS/tree/639955edbb00b837b76bfa077bb6816952a0d94a

As for alternatives, I’ve tried quite a few options (including local compiling) and there’s nothing that works as well for my dev workflow.

I’ve encountered a similar error on a few sites and was able to fix with the following workflow:

– Comment out the function on line 88 (via FTP)
– Navigate to WP-SCSS settings in dashboard
– Save setting
– Uncomment function on line 88 (via FTP)

WP Engine can also be finicky with permissions after editing files via FTP, so you might want to navigate to the WP Engine tab in the dashboard and hit the “Reset File Permissions” button.

I had a similar issue on upgrading to 2.3, which deprecates some of the output formats:
“Uncaught Error: Class ‘ScssPhp\\ScssPhp\\Formatter\\Crunched’ not found”

I fixed this with the following workflow:
– Activate a theme that doesn’t have your chosen “/scss/” directory
– Activate WP-SCSS plugin, which should throw a warning that the SCSS directory is not found
– Navigate to WP-SCSS settings and re-save your setting with the new options
– Reactivate your original theme

Hope that helps!

I had a similar issue on upgrading to 2.3, which deprecates some of the output formats:
“Uncaught Error: Class ‘ScssPhp\\ScssPhp\\Formatter\\Crunched’ not found”

I fixed this with the following workflow:
– Activate a theme that doesn’t have your chosen “/scss/” directory
– Activate WP-SCSS plugin, which should throw a warning that directory is not found
– Navigate to WP-SCSS settings and re-save your setting with the new options
– Reactivate your custom theme

Hope that helps!

I had a similar issue on upgrading to 2.3, which deprecates some of the output formats:
“Uncaught Error: Class ‘ScssPhp\\ScssPhp\\Formatter\\Crunched’ not found”

I fixed this with the following workflow:
– Activate a theme that doesn’t have your chosen “/scss/” directory
– Activate WP-SCSS plugin, which should throw a warning that directory is not found
– Navigate to WP-SCSS settings and re-save your setting with the new options
– Reactivate your custom theme

Hope that helps!