Hi, I am getting the warning from Wordfence that the plugin has been abandoned because no updates have been made for 2 years ( Dec 15 2022). Everything is working fine but I was wondering if somekind of change could be made to prevent this from happening?
Thanks for anything you can give regarding this issue
Cheers
Ian
I’m constantly getting these PHP Warnings in my error log:
[17-Sep-2024 06:58:16 UTC] PHP Warning: file_get_contents(/home/website/public_html/wp-content/plugins/wp-scss/cache/main.css): Failed to open stream: No such file or directory in /home/website/public_html/wp-content/plugins/wp-scss/class/class-wp-scss.php on line 107
[17-Sep-2024 06:58:16 UTC] PHP Warning: unlink(/home/website/public_html/wp-content/plugins/wp-scss/cache/main.css): No such file or directory in /home/website/public_html/wp-content/plugins/wp-scss/class/class-wp-scss.php on line 108
Is this an issue in WP SCSS or in LiteSpeed Cache, my caching plugin? If either, anyone know how to fix it or at least turn off the reporting? The SCSS compiles fine and displays correctly on the frontend (in main.css), so there’s no visible issues. It’s just irritating that these are constantly filling up the error log.
]]>The plugin writes messages about deprecated functions in the logs. I use PHP 8.2
PHP Deprecated: Creation of dynamic property Wp_Scss::$scss_dir is deprecated in /wp-content/plugins/wp-scss/class/class-wp-scss.php on line 22
PHP Deprecated: Creation of dynamic property Wp_Scss::$css_dir is deprecated in /wp-content/plugins/wp-scss/class/class-wp-scss.php on line 23
PHP Deprecated: Creation of dynamic property Wp_Scss::$compile_errors is deprecated in /wp-content/plugins/wp-scss/class/class-wp-scss.php on line 24
PHP Deprecated: Creation of dynamic property Wp_Scss::$scssc is deprecated in /wp-content/plugins/wp-scss/class/class-wp-scss.php on line 25
PHP Deprecated: Creation of dynamic property Wp_Scss::$cache is deprecated in /wp-content/plugins/wp-scss/class/class-wp-scss.php on line 27
PHP Deprecated: Creation of dynamic property Wp_Scss::$sourcemaps is deprecated in /wp-content/plugins/wp-scss/class/class-wp-scss.php on line 32Is there any way with the filter hook ‘wp_scss_variables’ to assign a Sass Map?
For example:
$variables['palette'] = array(
'primary' => '#012345',
'secondary' => '#543210',
'success' => '#3adb76',
'warning' => '#ffae00',
'alert' => '#cc4b37',
);This doesn’t work but it seems like there should be some way? Thanks for any help.
]]>I’m seeing this PHP warning for 50+ sites where the css location is set to /css/
PHP Warning: Trying to access array offset on value of type null in /var/www/sitename.com/htdocs/wp-content/plugins/wp-scss/wp-scss.php on line 342
Changing the css location to something else resolves the error, but I’d rather keep it as /css/
]]>I’ve got a file style.scss where I import all the .scss files. Still I get errors of undefined variables and mixins. So it seems it is not importing it or not importing it right. Do I need to change the way I do this?
Hope to receive an answer soon. Thanks in advance!
]]>This has been mentioned in other threads, I didn’t discover it. I’m just posting it up here because it took me a lot of digging to find. It’s too bad the developer isn’t following this as it’s caused me, and a lot of other people, a bunch of headaches.
THE PROBLEM
The plugin relies on this project: https://github.com/scssphp/scssphp
That’s great, except a critical portion of that project was not included in the 3.0 update. It’s missing the src/Block directory.
THE SOLUTION
Either revert to the previous version OR manually upload the missing folder. I’ll explain the process of uploading the missing folder.
You can download the scssphp project from the Github link above. Go to the link and click Code > Download Zip. Open the zip file on your computer and open up the ‘src’ folder. Inside you’ll see a folder called ‘Block’.
Via FTP, SSH, or your host’s file manager app you can upload the Block folder inside the plugin at: /wp-content/plugins/wp-scss/scssphp/src
As soon as I did this the error was gone, the website was back online, and Sass was compiling as expected.
I hope this helps.
]]>For those who work with multiple sites and have your plugin installed are going through hours of work to fix this, one by one.
Please check your updates before publishing them. The plugin is great, but this is a critical error that is costing time and money to a lot of people.
]]>Can we please get some proper developers on this project? I’m willing to pay/donate if that helps.
This is literally the third (out of like.. 4? 5?) versions that crashes a majority of the websites out there.
Is there a more stable alternative?
]]>Plugin has to be deactivated after latest update. Can we find a fix or roll back please?
]]>Hello
I created my website as stagging for dev in the beginning and the plugin worked great, when i transferred the website to the prod environment the plugin is causing the website to go down, i can’t use it on the prod website so i need to disable it.
Is there a step or something to change that i can use the plugin on the prod website.
Thanks
]]>Please remove version 3.0 from the plugin directory. It causes a critical error!
]]>I just updated this on another site to see if I got the same fatal error result, I did.
Here you go:
WordPress version 6.1.1 Active theme: (version ) Current plugin: WP-SCSS (version 3.0.0) PHP version 7.4.27 Error Details ============= An error of type E_ERROR was caused in line 494 of the file /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Parser.php. Error message: Uncaught Error: Class 'ScssPhp\ScssPhp\Block\CallableBlock' not found in /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Parser.php:494 Stack trace:
#0 /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Parser.php(287): ScssPhp\ScssPhp\Parser->parseChunk()
#1 /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Compiler.php(5707): ScssPhp\ScssPhp\Parser->parse()
#2 /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Compiler.php(2673): ScssPhp\ScssPhp\Compiler->importFile()
#3 /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Compiler.php(2885): ScssPhp\ScssPhp\Compiler->compileImport()
#4 /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Compiler.php(2348): ScssPhp\ScssPhp\Compiler->compileChild()
#5 /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Compiler.php(736): ScssPhp\ScssPhp\Compiler->compileChildrenNoReturn()
#6 /opt/bitnami/wordpress/wp-content/plugins/wp-scss/scssphp/src/Compiler.php(516): ScssPhp\ScssPhp\Compiler->coI’m having an issue with the latest update – getting a PHP error that states “Uncaught Error: Class ‘ScssPhp\ScssPhp\Block\DirectiveBlock’ not found in …/wp-content/plugins/wp-scss/scssphp/src/Parser.php:876.
Deactivated the plugin and the site started working again. Do we know of a fix for this issue?
]]>The latest version appears to be broken and throws errors like:
An error of type E_ERROR was caused in line 618 of the file /nas/content/live/[mysite]/wp-content/plugins/wp-scss/scssphp/src/Parser.php. Error message: Uncaught Error: Class 'ScssPhp\ScssPhp\Block\CallableBlock' not found in /nas/content/live/[mysite]/wp-content/plugins/wp-scss/scssphp/src/Parser.php:618
Issue exists across multiple version of PHP from 7.3 to 8. In my case, these are all child themes.
Deactivating the plugin resolves the issue as long as I have Enqueue Stylesheets unchecked, or made sure to enqueue them myself. Such a handy plugin, hope it can be resolved.
]]>I’m working on a new site with WP_DEBUG enabled & I’m seeing this warning:
Warning: Array to string conversion in /www/website_447/public/app/plugins/wp-scss/scssphp/src/Compiler.php on line 878
The plugin is still working as expected.
]]>Hello, we’re unfamiliar with your plugin but have recently inherited a site that uses it. We’ve noticed that rem units i.e 2rem are being ignored by browsers, and I wonder if this could be to do with your plugin and some kind of compatibility issue? I’m able to see the rem units in the browser inspector, but they are not honoured. Does this sound familiar?
Thanks
]]>Hi
Just starting to use wp-scss. Settings are:
base location: current theme
scss location: /custom-theme/scss/
css location: /custom-theme/css/
I keep getting a warning message:
/home…/plugins/wp-scss/cache/test.css
no such file or directory in:
/home…/plugins/wp-scss/class/class-wp-scss.php on line 108
It’s intermittent but happens often enough that it’s disruptive.
Can you advise?
]]>Hello,
Is it possible to edit UnderStrap (and UnderStrap child) SASS directly in WordPress using this plugin?
Thanks!
]]>Empty selector list in the “not()” pseudo class is crashing the site.
Example CSS for reproduction: .class:not()
Hi,
I noticed that all the files imported into my main file are also compiled independently which forces me to delete all the “child” files each time I make a small correction.
I don’t see an option in the admin to prevent this.
Do I miss something ?
Regards
]]>Dear Support!
I liked this plugin, thanks the development!
I follow with one bug: If in my scss file exists “grid-area” options, after compiling is run i get wrong value.
—
Sample:
SCSS line:
.three-col div.first { grid-area: 2 / 1 / 2 / 5 }
Result:
.three-col div.first { grid-area: 0.0138888889 }
—
Please help me!
]]>Within the past week, my scss has stopped compiling when I update my scss files, even though I have ‘Always Recompile’ enabled. I’m updating the files by uploading newer versions via SFTP.
I’m also seeing this PHP Warning when I turn on debug.log:
PHP Warning: unlink(/srv/www/www.website.org/wp-content/plugins/wp-scss/cache/styles.css): No such file or directory in /srv/www/www.website.org/wp-content/plugins/wp-scss/class/class-wp-scss.php on line 108
]]>After 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
Hello,
I activated this on a site I had used it on in the past and find that it is not working at all.
I have enabled always recompile in settings. I have set it to current theme and set the locations to /sass/ and /.
I am not getting any errors on the front or back end, and the error_log.log file is untouched.
]]>After updating WP to 5.8.2 and the plugin to the latest version, it crashed my site with the error message below. I’m running PHP 7.4. I removed and reinstalled it but still get the same compiling error. As I’m non technical, I don’t know what to do. Just passing it on in the hope that a new version will solve the problem…
Thanks
Fatal error: Uncaught InvalidArgumentException: Invalid output style "scss_formatter". in /home/wwstrategies/www/www/wp-content/plugins/wp-scss/scssphp/src/Compiler.php:5444 Stack trace: #0 /home/wwstrategies/www/www/wp-content/plugins/wp-scss/class/class-wp-scss.php(29): ScssPhp\ScssPhp\Compiler->setOutputStyle('scss_formatter') #1 /home/wwstrategies/www/www/wp-content/plugins/wp-scss/wp-scss.php(221): Wp_Scss->__construct('/home/wwstrateg...', '/home/wwstrateg...', 'scss_formatter', 'SOURCE_MAP_NONE') #2 /home/wwstrategies/www/www/wp-settings.php(409): include_once('/home/wwstrateg...') #3 /home/wwstrategies/www/www/wp-config.php(100): require_once('/home/wwstrateg...') #4 /home/wwstrategies/www/www/wp-load.php(50): require_once('/home/wwstrateg...') #5 /home/wwstrategies/www/www/wp-admin/admin.php(34): require_once('/home/wwstrateg...') #6 /home/wwstrategies/www/www/wp-admin/index.php(10): require_once('/home/wwstrateg...') #7 {main} thrown in /home/wwstrategies/www/www/wp-content/plugins/wp-scss/scssphp/src/Compiler.php on line 5444
There has been a critical error on this website. Please check your site admin email inbox for instructions.(no message was received)
]]>Hi everyone,
First of all, I’d like to thank the plugin creators and contributors.
Ever since the latest updates I get a warning on top of a random page on my website. The page I get this error changes. When I clear the cache, the issue is solved. But then again in a couple of days at max I get the same message again.
The error message reads:
Warning: unlink(/home/public_html/wp-content/plugins/wp-scss/cache/styles.css): no such file or directory in /home/public_html/wp-content/plugins/wp-scss/class/class-wp-scss.php on line 108
My settings are as follows:
Base Location: Current Theme
SCSS Location: /inc/assets/css/sass/scss/
CSS Location: /inc/assets/css/sass/
Compiling Mode: Compressed
Source Map Mode: Inline
Error Display: Show to Logged in Users
Enqueue Stylesheets: Checked
Always Recompile: Checked
Tried to change settings to no avail.
Kindly requesting help with this issue.
Thanks in advance to all.
]]>Understrap recently updated with no warning and wiped out my _theme.scss file with all of my style. I had a backup, pasted it into that location and updated the settings for WP-SCSS. I have confirmed in my BlueHost file manager that this is absolutely where this file lives, but WP-SCSS throws an error saying that it’s not a valid file path. Please advise.
/src/sass/theme/_theme.scss
WP-SCSS: The SCSS directory does not exist (/home2/yxqmnvmy/public_html/northerncaliforniacreative/wp-content/themes/understrap/src/sass/theme/_theme.scss/). Please create the directory or update your settings.
]]>I’m using this awesome plug-in in combination with a SCSS framework.
But since the last version they also use @use and @forward instead of @import only. This creates unwanted compiling errors.
]]>Greetings Sky Bolt and Connect Think,
My team and I are long-time users of this exceptional plugin and appreciate all of your hard work to maintain it. WP-SCSS has been a core component of our workflow for the past four years and has helped improve our WordPress projects and deliverables in countless ways. From ourselves and the greater community, thank you so much for continuing to keep this plugin updated and alive!
I am writing today to mention an unexpected issue we’ve been running into with the 2.3.X versions of the plugin. We’ve been testing these latest releases on a dev site (a clone of our master template site that we actively maintain for new projects). We’re running into a particular issue that didn’t exist in WP-SCSS v2.1.6 and earlier which has become a pain point for us.
On more than 150 of our client websites using WP-SCSS, we have been importing a partial file that includes all of our predefined breakpoints mixins to simplify our workflow. After upgrading to 2.3.X versions of WP-SCSS (the latest being 2.3.5 as of writing this post), WP-SCSS is throwing the following sass compiling error message regarding mixed units in mixins: https://rzfg.co/D4zgPS.
Within our foundation partial file, our breakpoints mixins are set using a combination of rem and px units for media queries as seen here: https://rzfg.co/oeqkpu.
After revising units to be rem only, the media queries now look like this: https://rzfg.co/q2fsxN. The WP-SCSS sass compiling error message disappears entirely and there are no further problems.
Would it be possible to continue including support for mixed units in future versions of WP-SCSS? Updating each of our sites individually, in a similar manner to the example above, is not ideal and would take an incredible amount of time to resolve for our small firm of three.
For the time being, we have no other choice but to continue using an outdated version of the plugin that supports mixed units, which is not a viable long-term strategy. We cannot afford to have all of our sites break if updated to the latest version.
Our team would appreciate learning more about the decision behind this change, and if supporting mixed units is perhaps an outdated practice that should be avoided altogether.
Thanks so much for your time and energy. We look forward to hearing back from you.
With gratitude,
Swerley
]]>