Was debugging a freeflarum site where one user reported being locked out (nojs=1). A browser cache flush / force reload did not fix the problem. The only thing that worked was a server cache flush (php flarum cache:clear
) and a browser flush.
Enabled extensions: ["flarum-approval","flarum-bbcode","flarum-emoji","flarum-english","flarum-flags","flarum-likes","flarum-lock","flarum-markdown","flarum-mentions","flarum-sticky","flarum-subscriptions","flarum-suspend","flarum-tags","flagrow-byobu","sijad-links"]
Settings: custom SMTP settings were used.
Sadly I could not reproduce it on another forum, but I do have the pre- and post admin-xxxxx.js files. Oddly, they are named the same, but are in fact different:
-rw-r--r-- 1 www-data www-data 414634 Dec 2 01:51 assets-nojs/admin-46889923.js
-rw-r--r-- 1 www-data www-data 464971 Dec 2 10:07 assets/admin-46889923.js
My guess:
- certain extension behaviour does not trigger a cache flush, and
- Flarum incorrectly adds unique id's to non-unique files
Would this help?
- always flush server cache upon every admin POST
- use file hash instead of unique idea to generate unique asset filenames