Daily updates from Odoo
Thursday, September 1, 2016
10 changes · master
New functionality added to Odoo
Authorize.Net payments can now be processed directly through a server-to-server flow, improving the checkout and stored-card experience. The update also fixes a warning shown when saving card details, making payment handling smoother for customers and staff.
Original PR description
Task: https://www.odoo.com/web#id=19521&view_type=form&model=project.task&menu_id=3942&action=327 Pad: https://pad.odoo.com/p/r.3X46VshooscHWWIH
Imports can now optionally add new linked records to many-to-many fields instead of replacing the existing list. This helps businesses update relationships in bulk without accidentally removing current links, while preserving the old behavior unless explicitly enabled.
Original PR description
Description of the issue/feature this PR addresses: Allow to pass a value in the context during import in order to allow the addition of new record in many2many field instead of replacing the current value with the imported value: in other words replace [(6, 0, [ids])] by [(4, id1), (4, id2), ...] Current behavior before PR: Import of many2many values always replace the existing values Desired behavior after PR is merged: if update_many2many is True in the context add the values to the existing list while importing else keep the current behavior ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
HTTP 404 errors are now recorded as errors instead of informational messages. This makes missing-page or missing-resource issues easier for teams to spot and investigate quickly.
Original PR description
Description of the issue/feature this PR addresses: We have HTTP-404 error in the log but is not easy to identify because is a logger.info Current behaviour before PR: If you have a HTTP 404 error in your instance you see a `INFO` logger. Desired behaviour after PR is merged: If you have a HTTP 404 error in your instance you see a `ERROR` logger.
This update adds support for authorizing card payments at checkout and capturing the money later, such as when an order ships. It also improves saved-card handling, checkout card saving, and Authorize.net server-to-server payment support, giving businesses more flexible and modern payment workflows.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The CRM experience is made easier to use by showing the Won stage by default and improving the guided tour so users can reach the planner more smoothly. Partner categories are also relabeled as tags, matching how business users understand and use them.
Original PR description
Task: https://www.odoo.com/web#id=28056&view_type=form&model=project.task&action=333&active_id=248&menu_id=4720
Odoo now gives teams clearer visibility into whether customer emails were sent, failed, or bounced directly from the conversation history. The mail system also handles bounced emails more reliably and removes outdated routing behavior, reducing confusion and improving follow-up with customers.
Original PR description
Task: https://www.odoo.com/web?#id=21026&view_type=form&model=project.task&action=333&active_id=248&menu_id=4720
This change ensures sales-related analytic entries are only created for confirmed sales orders, not quotations, completed, or cancelled orders. It helps avoid confusing or inaccurate reporting when expenses or timesheets are linked to orders that should no longer affect sales analytics.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Creating a new product now correctly keeps key details such as barcode, internal reference, cost, volume, and weight. This prevents missing product information at setup time and reduces manual corrections after product creation.
Original PR description
Description of the issue/feature this PR addresses: Issue : https://www.odoo.com/web#id=687065&view_type=form&model=project.issue&action=609&menu_id=4720 Current behavior before PR: - fields barcode, default_code (Internal Reference), standard_price, volume and weight are not saved on create of product template Desired behavior after PR is merged: - Fixed, all these fields will save on creation of product template ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
This change reorganizes how Odoo manages database registries by moving responsibilities into one central Registry component. It is mainly an internal cleanup that should make maintenance easier while preserving existing business behavior.
Original PR description
Move all functionalities of the class `RegistryManager` to the class `Registry`. The major difference in API is that the registry of a database is obtained by calling `Registry(name)`; the latter does not create a new registry instance if it already exists. The other difference is that some class methods have been converted to instance methods.
This update reorganizes how Odoo reads and routes incoming emails, moving shared email parsing logic into common tools. It simplifies maintenance and prepares the mail gateway for future improvements, with little direct impact on day-to-day users.
Original PR description
https://www.odoo.com/web?#id=19524&view_type=form&model=project.task&action=333&active_id=248&menu_id=4720