Before this commit, the planner section of the settings weren't translated.
This was because the context was not sent along with the search_read that fetches planners data
After this commit, the planner section is correctly translated
OPW 1881092
closes#26766
Usability: remove the Settings tour and include the addition of users
back at the end of others tour. The reasons:
- When someone starts with Project, we don't want to invite him going on
the settings tour (Don't make me think/choose)
- If the user starts with Settings (e.g. out of curisity), he will not
have a great on boarding experience.
- We expect the user to follow the steps in this order 1/ discover
project tasks and, only after, 2/ invite users (he will probably not
invite users before discovering the application)
The drawback is that we have to add "Invite Users" steps on others tour,
but only those for which it has a sense:
- Website, Accounting, eCommerce are typically single-users apps (we
don't need to make him invite people)
- CRM, Project are multi-users apps
1/ The tip should be on the textarea, not on the button.
2/ The access right field on the quick user creation form is confusing.
I propose to put it in "Technical Feature" so that it's not visible for normal users.
3/ dissociate les settings tour from project tour
The ERP managers (users with 'Access Rights' rights) cannot even click on
the Settings app menuitem. Because of 2 things:
- The Dashboard settings is accessing the model ir_module_module. So
we set a groups 'group_settings' on it.
- The Users view is accessing the model ir_module_category to groups
the aggregate and display the settings. So we change the security rules
by giving the access to the group_erp_manager instead of group_settings
- The global rules opn companies was applied to the erp managers. We
splitted this ir.rules into three new ones on portal,public and employee
users to allow the erp managers to access the companies
- Writing on the res_groups was calling the method _update_user_groups_view
in all the cases. This method should be called only when the view was
needed to be modified, i.e. when the category_id is modified for this
group.
Lucas Perais (lpe)