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

[18.0][MIG] product_multi_company: Migration to 18.0 #711

Closed

Conversation

BertVGroenendael
Copy link

@BertVGroenendael BertVGroenendael commented Oct 24, 2024

No description provided.

pedrobaeza and others added 30 commits October 23, 2024 15:56
==========================================
Product permissions for discrete companies
==========================================

This modules allows to select in which of the companies you want to use each
of the products.

Installation
============

This module uses the post and uninstall hooks for updating default product
template security rule. This only means that updating the module will not
restore the security rule this module changes. Only a complete removal and
reinstallation will serve.

Usage
=====

On the product form view, go to the "Information" tab, and put the companies
in which you want to use that product. If none is selected, the product will
be visible in all of them. The default value is the current one.
* Rename manifest
* Change openerp references to odoo
* Bump version
* Add pragma no cover
* Edit security of product employee to allow writes (in tests)
* Fix permissions in tests
* Fix domain & add test
* Implement base_multi_company on product_multi_company
* Add related cols for product variant
…figurator

When this module is integrated with `product_variant_configurator`, tests fail because the latter makes some black magic on the `name` field.

I switch the tests to rely on the `description_sale` field instead, which isn't touched by that module, and is also a field delegated from the related `product.template`.

BTW it doesn't make sense to modify provided permissions on a test that checks access errors, so instead I switched them to use users in a group that should have access in production.

@Tecnativa TT27288
Currently translated at 100.0% (4 of 4 strings)

Translation: multi-company-13.0/multi-company-13.0-product_multi_company
Translate-URL: https://translation.odoo-community.org/projects/multi-company-13-0/multi-company-13-0-product_multi_company/es/
In order to extend testing, a common class is necessary to avoid code
duplication.
…ect context

As some default values can come from current company (e.g.: main one), change context
when creating.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: multi-company-15.0/multi-company-15.0-product_multi_company
Translate-URL: https://translation.odoo-community.org/projects/multi-company-15-0/multi-company-15-0-product_multi_company/
Currently translated at 100.0% (7 of 7 strings)

Translation: multi-company-15.0/multi-company-15.0-product_multi_company
Translate-URL: https://translation.odoo-community.org/projects/multi-company-15-0/multi-company-15-0-product_multi_company/es/
Remove dependency to stock and its overwritten fields, this logic should
go  if ever done in a separate module named: product_multi_company_stock

TT48972
oca-ci and others added 9 commits October 23, 2024 15:56
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: multi-company-16.0/multi-company-16.0-product_multi_company
Translate-URL: https://translation.odoo-community.org/projects/multi-company-16-0/multi-company-16-0-product_multi_company/
The description shouldn't be overriden in any child module, as it's a traversal data that then changes all the translations.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: multi-company-16.0/multi-company-16.0-product_multi_company
Translate-URL: https://translation.odoo-community.org/projects/multi-company-16-0/multi-company-16-0-product_multi_company/
Currently translated at 100.0% (4 of 4 strings)

Translation: multi-company-16.0/multi-company-16.0-product_multi_company
Translate-URL: https://translation.odoo-community.org/projects/multi-company-16-0/multi-company-16-0-product_multi_company/it/
@BertVGroenendael BertVGroenendael force-pushed the 18.0-mig-product_multi_company branch 4 times, most recently from 580d707 to 5004f12 Compare October 24, 2024 08:41
Copy link
Member

@chienandalu chienandalu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rebase from branch 17.0 as it's just been merged with all the last features and fixes #625

@BertVGroenendael
Copy link
Author

In the last commits, I redid the migration starting from the 17.0 branch.

Comment on lines +14 to +18
def post_init_hook(env):
hooks.post_init_hook(
env,
"product.product_comp_rule",
"product.template",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the last commits, I redid the migration starting from the 17.0 branch.

Are you sure, this changes should be already in v17...

"version": "16.0.1.0.1",
"version": "18.0.1.0.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the last commits, I redid the migration starting from the 17.0 branch.

Are you sure? 🤔

@BertVGroenendael BertVGroenendael deleted the 18.0-mig-product_multi_company branch November 26, 2024 07:50
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

Successfully merging this pull request may close these issues.