Is there a way to force the CSS to be recompiled? Currently, our process is to upload a new LESS file through FTP to the directory, and then just wait for LiveWhale to pick it up and recompile. Sometimes it seems to take a very long time, and as far as I can tell, it’s not a caching issue on the user end.
Hi there,
The short answer to your question is yes—from your web browser’s network inspector, if you locate the /live/resource/css/chain-of-filenames.css file that includes your rendered code, you can open that in a new browser tab and append ?refresh=1 to the end of it to force LW to re-render and cache it. You’ll see the cache date/time at the top of the file in a comment so you can see if it’s taken effect.
To go a bit deeper – LiveWhale should detect updates to the LESS files and auto-recompile, but a few things can make that slower:
(1) If you’re on your production site, you may be viewing web2, which can be ~60sec behind production in theme files. In a browser, you can use a plugin like ModHeader to send “lw-lb-target-node: web01” to always see the web1 node where you’re SFTPing to.
(2) Some SFTP programs seem to be able to update files without always “touching” the system last modified date, which can confuse LiveWhale’s auto-cache-clearing.
(3) Or, if you’re using a file with nested @import statements, sometimes a file change on an included LESS partial may not always trigger LiveWhale to re-render the parent file that includes it.
Hope this helps!
1 Like
I will look into those options. Thank you so much!