• Hi, I keep getting this error when opening our website http://www.zorgmarketeers.nl. I can’t deactivate WP LESS. Please help, site is down 2 days now. Thanks in advance! Regards, Wouter

    Fatal error: Uncaught exception ‘Less_Exception_Chunk’ with message ‘ParseError: missing closing */ in layout.less on line 368, column 3 366| } 367| 368| } /* /media query ‘ in /home/users/zorguftp/zorgmarketeers.nl/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php:535 Stack trace: #0 /home/users/zorguftp/zorgmarketeers.nl/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php(343): Less_Parser->GetRules(‘/home/users/zor…’) #1 /home/users/zorguftp/zorgmarketeers.nl/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Tree/Import.php(277): Less_Parser->parseFile(‘/home/users/zor…’, ”, true) #2 /home/users/zorguftp/zorgmarketeers.nl/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Tree/Import.php(193): Less_Tree_Import->ParseImport(‘/home/users/zor…’, ”, Object(Less_Environment)) #3 /home/users/zorguftp/zorgmarketeers.nl/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Tree/Ruleset.php(248): Less_Tree_Import->compile(Object(Less_Environmen in /home/users/zorguftp/zorgmarketeers.nl/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php on line 535

    https://wordpress.org/plugins/wp-less/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author oncletom

    (@oncletom)

    Well, the new parser might be less flexible.

    The aforementioned error states a Less syntax problem — I invite you to check it out, file layout.less, line 368. Looks like a comment is missing a closing */ (use // if you don’t want to close a single line comment).

    Thread Starter zorgmarketeers

    (@zorgmarketeers)

    Thanks! When I follow the path wp-less/vendor/oyejorge/less.php it says ‘File doesn’t exist’. That might me be the problem I guess? 😉 This way I cannot open Layout.Less.

    Can I reinstall the plug-in? Although deactivation isn’t working.

    Regards,

    Wouter

    Plugin Author oncletom

    (@oncletom)

    Well, it is a file used by your theme.

    If you have not authored your theme, you should report the error to its author.

    It is not a plugin issue, but more likely an error in a file of the theme. DIsabling the plugin and re-enabling it would not change anything to the problem.

    Thread Starter zorgmarketeers

    (@zorgmarketeers)

    Thanks for your help, I will contact the developer of our theme. Regards!

    Actually I’ve found that the new compiler used in version 1.8 has a problem with multi-line comments sometimes. We get a similar error (it acts like there’s a missing closing comment when there isn’t), but on the earlier versions of the plugin we have no problems. For example, the following code produces an error:

    /*! #Fonts and Colors *//*
    ================================================== */
    @primary-font: ‘Lato’, sans-serif;
    @secondary-font: ‘Cardo’, serif;

    //blues
    @header-blue: #66939c;

    I’ve tried removing all commenting – no dice.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Website down/fatal error’ is closed to new replies.