thom4

Oh OK i got the point!

Well it might be a replacement issue, something I’ve let passing through as I don’t recommend generating content outside the configured WordPress upload_dir; this is the sole directory supposed to be writeable at any moment.

Have you spotted where in the code this problem is happening?

@mikemuller you seem to enqueue stuff the good way.

I’d bet you have a customized blog URI somewhere and the plugin is getting messed with that.

If you want to use a CDN, i recommend you using only the setUploadUrl(): it will save the compiled CSS file in the proper location and will render the proper CDN uri to the browser.

Very good question but tricky answer.

Do you want to clean the existing compiled files OR also regenerate compiled files?

In the first case, you could simply delete any files located in your wp-content/uploads/wp-less directory. The compiled files will be regenerated on the next displayed page.

However it may not work if any server-side cache system is enabled and has not been flushed too.

At the moment, calling a page embedding a LESS file is the only way to recompile a LESS file. WP lacks of a CLI interface to process administrative tasks. An HTTP query could do the trick but it should be secured (secret URI known and (re)generated by an admin).

In the future, for an admin page feature, it would be necessary for the plugin to know about the enqueued LESS files at another moment than the runtime to display those informations. Prior to that moment, it will be a little bit hacky.

Otherwise, flush all caches, css compiled files and launch a browser to generate anything needed (to simulate visits and reduce the payload for the next real visitor).

Hello,

yes it would be great. I’m lacking of time until the end of May to work on that.
Anyway, you can still contribute a pull-request to add this feature, even if it’s “just” a button to clear the whole cache — and especially as you already coded such a feature for your own needs ??

> https://github.com/oncletom/wp-less

Why would you like not to enqueuing?
It’s the recommended way of including CSS files into any template files.

If the LESS file is directly included in a style or link tag in your templates, it won’t work.

It does not seem to be the way of working of the Roots theme though.

I had a quick look and did not find an obvious location of where the theme is registering the stylesheet(s) in the code. If you provide me some more insights about that, I may help you to figure out how to deal with this problem.

Well, that’s weird.

What is the complete line containing this LESS code?

It should be fixed in the 1.5.3 release.

Hm, I’m not sure to understand the issue you are encountering: you mean files are not compiled in .css?

OK I should definitely update the LESS library; I’m a bit late in the updates since I relocated.

Feel free to propose a PR on the github project: https://github.com/oncletom/wp-less

I think I understand what you are trying to do but it’s not related to the plugin; only to the way you enqueue CSS files.

You should either plug your LESS file in a hook happening after the one loading the CSS file. Otherwise, you should access the $wp_styles (or a similar global containing styles/scripts loader) and change the priority.

Hi both of you,

within the new mechanism introduced in 1.5, some data are stored in database.
It lacks of a “rebuild CSS” button so to fix the problem, simply update a LESS file to force the CSS compilation.

Hi,

it’s a compilation error.
Maybe your @index value is incorrect and thus your .span mixing generates an invalid behavior.

It is not a recommended practice to alter the original plugin file — especially it it’s updated later without a bugfix or because it is related to a misuse/misunderstanding.

What’s changing between your local and your production environment? Maybe do you configure a domain differently?

Which version of the plugin do you use? Have you APC enabled?
A fix has previously been introduced for hostname and generally, people had trouble because APC was caching old files so the new update of WP-LESS was in fact not taken in account.

I need those informations to determine if it’s either a bug or not.
Thanks ??

And the fix included in 1.5.2. I’ve missed the PR.