-
-
Notifications
You must be signed in to change notification settings - Fork 273
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
[MIG] base_dav: Migration to 17.0 #269
base: 17.0
Are you sure you want to change the base?
Conversation
Currently translated at 100.0% (62 of 62 strings) Translation: server-backend-17.0/server-backend-17.0-base_user_role Translate-URL: https://translation.odoo-community.org/projects/server-backend-17-0/server-backend-17-0-base_user_role/es/
Currently translated at 100.0% (62 of 62 strings) Translation: server-backend-17.0/server-backend-17.0-base_user_role Translate-URL: https://translation.odoo-community.org/projects/server-backend-17-0/server-backend-17-0-base_user_role/it/
Currently translated at 100.0% (11 of 11 strings) Translation: server-backend-14.0/server-backend-14.0-base_user_role_company Translate-URL: https://translation.odoo-community.org/projects/server-backend-14-0/server-backend-14-0-base_user_role_company/it/
Issue found on logout / relogin. The user groups were applied correctly, but the main menu showed apps the user did not have access to. This was related to the menu caching mechanisn, that was disabled here.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: server-backend-14.0/server-backend-14.0-base_user_role_company Translate-URL: https://translation.odoo-community.org/projects/server-backend-14-0/server-backend-14-0-base_user_role_company/
Currently translated at 90.9% (10 of 11 strings) Translation: server-backend-14.0/server-backend-14.0-base_user_role_company Translate-URL: https://translation.odoo-community.org/projects/server-backend-14-0/server-backend-14-0-base_user_role_company/it/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: server-backend-16.0/server-backend-16.0-base_user_role_company Translate-URL: https://translation.odoo-community.org/projects/server-backend-16-0/server-backend-16-0-base_user_role_company/
Currently translated at 100.0% (8 of 8 strings) Translation: server-backend-16.0/server-backend-16.0-base_user_role_company Translate-URL: https://translation.odoo-community.org/projects/server-backend-16-0/server-backend-16-0-base_user_role_company/es/
Hi, @dreispt. Copying the commit from 11.0 and adding it to this branch is very complex for me, so is it okay if I make a new PR with an 11.0 history for this module, and then we can close this one? |
@jaydeep32 Did you try the migration recipe, replacing 15.0 with 11.0? |
Yes, I have, but like in my current branch if I make this, it makes many conflicts with new module changes, making it harder to resolve. However, it would work well if I created a new branch and then did this. So this is why I asked if I could make a new branch and PR. |
@jaydeep32 Yes, you should use the recipe to create a new clean branch, and after that add your migration changes. |
Co-authored-by: Yannick Vaucher <[email protected]>
…rver-backend into 17.0-mig-base_dav
Hello @dreispt Now is it ok? I have added those commits from 11.0 to this one. |
@@ -19,6 +20,6 @@ | |||
"security/ir.model.access.csv", | |||
], | |||
"external_dependencies": { | |||
"python": ["radicale"], | |||
"python": ["radicale==2.1.12"], |
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.
Can this be >= ?
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.
Here, I use this specific module version because this module's code is only compatible with this 2.1.12 or older version of radical.
If you check this #254 issue here, @AquaMCU has mentioned that he is having this strange error in the log,
so I solved that by changing the module version to radicale==2.1.12.
Also, if possible, can we add @AquaMCU to the discussion since he is the one who has migrated the module?
Actually, he was not able to create PR, so I simply made that for him
def eval(self): | ||
if not self: | ||
return self.env["unknown"] | ||
self.ensure_one() | ||
self = self.with_user(SUPERUSER_ID) |
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.
This raises security concerns, why is this required?
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.
@jaydeep32 This doesn't look right. Why are there commits specific to the base_user_role_company module? I second @dreispt 's comment that you need to start fresh with a clean local folder and follow the steps in the migration documentation.
@jaydeep32 Great work, you made it! |
@amh-mw You're right. I suggest you fetch my branch, |
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.
thanks for this PR.
I thinks some ACL are missing for http://oca-server-backend-17-0-pr269-360893ee9167.runboat.odoo-community.org/web?debug=1#id=1&cids=1&menu_id=65&action=77&model=dav.collection&view_type=form
mostly impossible to configure this in the UI |
Should we move to #276 ? |
Is there any progress on it? Maybe even upgrading it to Odoo 18? Can we sponsor this? |
Syncing from upstream OCA/server-backend (12.0)
To install and use this module, use the right version of
radicale==2.1.12
python package.This PR for this #254