Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

web module error #107

Closed
pankk opened this issue Sep 26, 2014 · 7 comments
Closed

web module error #107

pankk opened this issue Sep 26, 2014 · 7 comments

Comments

@pankk
Copy link
Member

pankk commented Sep 26, 2014

Hi,

I'm getting an error (see below) when using an upgraded database upgraded using the c1b9ad1 commit. I think I'm using the wrong (too new) revision of Odoo. I've tried multiple revisions of Odoo:
4f5cc00: as mentioned at #1 but this seems dated and gives me an error on report/modules/report.py;
932ecccc: (Odoo 8.0) initially gives a ir_ui_view.action does not exist error but works after an update all, but I get a javascript web module error;
e4521e4 (older Odoo 8.0): works without the update all but I get the same web error).
Which revision of Odoo should I use?

The error I'm getting:
From sales->customers in kanban view click on a partner pops up:
Uncaught TypeError: Cannot read property 'constructor' of undefined
http://0.0.0.0:8068/web/js/web.assets_backend/ce41694:2840
(found this in addons/web/static/lib/src/js/pyeval.js around line 719)

and:

Uncaught Error: QWeb2 - template['FieldRadio']: Runtime Error: TypeError: Cannot read property '1' of undefined
http://0.0.0.0:8068/web/js/web.assets_common/08701fd:1020
(found this in addons/web/static/lib/qweb/qweb2.js around line 48

@pankk
Copy link
Member Author

pankk commented Oct 16, 2014

This problem is solved by migrating mail.

@pankk pankk closed this as completed Oct 16, 2014
hbrunn pushed a commit to hbrunn/OpenUpgrade that referenced this issue Oct 17, 2014
[MOV] [RENAME] project_mrp -> sale_service
@martintamare
Copy link

Could you elaborate on how to solve the problem ?

@pankk
Copy link
Member Author

pankk commented Aug 1, 2016

@martintamare IIRC the mail module did not have migration scripts at the moment of opening this issue, they were added a few weeks later, so you should not run into the same issue as above anymore using a recent version of OpenUpgrade. Have a look at the mail migration scripts, they might hold a clue to solving the errors you are getting.

@martintamare
Copy link

martintamare commented Aug 1, 2016

Here is what fixed the issue for me using raw postgresql (ugly but efficient ^^):
update res_partner set notify_email ='always' where notify_email='none';

The problem was present when clicking on a res.partners in the list view -> I then focus on the res.partner table and see the constraint there. none was not supposed to be in notify_email :)

@pankk
Copy link
Member Author

pankk commented Aug 2, 2016

@martintamare Thanks for sharing your solution. Maybe I don't fully understand the problem, and I'm not sure to which version you are migrating, but 'none' should be a valid option for that field (e.g. https://github.com/odoo/odoo/blob/master/addons/mail/models/res_partner.py#L21).

@martintamare
Copy link

We started with openrp 7.0 then updating to odoo 8.0 using OCA.
Since the migration, we had this issue. Debugging the JS is a real pain so maybe that is not the correct fix.
We had a dirty installation with plenty of old module, I clean it all, let's see where this is leading us ;)
Anyway I can't reproduce the issue anymore, so ... :)

@alesisjoan
Copy link

Had a similar problem migrating 7.0 to 8.0.

The field notification_email_send is 'comment' while 8.0 accepts as 'always'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants