THE FIX for the 3.0 fatal error

  • Erik

    (@cleverpixel)


    1 year, 4 months ago

    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.

Viewing 10 replies - 1 through 10 (of 10 total)
  • digielu

    (@digielu)

    1 year, 4 months ago

    Confirmed, solution is working perfectly.

    igorrf

    (@igorrf)

    1 year, 4 months ago

    Fine ! Fine ! Fine !

    Thaaaaanks !

    nobita

    (@nobita)

    1 year, 4 months ago

    Thanks for providing the solution for wp-scss 3.0

    airplanenoise

    (@airplanenoise)

    1 year, 4 months ago

    I agree that this is fixable like that or rolling back, but the real issue is if you use this on like… dozens, hundreds of sites and you suddenly have a major outage. Couldn’t the plugin owner update it to 3.0.1 and add that missing Blocks folder and everybody’s happy?

    Thread Starter Erik

    (@cleverpixel)

    1 year, 4 months ago

    Obviously. I would have expected that to happen about an hour after 3.0 was published.

    I feel your pain, I’ve been using this on every site we build for years.

    ionian

    (@ionian)

    1 year, 4 months ago

    Excellent indeed! Thank you very much.

    abra2020

    (@abra2020)

    1 year, 4 months ago

    Thank you so much, it works perfectly!

    My follow-up question is: In the src folder of the github project are some more folders which are not included in my website’s src folder (e.g. “Ast”, “Collection”, “Extend”). Should I upload them as well on my server?

    Thanks again!

    abra2020

    (@abra2020)

    1 year, 4 months ago

    I just found the answer to my question by myself: yes, all missing folders should be uploaded –

    https://wordpress.org/support/topic/latest-update-breaks-the-site-but-here-is-the-fix/

    janramroth

    (@janramroth)

    1 year, 4 months ago

    Thank you very much! Could fix all my broken sites with your help. Replaced the whole /src folder from https://github.com/scssphp/scssphp to plugin dir /scssphp and done.

    Plugin Author Sky Bolt

    (@sky-bolt)

    1 year, 4 months ago

    Thank you for jumping in to take action and offering a correction for this issue. I mistakenly missed some files when committing to WordPress SVN for version 3.0.0

    This has been fixed in 3.0.2 and now with 4.0.2, which also has a new version of SCSSPHP 1.11 (which requires PHP 7.2)

    If you would like to help maintain this plugin, please reach out here.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘THE FIX for the 3.0 fatal error’ is closed to new replies.