It seems the css for a sub can only be changed once, further changes don't seem to take effect.
Comments (8)
Want to leave a comment?
Sort by: Best
It seems the css for a sub can only be changed once, further changes don't seem to take effect.
Want to leave a comment?
Success
Info
Warning
Error
this is a production-only bug so I'll have to fix in prod. I'll let you know when it's fixed.
Epic, looking forward to it.
This is probably that weirdest production bug I've ever encountered. It seems that these files are being cached. So you ARE replacing these files, the server-side cache needs to be cleared before it works. wtf
Would it make sense for the custom css to be dynamic loaded then? It's an extra api call, but should solve the issue and would allow people to block custom css too.
Right now the custom CSS is being parsed and checked if it's valid, with some custom validation rules I added like no URLs, then saved. The problem is that ALL user-uploaded files are being cached, for hours it seems. Even things like avatars. So I need to fix this. I'm GUESSING laravel octane is causing the issue but I can't find anyone else with this issue.
It seems that it is possible to programatically clear/update the cache, you could do a task that is run every 5 minutes to update the cache.
Programatically clear the cache: https://tinkerwell.app/blog/laravel-caches-and-all-ways-to-clear-them
I'll take a look