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

[17.0][MIG] attribute_set: Migration to 17.0 #175

Open
wants to merge 47 commits into
base: 17.0
Choose a base branch
from

Conversation

damcar
Copy link

@damcar damcar commented Dec 5, 2023

No description provided.

clementmbr and others added 30 commits December 4, 2023 13:33
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()
…d attribute_set

[CHG] add required columns on attributes on attribute set form view
[UPD] README.rst

[UPD] README.rst

[ADD] icon.png

Apply dotfiles

[UPD] Update attribute_set.pot
[UPD] README.rst
[UPD] Update attribute_set.pot
[UPD] Update attribute_set.pot

[UPD] README.rst
When you define an attribute as a select field and add a related model,
you have the option to "Load attribute options".

On this wizard, an "option_ids" dummy field is created via
fields_view_get.

This change deletes option_ids from create (once the options are created) and read
menu items are visible only for two levels
sbejaoui and others added 16 commits December 4, 2023 13:33
…ss data (tree/search...)

Use get_view() to get the view_type directly. Moreover, this will allow to test it through
odoo.tests.Form().

Add attribute_set_id field in test form (as it should be included in inherited views
If user is not in the base.group_erp_manager group, the value_ref field
selection function will be computed without access rights on ir.model.
So, hide the field for users not in that group.
Add all the attributes defined for the model into the list of fields to load to display the form view. Wihout this change a JS error occurs when displaying the form view of a x2many field for a model defining attributes. The origin of the error comes from the the get_views method which is called for the type 'form' only. In this case it's important to add all the custom attributes to the list of fields defined on the model for the view. When the same method is called without restriction it will load all the views. Since odoo include all the fields defined on the model for the search view, the error doesn't occur when using the form view from a menu action.
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.
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/
@damcar damcar mentioned this pull request Dec 5, 2023
1 task
Copy link

github-actions bot commented Apr 7, 2024

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Apr 7, 2024
@github-actions github-actions bot closed this May 12, 2024
@rvalyi rvalyi reopened this May 12, 2024
@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label May 19, 2024
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.