Daily updates from Odoo
Friday, September 2, 2016
17 changes · master
New functionality added to Odoo
A new module category was added to organize GitHub-related integration connectors alongside Discuss-style modules. This helps users and administrators find and manage these connector modules more easily as the integration area expands.
Original PR description
[ADD]: added a new module for connectors(list of all discuss type module). Task: https://www.odoo.com/web?#id=19545&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.rMlx5SNEK1Dm59pP
This change adds more automated checks around bank reconciliation, including multi-currency scenarios. It helps reduce the risk of accounting issues reaching users by catching problems earlier during development.
Enhancements to existing features
This update removes unnecessary code evaluation in the stock product logic, making the implementation simpler and slightly more efficient. It also includes an administrative CLA update for a contributor, with no expected change for everyday users.
Original PR description
**Description of the issue/feature this PR addresses:** Improves code quality and performance **Current behavior before PR:** eval + 2 explicit casts **Desired behavior after PR is merged:** code clean and good perfs ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Because in this file eval is unnecessary.
The website quotation feature has been migrated to Odoo's newer internal framework. This should make the feature easier to maintain and reduce duplicated or outdated backend elements without changing the core customer-facing quoting workflow.
Original PR description
task: https://www.odoo.com/web#id=12132&view_type=form&model=project.task&action=327&menu_id=5200 pad: https://pad.odoo.com/p/r.19581cae2884b8b309d2b3153792a804 ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The event sales module was updated to use Odoo's newer internal framework, helping keep the feature easier to maintain and compatible with ongoing platform improvements. This mainly affects how event-related products, sales orders, registrations, and demo data are handled behind the scenes, with limited direct change for everyday users.
Original PR description
...py) to new API - Task: https://www.odoo.com/web#id=12010&view_type=form&model=project.task&action=333&active_id=131 - Pad: https://pad.odoo.com/p/r.Hddf0qvcf9AJY1fL
This update standardizes wording in the payment area to make labels or messages clearer and more consistent. It is a small usability improvement that helps reduce confusion for users working with payment configuration or flows.
Original PR description
@dbo-odoo check this.
Resolved issues and error corrections
This fixes an issue where boolean fields written as text, such as "False" or "0", could be incorrectly treated as true during XML data loading. The change helps ensure imported or demo records reflect the intended active/inactive or yes/no settings.
Original PR description
Description of the issue/feature this PR addresses:
Process boolean value where is used without a eval
e.g.
``` xml
<?xml version='1.0' encoding='UTF-8'?>
<odoo>
<record id="res_partner_demo_01" model="res.partner">
<field name="name">Test demo 01</field>
<field name="active">False</field>
<field name="supplier">0</field>
<field name="customer" eval="False"/>
</record>
</odoo>
```
Current behaviour before PR:
`<field name="active">False</field>` Processed like as a `True`
`<field name="supplier">0</field>` Processed like as a `True`
`<field name="customer" eval="False"/>` Processed like as a `False`
Desired behaviour after PR is merged:
`<field name="active">False</field>` Processed like as a `False`
`<field name="supplier">0</field>` Processed like as a `False`
`<field name="customer" eval="False"/>` Processed like as a `False`Customers will no longer receive the internal notification that their quotation was viewed. The notification is now treated as an internal note, so only relevant salespeople following the document are informed.
Original PR description
Description of the issue/feature this PR addresses: - "Quotation viewed" notification should not be received by customer Task:https://www.odoo.com/web#id=26662&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad:https://pad.odoo.com/p/r.f4e9d33a8dac45aed936a6708704a391 Current behavior before PR: - This notification "Quotation viewed by customer" is received by the customer. Desired behavior after PR is merged: - This notification "Quotation viewed by customer" shouldn't be received by the customer and only the salesman who follow the notes will get it. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix moves the product purchasing option back to the core Product app so it is available where other apps, such as Accounting, expect it. This prevents missing-setting issues for businesses that use product and accounting features without installing Purchase.
Original PR description
The 'purchase_ok' field has been moved into the 'purchase' module in rev https://github.com/odoo/odoo/commit/e945b86d5a61e53a9104ab6cc4ed4a1c060587e4 and removed from 'product' module in rev https://github.com/odoo/odoo/commit/fee03009cfcc41d108a79a2380912f21bc825d77 to fix a duplicated field. But it should actually stay only in 'product' module because the field is needed in the 'account' module which doesn't depend of 'purchase'. So to fix it we set back the 'purchase_ok' field in the product module as it was originally in the rev https://github.com/odoo/odoo/commit/e23e018285b17450af97cf93165704926f8248db
This update corrects records that were incorrectly registered as belonging to the core Base app instead of the app that created them. This helps ensure apps uninstall cleanly and translations are kept when languages are installed before those apps.
Original PR description
cf odoo/odoo#12812 Several modules defines records with the external ID `base.foo_bar` while it is created inside this module (typically menus and groups). While there is no technical reasons to do so but this may introduce issues: - these records will not be deleted during uninstall - if a language is loaded before the installation of the module, it won't be translated The uninstallation will only remove the records with an external id linked to this module (these would only be removed when removing base). Installing a language before the module will drop the translations not linked to an existing external id (as it can not be resolved).
Code cleanup and technical improvements
This change updates the system’s internal framework name from “openerp” to “odoo” across the codebase. It helps keep the product’s technical foundation aligned with the Odoo brand while preserving existing business functionality.
Original PR description
- Rename the module - Adapt imports in the framework - Adapt import hooks
The website recruitment app has been migrated to Odoo's newer application framework. This helps keep the hiring website functionality maintainable and aligned with current platform standards, with no major change expected for end users.
Original PR description
Task : https://www.odoo.com/web/#id=12028&view_type=form&model=project.task&menu_id=3942&action=327 Pad : https://pad.odoo.com/p/r.CFZ51hLERFpk5s06
The account budgeting module was migrated to Odoo's newer internal framework and its files were reorganized. This should make the budgeting feature easier to maintain and test, while preserving the existing business functionality for users.
Original PR description
Task: https://www.odoo.com/web?#id=12160&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.3425f60cbab97845a13fcc165ff3657d
The CRM partner assignment module was updated to Odoo's newer internal framework while keeping its business purpose intact. This should make the module easier to maintain and more reliable for future improvements, with minimal direct impact on everyday users.
Original PR description
Task: https://www.odoo.com/web#id=12139&view_type=form&model=project.task&action=327 Pad: https://pad.odoo.com/p/r.fPuJnMpZkc0rcB75
The Gengo translation module was reorganized and migrated to Odoo's newer internal framework. This helps keep the translation integration maintainable and aligned with current platform standards, with limited expected impact on day-to-day users.
Original PR description
Task: https://www.odoo.com/web#id=12209&view_type=form&model=project.task&menu_id=3942&action=327 Pad: https://pad.odoo.com/p/r.4YJMn6R8itJDcfnQ
The point of sale loyalty module has been reorganized and migrated to Odoo's newer application framework. This keeps loyalty features maintainable and aligned with current platform standards without introducing a major functional change for users.
Original PR description
Task: https://www.odoo.com/web#id=13731&view_type=form&model=project.task&action=327 Pad: https://pad.odoo.com/p/r.NmkjQTXj345Cnydy
This update aligns several business flows with recent platform changes by removing outdated workflow calls. It helps keep sales, purchasing, accounting, subscriptions, and portal-related processes compatible and reduces the risk of errors from obsolete automation hooks.
Original PR description
- adaptation to removal of workflows in community modules. (PR: https://github.com/odoo/odoo/pull/13103 ) - correction of already removed workflow calls. (purchase.order, sale.order)