-
-
Notifications
You must be signed in to change notification settings - Fork 700
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
[13.0][MIG] utm #2258
[13.0][MIG] utm #2258
Conversation
I think need to merge mail.mass_mailing.campaign and utm.campaign models |
a2071c9
to
373ec61
Compare
Thanks @kos94ok-3D , it slipped my mind. |
Yes, in v12, |
Then the code should be more sophisticated (I will check any way this later). |
yeah, I am working on it |
d0c7739
to
5c5e738
Compare
It's ready. @kos94ok-3D could you review again? :) |
5c5e738
to
5027c1a
Compare
Looks good. Just code review. |
utm does not depend on mass_mailing so scripts fail when mass_mailing is not installed previously 😱 |
It shouldn't. Please put the stack trace that supports your affirmation. |
This is the stack trace:
The renames for model, table and xmlid are not executed (that is correct), but then it fails when upgrading the module. It is weird because it tries to read a table before creating it. I will update this comment with my findings. |
It shouldn't fail, as Odoo will create the table for you in most cases. |
I think the problem is Odoo defines a relation to utm_stage https://github.com/odoo/odoo/blob/13.0/addons/utm/models/utm.py#L27 before defining the model https://github.com/odoo/odoo/blob/13.0/addons/utm/models/utm.py#L51 so no issue with Openupgrade Edited: Confirmed. It does not fail if I move that code upwards. Thank you @pedrobaeza |
Migration scripts of
utm
.--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr