Open
Conversation
bosd
force-pushed
the
19.0-mig-attribute_set
branch
from
d3445da to
963440b
Compare
bosd
force-pushed
the
19.0-mig-attribute_set
branch
from
14d00bc to
6ab37c5
Compare
This was referenced Nov 26, 2025
Author
|
/ocabot migration |
Contributor
|
Hi @bosd. Your command failed:
Ocabot commands
More information
|
Open
New organization : - attribute_set (former base_custom_attribute) - product_attribute_set (former pim_custom_attribute but without menus) - pim (The "PIM application" former pim_base) - pim_attrubute_set (depends on product_attribute_set and adds menus in the PIM application)
And small FIX in _build_attribute_field()
[UPD] README.rst [UPD] README.rst
[UPD] README.rst
…d attribute_set [CHG] add required columns on attributes on attribute set form view attribute_set 13.0.1.0.1
As model_id is referring to non accessible models for common users, set a related field in order to be able to use it in views domains. Moreover, add a domain on attribute_set_id field in attribute owner mixin in order to simplify inherited views.
As attribute view building is accessing ir.model records, do it with sudo. [UPD] Update attribute_set.pot [BOT] post-merge updates [UPD] Update attribute_set.pot
Currently translated at 100.0% (125 of 125 strings) Translation: odoo-pim-16.0/odoo-pim-16.0-attribute_set Translate-URL: https://translation.odoo-community.org/projects/odoo-pim-16-0/odoo-pim-16-0-attribute_set/es/
bosd
force-pushed
the
19.0-mig-attribute_set
branch
5 times, most recently
from
af862b1 to
4b109b0
Compare
added 3 commits
December 21, 2025 14:02
- Fix attribute_set native field updates during module upgrades - Fix Attribute record duplication to ensure unique names - Fix Attribute error where bool has no startswith method - Fix attribute set placeholder handling to improve compatibility - Fix popup attributes view to show more than 2 characters - Fix view styling and other compatibility improvements
bosd
force-pushed
the
19.0-mig-attribute_set
branch
from
4b109b0 to
474ea47
Compare
Author
|
Done, it is now based ontop of the offical 18.0 migration ✨ |
Author
|
/ocabot migration attribute_set |
Contributor
|
Sorry @bosd you are not allowed to mark the addon to be migrated. To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons. If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the |
This was referenced Dec 31, 2025
|
@bosd Could you redo commit history? New language commit was added in v18. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WIP, Should be functional. Commits are a bit of a mess. some fixes should have been backported in the v18.
But various fixes already applied here.
Based upon #225