Updating from 2.0.1 -> 2.1.1 breaks CSS completely

  • We updated several of our websites to WP-SCSS 2.1.1, but it breaks the CSS completely after updating.

    When I save the WP SCSS settings once after updating, the CSS is working correctly.

    I can see the compiled CSS file it not loaded correctly after updating, it’s trying to enqueue:
    //css/master/master.css?ver=1606835284

    Instead of:
    https://my-website.com/wp-content/themes/mytheme/css/master/master.css?ver=1606835284

    —-

    Could you please fix this as soon as possible? We have about 100 websites, which we can’t all update manually (as in saving the WPSCSS settings once).

Viewing 3 replies - 1 through 3 (of 3 total)

  • I found a workaround for this. Not sure if it helps you, but go into the settings for WP-SCSS and choose “Compressed” compiling mode. That seemed to work for us. Wish the developers would fix this as it was fixed with 2.0.1 but then back to broken again after. ??

    Thread Starter daveykj

    (@daveykj)

    v2.1.2 made it even worse. When saving the settings now (with ‘Current theme’ as the base path), the correct path to the compiled CSS is not updating (!!).

    It’s loading:
    //css/master/master.css?ver=1611914355

    Instead of:
    https://my-website.com/wp-content/themes/mytheme/css/master/master.css?ver=1611914355

    The fix:
    In wp-scss.php on Line 301 $base_compiling_folder is missing.
    Add it to global like this:

    global $wpscss_compiler, $wpscss_options, $base_compiling_folder;

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Updating from 2.0.1 -> 2.1.1 breaks CSS completely’ is closed to new replies.

Tags