thom4

I understand, it’s fair.

Keep me in touch if you discover any problem with your own usage of the plugin.
I hope it will save you some time during your developments!

An issue has been spotted and should be fixed by 1.5.2.

It would have persisted with any opcode cache not stating files.
Update the plugin, modify your stylesheet and it would be back on tracks.

On the next version I’ll add an admin panel to force reload/invalidate cache files to avoid those manipulations in case of bug.

Keep me in touch.

Cool, thanks @boogah for the insight!

It’s kinda weird to let a negative review despite there is an active support and you did not even wait for an answer.

Anyway, I hope we’ll find a solution for this problem.

Well the major problem is the garbage collector should not delete all files.

Do your hosting service provide APC cache? Because it can be an issue: an old PHP file is used instead of the updated ones.

wp-less does not hook on caching mechanism so normally wpengine would not have any effect on this problem (I hope).

Another alternative is to have apc.stat turned on.

> https://php.net/manual/en/apc.configuration.php#ini.apc.stat

It will check filechange for each request.

Good news! You should definitely keep APC on as it speeds up your website.

However it may be the only way to purge APC cache, disabling and enabling it.

Hi,

unfortunately there’s nothing special in the enqueue system because it is already what you should do even if not using LESS files.

I like the idea of automatic enqueuing; I’ll think about it.
But as WordPress works on explicit style declaration, I’ll not hurry about this feature yet it’s totally feasible.

Well, it’s weird. Try to deactivate and reactive the plugin.
This issue has been fixed in 1.5.1 so I’m hardly understanding why it would persist to exist on your installs.

Garbage collection is plugged in WP-Cron mechanism on a daily basis, and is effective for every file older than 5 days. Except than on 1.5.1 i’ve added a fix which keeps the more recent version of each compiled file, even if it’s older than 5 days.

Do you have APC file caching activated?

Ok stange. Maybe it was an issue combining both IP host and WP 2.4. Weird.

Nice to know your problem is now solved… and to know it works well on 2.5 ??

It was an issue of the 1.5 beta version. It has been fixed in 1.5.1. The garbage collector also cleaned used files.

If a cache system was active, the CSS was never compiled again causing your website to be naked.

Please be sure to have the latest version installed!

If your upload dir is writeable for image uploads, wp-less may write inside without any problem.

The plugin automatically creates the uploads/wp-less. This error is raised when it does not have the permissions to self-create this folder.

When you upload a picture in the media manager, is everything’s going right? Is the file system a plain filesystem or do you have some plugin like Amazon S3 Filesystem or anything like that?

Your other topic problem is maybe related to this writing issue.

The JavaScript library is nice only for prototyping stuff quickly within the browser. It’s definitively a bad idea in term of performance for the client-side.

Is your 10.z.y.x the hostname of your blog install?

The error is straightforward: the compiled CSS does not exist.
If you go in the wp-content/uploads/wp-less/intranet/css/ folder of your server, do you find something?

Do your LESS file rely on mixins located in Twitter Bootstrap library?

Fine. It’s more a library-specific problem but if I can ease stuff, I’ll do.

Thanks for have taken time to share that ??

Cool, nice to hear that ??