Less Compiled CSS Cache-control
Posted 22 June 2012 - 07:49 PM
Posted 22 June 2012 - 08:58 PM
Posted 25 June 2012 - 04:48 AM
Posted 25 June 2012 - 04:01 PM
Posted 15 July 2012 - 07:45 AM
Posted 15 July 2012 - 02:38 PM
So either the transient times out and then the less is recompiled on the next page load, or you can flush this cache.
On the pagelines Theming page, it says this:
Tip:Disable the LESS caching system while working locally. Simpy adddefine('PL_LESS_DEV',true);to your wp-config file, and this will turn off the caching system. DO NOT use this on a production rig, or you'll face a nuclear melt-down. You have been warned!
This is not 100% accurate (not just about the nuclear melt-down part). The constant does not disable the caching system (at this point at least, perhaps things are in the works to be consistent with this statement in the future) but at current, it forces the LESS to be recompiled on every admin (backend) page load. So if this is set, all you have to do is reload/navigate to any admin page, (or if you just saved your options, that would work too) and that will recompile your LESS.
It's worth noting, that if you get a parse error in your LESS when it's compiled that your site will serve up a backup version of your last good compiled less. If you have a parse error it will let you know with a big red button in your wp admin bar, though so it's obvious. Basically, if you have a parse error, you won't see your most recent changes even if you're forcing a recompiling of the less.
@danny, @beardedavenger -
About the problem I referenced above, please let the developers know that there is a typo in the __construct function of the PageLinesRenderCSS class defined in class.render.css.php
$this->ctimout = 86400;where the set_transient functions use
Posted 15 July 2012 - 06:20 PM
Posted 15 July 2012 - 06:36 PM
Posted 15 July 2012 - 06:59 PM
Posted 15 July 2012 - 08:16 PM