-
-
Notifications
You must be signed in to change notification settings - Fork 698
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
[18.0][MIG] website_odoo_debranding: Migration to 18.0 #1065
base: 18.0
Are you sure you want to change the base?
[18.0][MIG] website_odoo_debranding: Migration to 18.0 #1065
Conversation
* Imported last updates from v8 * Adapted to v9 * Renamed to website_odoo_debranding * Updated README
- Relicensed to LGPL. - The template that does the job can be disabled by the admin.
…nment.manage()' Closes OCA#899
[UPD] README.rst Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: website-16.0/website-16.0-website_odoo_debranding Translate-URL: https://translation.odoo-community.org/projects/website-16-0/website-16-0-website_odoo_debranding/ [UPD] README.rst
With website_odoo_debranding installed it was not possible to install enterprise planning. Planning relies on <t t-call="web.brand_promotion_message"> sections which was removed with replacing the o_brand_promotion. [UPD] Update website_odoo_debranding.pot [BOT] post-merge updates
f03bd29
to
5aa5de0
Compare
Hi, I think this PR could be mark as ready. Threre is no breaking change at this point. What do you think? :) |
Just havent had the time to check the failing tests. But this is not related to the module |
The failure is for having this warning:
The workaround is to have an empty dummy test. |
5aa5de0
to
ecaa1e2
Compare
@pedrobaeza ahh many thanks for the hint. Added the dummy test. |
Yes, remove that commit. I think you have added |
ecaa1e2
to
0fa3708
Compare
this is correct. i was not sure how to handle the no-change, so added this commit temporarily. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested it on RunBoat and at first access I see this on the bottom right:
I tried to replicate it, moving on the other site and creating a new one, switching dev mode on/off. In one occasion it appears after changing the site language.
Unfortunately I am not able to reproduce a step sequence that causes this behaviour.
This PR has the |
standard migration