Daily updates from Odoo
Friday, September 2, 2016
6 changes · master
Resolved issues and error corrections
This update corrects how many Odoo modules label their built-in menus, groups, and related records so they belong to the module that actually provides them. This helps ensure module uninstallations clean up properly and translations are available when languages are installed before optional modules.
Original PR description
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…
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). Just to make @KangOl life easier: - menu_action_currency_form -> account & sales_teams (2 menus) - menu_association -> membership - menu_event_config-> membership - menu_import_crm -> crm - group_hr_user -> hr - group_hr_manager -> hr - group_hr_attendance -> hr (shouldn't it be moved to hr_attendance btw?) - group_hr_attendance_use_pin -> hr_attendance - action_partner_mass_mail -> mail (why is it duplicated?) - group_equipment_manager -> maintenance - menu_association -> membership - menu_marketing_config_association -> membership - menu_mrp_config -> mrp - menu_mrp_root -> mrp - menu_main_pm -> project - menu_project_config_project -> project - menu_project_report -> project - menu_project_general_settings -> project - menu_purchase_root -> purchase - purchase_report -> purchase - menu_aftersale -> sale_stock - menu_invoiced -> sale_stock - menu_action_res_partner_bank_form -> sales_team - menu_sale_report -> sales_teams - sales_team_config -> sales_teams - group_survey_user -> survey - group_survey_manager -> survey - group_website_publisher -> website - group_website_designer -> website - module_category_theme_hidden -> website_theme_install (does it impact theme modules?)
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`Cancelling a product return now correctly restores the link to the next warehouse movement. This helps keep inventory operations consistent and prevents follow-up transfers from being left unassigned.
Original PR description
Task : https://www.odoo.com/web#id=12762&view_type=form&model=project.task&menu_id=3942&action=327 Pad : https://pad.odoo.com/p/r.rLOfjEuqxD2A0f8B
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).