Missing staticfiles manifest entry for 'bootstrap4/css/bootstrap.min.css'

500 views
Skip to first unread message

eyti...@gmail.com

unread,
May 4, 2021, 7:07:48 PM5/4/21
to oTree help & discussion
Hi everyone,

when starting my app on a production server (either locally or on heroku) I keep getting this error message before the login page shows up:

2021-05-04T22:52:26.633397+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.7/site-packages/django/contrib/staticfiles/storage.py", line 420, in stored_name2021-05-04T22:52:26.633398+00:00 app[web.1]: raise ValueError("Missing staticfiles manifest entry for '%s'" % clean_name)2021-05-04T22:52:26.633398+00:00 app[web.1]: ValueError: Missing staticfiles manifest entry for 'bootstrap4/css/bootstrap.min.css'

This error does not show up in the debug mode. I am now using otree 3.3.11, but I also had the problem with an earlier version. Does anyone have an idea how to solve that?

Thank you in advance,
Markus

eyti...@gmail.com

unread,
May 5, 2021, 8:18:20 AM5/5/21
to oTree help & discussion
update: the error disappears when I update to otree 5, but since this is otree lite, a few other things do not work there. Therefore, I need it to run on the "full" version, preferable otree 3.3.x. Switching back to this version also lets the error reappear....

Chris @ oTree

unread,
May 5, 2021, 9:44:26 AM5/5/21
to oTree help & discussion
Are you deploying through oTree Hub? That can prevent certain common mistakes.

eyti...@gmail.com

unread,
May 5, 2021, 11:41:24 AM5/5/21
to oTree help & discussion
Thank you - it works now.

After checking the logs i saw that the difference must have been the collectstatics. In an earlier (failed) build, the logs told me to disable collectstatic, which i did back then - without knowing why... Afterwards deploying worked, but the app didnt run. Now, after checking the otree hub log, I switched collectstatic back on and also tried deploying through github again and now it works. (I guess I had changed other stuff in my code in the meantime which must have affected collectstatic to not be a problem anymore...)

For future projects, can you tell why sometimes disabling collectstatic is recommended? While it might allow the build to be successful, doesnt that ultimately lead to some static filed not being able to call when running the app?
Reply all
Reply to author
Forward
0 new messages