Crashing Site

I have something the same:

Today I updated my website with the plugging WP-LESS.
With the new update (1.7.6) I see nothing on my homepage.
Admin is working as well.

When i deactivate this plugin, my site is working as well.
What can I do to let my site working with update 1.7.6?

I’m having issues to. The whole site goes white on the front end after the upgrade. Here is the PHP error log:

[09-Sep-2015 18:02:48 UTC] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘variable @white-faded is undefined: failed at `s”;
` /home/username/public_html/wp-content/themes/brook/stylesheet/less/main.less on line 47′ in /home/username/public_html/wp-content/plugins/wp-less/vendor/leafo/lessphp/lessc.inc.php:3553
Stack trace:
#0 /home/username/public_html/wp-content/plugins/wp-less/vendor/leafo/lessphp/lessc.inc.php(2097): lessc_parser->throwError(‘variable @white…’, 741)
#1 /home/username/public_html/wp-content/plugins/wp-less/vendor/leafo/lessphp/lessc.inc.php(1852): lessc->throwError(‘variable @white…’)
#2 /home/username/public_html/wp-content/plugins/wp-less/vendor/leafo/lessphp/lessc.inc.php(1475): lessc->get(‘@white-faded’)
#3 /home/username/public_html/wp-content/plugins/wp-less/vendor/leafo/lessphp/lessc.inc.php(1480): lessc->reduce(Array, false)
#4 /home/username/public_html/wp-content/plugins/wp-less/vendor/leafo/lessphp/lessc.inc.php(686): lessc->reduce(Array)
#5 /home/username/public_html/wp- in /home/username/public_html/wp-content/plugins/wp-less/vendor/leafo/lessphp/lessc.inc.php on line 3553

I had to disable the plugin to get the site back.

Do anyone associated with developing the plugin actually monitor these messages, or are we just wasting our time by asking questions here?

@dbmurray oh, how rude this is. Free software and you ask for a quick service? Come on… I did not even get any of these notifications, which makes it hard to be aware of these issues, and then to provide support.

Even though, you have to assume developers use their spare time and have a life. Better to be supportive rather than trying to drawn them down into some passive/aggressive shameful message.

1.8.0 has been released and use a different version of Less compiler.
Give me a shout and be responsible, stop ranting – leave that to the french ??

Hey all,

The theme developed by me required WP-Less plugin. I’m pretty sure that @dbmurray is using it. New version of Less compiler caught a typo in my .less files that caused a fatal error (previous version didn’t mind it).

The issue of this topic is caused by the theme’s integration of the plugin and not the plugin itself!

@dbmurray This has now been resolved, and theme will be updated very soon.

@oncletom Thanks for actively developing and maintaining the plugin! Great job! And sorry for the harsh messages, especially when you were not the one making the error at all. Hope that it didn’t ruin your coffee :/

@matijamrkaic no worries, the only problematic message was @dbmurray’s one.

oncletom,
I do appreciate all the work you do, and apologize for my “tone” in the way the complaint was conveyed. I should not have used the phrase “wasting our time.”

There was nothing rude intended, however. It really was a serious question not intended to sound hateful. Some support forums are for users to help each other. Other support forums are monitored by developers who respond directly to questions. I did not know if developers typically responded directly here or not.

matijamrkaic,
The theme I am using is called Sleek. I purchased it at the Theme Forest website.

The developer of the theme has responded saying they are currently reviewing the latest update of the WP Less plugin, and that he anticipates all issues will be resolved.

I am actually having almost the same problem with version 1.8.0
I have several comments with /*! stuff here */ and they seem to be causing parse errors, though they didn’t on the old versions. Is this something that is fixable, or should I just go change my comment structure for the relevant sites?

Error Log shows the following:
PHP Fatal error: Uncaught exception ‘Less_Exception_Chunk’ with message ‘ParseError: unmatched /* in layout.less on line 29, column 52\n27| \t\n28| /*! #Fonts and Colors *//*\n29| ================================================== */\n30| @primary-font: ‘Lato’, sans-serif;\n31| @secondary-font: ‘Cardo’, serif;\n32| ‘ in /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php:535\nStack trace:\n#0 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php(474): Less_Parser->GetRules(‘/nas/wp/www/clu…’)\n#1 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php(346): Less_Parser->_parse(‘/nas/wp/www/clu…’)\n#2 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lessc.inc.php(147): Less_Parser->parseFile(‘/nas/wp/www/clu…’)\n#3 /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lessc.inc.php(225): lessc-> in /nas/wp/www/cluster-41977/cedarhurst/wp-content/plugins/wp-less/vendor/oyejorge/less.php/lib/Less/Parser.php on line 535

The Sleek developer released a new version of the theme today. I have installed it as well as the 1.8.0 version of the WP Less plugin.

Everything appears to be working correctly. Thanks for the fix!

On 1.8, I’m getting “Fatal error: Uncaught exception ‘Less_Exception_Chunk’ with message ‘ParseError: Unexpected input in fwt.less on line 131, column 39 129| padding-left: 0; 130| } 131| .simple-social-icons a { .rounded(3px); } 132| h1 { 133| font-size: 36”

after upgrade. It was working until upgrade. I’ve run the section in question through a LESS tester and get no errors.

It seems to be a Less compiler related issue: https://github.com/oyejorge/less.php/issues/149