Friday, March 29, 2019
5 changes
Enhancements to existing features
Odoo now avoids recording field-by-field change history when a record is first created, since there is no previous value to compare against. This makes creation messages cleaner and can reduce database work during record creation, while preserving special creation notifications where needed.
Original PR description
*: project, crm, maintenance, helpdesk, It is useless to track fields during create since they have no initial value and future tracking message will show changes on tracked field. We can log a default creation message instead (as it is now if there is no mail_create_nolog context key) This change will implies - less queries when creating record - cleaner creation messages - less occurence of mail_create_nolog ctx key Removing tracking at create could break the creation subtypes mechanism (example: following task creation subtype on project) Instead of using _track_subtype to give a subtype at create, a new _creation_subtype method can be override. If a creation subtype is set on a specific modlel, creation messages will be create by message_post instead of _message_log. We also need to adapt the message_track_post_template in order to keep this feature whithout tracking. Task: #1916916
This change prevents pricelists from being linked to a website that belongs to a different company, reducing configuration errors in multi-company, multi-website setups. It also limits website choices to the relevant company and avoids localization installation failures caused by using the wrong company context.
Original PR description
Before this commit, a pricelist could be easily misconfigured when multi-company and multi-website were both activated. Eg: website 2 is for company 1, create a pricelist and set website 2 and…
Before this commit, a pricelist could be easily misconfigured when
multi-company and multi-website were both activated.
Eg: website 2 is for company 1, create a pricelist and set website 2 and
company 2, it would make no sense and code would not behave as expected.
Now, we prevent this type of misconfiguration by ensuring a pricelist can't
have a website which is from another company than the company set to the
pricelist.
We also filter website in m2o widget to only show company's websites.
Closes #25109
---------------
With this new constraint, l10n module would need to force company:
l10n modules install will change the company currency, creating a pricelist for
that currency. Do not use user's company in that case as module install are
done with OdooBot (company 1).
Step to reproduce:
- Active multi-company and create a new company
- Switch to that company and try to install any l10n module not in EUR or USD
- It will create a new pricelist for that company for that new currency
- It will crash as module install are done as OdooBot which is in company 1.
It will search websites in OdooBot company (self.env.user).
It will then create the pricelist with company 1's website which is
uncompatible with the new company, thus raising the constraint.Blog pages were refreshed to better match the updated look used on forum and event pages, including cleaner cards and improved sidebar styling. The changes also tidy up page structure and social link visuals, making blogs feel more modern and consistent for visitors.
Original PR description
* website Review the blog layouts to - Use cards where necessary to match the forum / event redesign - Use correct bootstrap / HTML + Some minor improvements task-1948882
This update reduces unnecessary activity tracking when new records are created across several business areas. It should improve performance and keep communication histories cleaner, especially for projects and mail-related workflows.
Original PR description
Task: https://www.odoo.com/web#id=1916916&action=333&active_id=1519&model=project.task&view_type=form&menu_id=4720
New records in Helpdesk and HR Appraisals now use simpler creation messages instead of listing tracked field changes that had no previous value. This reduces unnecessary database work, keeps activity histories clearer, and stabilizes a Helpdesk CRM assignment test by making tie-breaking deterministic.
Original PR description
*: helpdesk, hr_appraisal It is useless to track fields during create since they have no initial value and future tracking message will show changes on tracked field. We can log a default creation message instead (as it is now if there is no mail_create_nolog context key) This change will implies - less queries when creating record - cleaner creation messages - less occurence of mail_create_nolog ctx key Removing tracking at create could break the creation subtypes mechanism (example: following task creation subtype on project) Instead of using _track_subtype to give a subtype at create, a new _creation_subtype method can be override. If a creation subtype is set on a specific modlel, creation messages will be create by message_post instead of _message_log. Task: #1916916