Some of our users, when accessing the profile of Odoo, see only a white screen and nothing else.
Below options tried
1) Clear the cache and cookie
2) Tried from different browser
3) Regenerate Assets Bundles
4) Restart odoo service
What could it be? And how to solve this?
once you are in login page
your url looks like http://ip:port/web
change it to
http://ip:port/web?debug=assets
it will work then go to developper icon in top right click on it then clik on regenerate assets bundle the ur problem is fixed
Thank you! That solved it for me with odoo 17 CE.
Open inspect in your browser and see in console. if any error then solve it. like missing some abc.js file or etc..
| 関連投稿 | 返信 | ビュー | 活動 | |
|---|---|---|---|---|
|
3
2月 24
|
2904 | ||
|
0
1月 24
|
2609 | ||
|
2
3月 24
|
7463 | ||
|
0
3月 22
|
3928 | ||
|
|
0
2月 24
|
2867 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
Example with console log https://prnt.sc/GfsgOqfapypn
Also I think this is because of this error:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/odoo/addons/base/models/ir_http.py", line 237, in _dispatch
result = request.dispatch()
File "/usr/lib/python3/dist-packages/odoo/http.py", line 687, in dispatch
result = self._call_function(**self.params)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 359, in _call_function
return checked_call(self.db, *args, **kwargs)
File "/usr/lib/python3/dist-packages/odoo/service/model.py", line 94, in wrapper
return f(dbname, *args, **kwargs)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 348, in checked_call
result = self.endpoint(*a, **kw)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 916, in __call__
return self.method(*args, **kw)
File "/usr/lib/python3/dist-packages/odoo/http.py", line 535, in response_wrap
response = f(*args, **kw)
File "/usr/lib/python3/dist-packages/odoo/addons/bus/controllers/main.py", line 28, in poll
raise Exception("bus.Bus unavailable")
Exception
Check the browser console and see whether you get some hints over there. It may be caused by JS changes.
Had the same issue. Safari and Chrome app. Fixed itself by updating to last ios version.