Support » Plugin: WP-LESS » [Plugin: WP-LESS] Feature Request: Allow disabling the chache during development

Viewing 7 replies - 1 through 7 (of 7 total)
  • This would allow disabling the cache during development where you make frequent changes and curtain changes that do not trigger a cache reset.

    sorry, that’s apply_filters not apply_filter.

    Plugin Author oncletom

    (@oncletom)

    Well, each time you change a less file it is recompiled.

    At least, we could detect that through the WP_DEV constant.

    The issue I find is that if all you’re changing is the value of variables, it doesn’t detect the change. For ex.
    if you change from this:

    @test: 5em;
    .test {
    line-height:@test;
    }

    to

    @test: 10em;
    .test {
    line-height:@test;
    }

    it doesn’t seem to detect it. Also I don’t think it detects changes to files that are included.
    That’s the reason I suggested this capability (and implemented it on my installation). Thanks for any input you jave on this, And thanks again for the plugin.

    Plugin Author oncletom

    (@oncletom)

    Do this occurs on imported stylesheets (via @import) or on WP registered stylesheets?

    I need a a filter hook to force function, too.
    If I use addVariable (Example: Theme Options within WordPress Backend) the cache is not automatically renewable. I must change something in style.less first. PHP custom variables make no sense, since if style.less must always be touched.

    Plugin Author oncletom

    (@oncletom)

    Ok, I’ll add something to deal with variables, and eventually an automatic rebuild when WP_DEBUG is set to true.

    In 1.4.2, the plugin detects variable changes and recompile if needed.

    Thanks for you feedback!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: WP-LESS] Feature Request: Allow disabling the chache during development’ is closed to new replies.