Skip to Content
This question has been flagged
3 Replies
10682 Rodiniai
Portretas
Fronty

Hello,

We have just started using Odoo and have a hosted instance at odoo.com. Most of us are getting along fine, but there is one user who keeps getting a browser error as soon as they access the server:

Uncaught TypeError: Cannot read property 'current_company' of undefined
https://company.odoo.com/web/content/363-061cc4d/web.assets_common.js:925 
Traceback:
TypeError: Cannot read property 'current_company' of undefined
at Class.start (https://company.odoo.com/web/content/364-e98e153/web.assets_backend.js:487:2746) 
at Class.start (https://company.odoo.com/web/content/364-e98e153/web.assets_backend.js:499:848) 
at Class.prototype.<computed> [as start] (https://company.odoo.com/web/content/363-061cc4d/web.assets_common.js:3860:488) 
at HTMLDocument.<anonymous> (https://company.odoo.com/web:68:40) 
at mightThrow (https://company.odoo.com/web/content/363-061cc4d/web.assets_common.js:914:18) 
at process (https://company.odoo.com/web/content/363-061cc4d/web.assets_common.js:916:89)

She has tried using Chrome, FireFox & Edge but none of them work. She is the only one having problems, other people are working fine with these browsers, so I can't help thinking it's something local on her machine. She's running Windows 10.

Anyone got any ideas?

Portretas
Atmesti
Ibrahim Boudmir

Inspect Element in the browser then tell us what is the error you have in Console section.

Waiting to hear from you.

Portretas
James Dommenick Asaria
Best Answer

Good day guys, Im encountering the same issue. Im currently doing a migration from odoo 12 to 13 and I keep having this error.

Uncaught TypeError: Cannot read properties of undefined (reading 'current_company')
http://localhost:8072/web/content/494862-38c1840/web.assets_common.js:925
Traceback:
TypeError: Cannot read properties of undefined (reading 'current_company')
    at Class.start (http://localhost:8072/web/content/494863-800e0af/web.assets_backend.js:491:2746)
    at Class.start (http://localhost:8072/web/content/494863-800e0af/web.assets_backend.js:503:638)
    at Class.prototype. [as start] (http://localhost:8072/web/content/494862-38c1840/web.assets_common.js:3862:488)
    at HTMLDocument. (http://localhost:8072/web:69:40)
    at mightThrow (http://localhost:8072/web/content/494862-38c1840/web.assets_common.js:914:18)
    at process (http://localhost:8072/web/content/494862-38c1840/web.assets_common.js:916:89)


Portretas
Atmesti
Portretas
Yinon Dev
Best Answer

Has this been solved?
I'm having the same issue, some users can access the site and some get the same error as yours.

** update **

This is an error that is thrown when the user is of type "portal" or "public" and not "internal user".
When changed the user type (Settings -> Users) to internal user it worked.

Portretas
Atmesti
Portretas
Fronty
Autorius Best Answer

The person in our organisation that was having this problem got made redundant, so the issue went away. We never did get to the bottom of it, I didn't know what I was doing with browser debugging.

Portretas
Atmesti