aikozijlemans this happens when public/assets/forum.js
cannot be loaded. And a common reason this exists is because that file cannot be created.
When flarum starts/handles a request it will check whether public/assets/rev-manifest.json
exists and whether that file is up to date. If it does not exist or is outdated Flarum will attempt to automatically recompile all javascript of itself and any enabled extension and create the files public/assets/forum.js
and public/assets/forum-en.js
.
If these files are not created you will see the error you are reporting. Usually not being able to write those files is due to incorrect file permissions - the web user (nginx or fpm) - is unable to write the necessary files into public/assets
.
- I'm trying to hit your URL, I'm not sure something is wrong with your DNS but I'm getting a redirection issue. Can you post your nginx configuration?
- Another issue I'm seeing is that the js/css is being loaded with URL
public/index/assets
, this is incorrect. Can you provide the output for ls -la public/assets
to see whether the assets are compiled and available? If that is the case then the issue lies with the nginx rewriting rules.