Daily updates from Odoo
Navigate
Branch
Monday, July 24, 2023
17 changes
Enhancements to existing features
The module import wizard now limits the file picker to zip files, matching the only format the import process supports. This reduces confusion and helps users choose the correct file more quickly.
Original PR description
before this commit, in the import module wizard the end user can select any type of file in the upload file field and clicking import it will say only zip format is supported. after this commit, on clicking upload files, only zip files will be shown to the end user to select, which will make easy to select the files from directory
Resolved issues and error corrections
This fix ensures rental stock website tests use pricing and website data from the same company. It prevents inconsistent multi-company test failures, helping keep validation builds reliable without changing customer-facing behavior.
Original PR description
Before this commit, tests were using another pricelist which does not belong to the same as the sale order. This commit archives all pricelists that are not used in this testing suite. Fixes build error 23056
New subscriptions can now generate Stripe payment mandates even when their subscription start date has not been set yet. The system uses the current date as a fallback, reducing setup blockers and helping payments proceed smoothly.
Original PR description
Before this commit, it was not possible to create mandates for subscriptions without a start_date. Now, if the start_date is not yet set, the current date will be used to created the mandate. task-3322020 Fixes #42196
This update prevents an error when installing the Mexican electronic invoicing module. It adds a required hidden field to the payment view so the setup can complete normally without affecting day-to-day screens.
Original PR description
before this commit, there is a traceback on installing l10n_mx_edi module, as the field edi_document_ids is not present in the view and used in attrs after this commit field is added to view with invisible attribute related to: https://github.com/odoo/odoo/commit/e289c4f0868de2ffd4ca011d6d4279f41b3c2a34
Features or functions removed from Odoo
The separate Kenyan payroll benefits module has been folded back into the main Kenyan payroll module, simplifying setup and maintenance. Unused fields were removed, and payslip styling was made more flexible so payroll reports can better reflect configured salary lines.
Original PR description
Before this commit, a module named l10n_ke_hr_payroll_bik
was created in order to implement some new fields in stable.
This commit moves that module back into l10n_ke_hr_payroll and
removes unused fields.
task-3029348Code cleanup and technical improvements
Several Odoo Enterprise apps were adjusted to work with the platform’s new relational data model. This is mainly an internal modernization that helps keep accounting, documents, web studio, and related interfaces reliable as the underlying framework changes.
Original PR description
This PR adapts the code in addons w.r.t. the introduction of the RelationalModel [1]. Main changes that were requested are: - record datapoints no longer always have an "id" key in their data (they still do if the id field is in the view), so we use record.resId instead - the new model is based on fined-grained reactivity, so several components that previously relied on onWillUpdateProps to update their internal state no longer worked. Typically, using the hook "observeRecord" is the way to go now. - specialdata are no longer handled in the model, so the components needing specialData can use the hook "useSpecialData" - more generally, all overrides of models (RelationalModel or KanbanModel) needed to be reworked. Part of task~3179751 [1] odoo/odoo#114024 Co-authored-by: Aaron Bohy <aab@odoo.com> Co-authored-by: FrancoisGe <fge@odoo.com> Co-authored-by: Jorge Pinna Puissant <jpp@odoo.com> Co-authored-by: Pierre Rousseau <pro@odoo.com>
Miscellaneous changes
Since https://github.com/odoo/odoo/commit/fc0464427f268ed58d5f800dfcf40404640c6676 customizing an invoice PDF report leads to a white page. This is because the dynamic t-call in PDF report in not supported by Studio on the customization screen. Forward-Port-Of: odoo/enterprise#44474
Original PR description
Since https://github.com/odoo/odoo/commit/fc0464427f268ed58d5f800dfcf40404640c6676 customizing an invoice PDF report leads to a white page. This is because the dynamic t-call in PDF report in not supported by Studio on the customization screen. Forward-Port-Of: odoo/enterprise#44474
**[FIX] l10n_mx_edi: Fix CacheMiss in _compute_l10n_mx_edi_document_ids** Nightly builds are broken because assigning an empty list on a computed o2m field is considered as a Falsy value by the ORM. **[IMP] l10n_mx_edi: Add tests for 'tax_objected'** Forward-Port-Of: odoo/enterprise#44470
Original PR description
**[FIX] l10n_mx_edi: Fix CacheMiss in _compute_l10n_mx_edi_document_ids** Nightly builds are broken because assigning an empty list on a computed o2m field is considered as a Falsy value by the ORM. **[IMP] l10n_mx_edi: Add tests for 'tax_objected'** Forward-Port-Of: odoo/enterprise#44470
Steps: Install : l10n_lu_hr_payroll and hr_contract_salary Go to (lu) employee contract - Generate Offer and click on it. We get: AttributeError: 'hr.contract.salary.offer' object has no attribute 'contract_type_id' This is because 'contract_type_id' is defined on 'hr.contract.salary.offer' in l10n_be_hr_contract_salary Forward-Port-Of: odoo/enterprise#44467
Original PR description
Steps: Install : l10n_lu_hr_payroll and hr_contract_salary Go to (lu) employee contract - Generate Offer and click on it. We get: AttributeError: 'hr.contract.salary.offer' object has no attribute 'contract_type_id' This is because 'contract_type_id' is defined on 'hr.contract.salary.offer' in l10n_be_hr_contract_salary Forward-Port-Of: odoo/enterprise#44467
Issue: ------ When we go to a recurring product on ecommerce and want to go to another recurring product, we stay on the same product. Cause: ------ The `t-cache` key is overwritten and not added. Solution: --------- Syntax correction for key addition on `t-cache` attribute. `<attribute name="t-cache" add="expr_py" separator=","/>` opw-3420753 Forward-Port-Of: odoo/enterprise#44381
Original PR description
Issue: ------ When we go to a recurring product on ecommerce and want to go to another recurring product, we stay on the same product. Cause: ------ The `t-cache` key is overwritten and not added. Solution: --------- Syntax correction for key addition on `t-cache` attribute. `<attribute name="t-cache" add="expr_py" separator=","/>` opw-3420753 Forward-Port-Of: odoo/enterprise#44381
Create a delivery operation with scheduled datetime close to the tz boundary Example for UTC+2 26-06-23 00:20:00 Print Delivery Guide SII DTE 52 (CL) Issue: In the pdf report date will be 25-06-23 opw-3264251 Forward-Port-Of: odoo/enterprise#44370 Forward-Port-Of: odoo/enterprise#43170
Original PR description
Create a delivery operation with scheduled datetime close to the tz boundary Example for UTC+2 26-06-23 00:20:00 Print Delivery Guide SII DTE 52 (CL) Issue: In the pdf report date will be 25-06-23 opw-3264251 Forward-Port-Of: odoo/enterprise#44370 Forward-Port-Of: odoo/enterprise#43170
[REF] account_reports: html, css and usability improvements This pr continues the refactoring of account_reports by mainly simplifying the html and css. The goal was to make the html and css of account reports in general more stable, more customizable and easier to maintain. Also, we wanted to refresh the look of account reports to make it cleaner and closer to the milk style. - The css got an overall redesign. The styling is now based mostly on the figure_type of the column. That allow
Original PR description
[REF] account_reports: html, css and usability improvements This pr continues the refactoring of account_reports by mainly simplifying the html and css. The goal was to make the html and css of…
[REF] account_reports: html, css and usability improvements This pr continues the refactoring of account_reports by mainly simplifying the html and css. The goal was to make the html and css of account reports in general more stable, more customizable and easier to maintain. Also, we wanted to refresh the look of account reports to make it cleaner and closer to the milk style. - The css got an overall redesign. The styling is now based mostly on the figure_type of the column. That allows to maintain a more consistent look a lot easier. - Each report can now be customized by the use of the 'client_css_custom_class' in '_get_custom_display_config' and the data-expression_label on each table cell. This allows to target specific reports and/or specific columns without it affecting other reports/columns. It also allows to have completely different styling for each report if needed. - There is now the possibility to force a currency in an expression field directly in the report declaration. It can be done by creating another expression that starts with '_currency_' and then the name of the label to force the currency. For example, for expression with label 'a' we create a new expression with '_currency_a'. - To make report columns more 'standard' we introduce a new function '_build_column_dict' to build them. - There is a new component 'AccountReportEllipsis' which handles the ellipsis on table cells in an account_report. It will hide the overflowing text and will create a popover next to it with the whole text. It can be customized with the number of characters to be shown. _ Overall html and css clean up where a lot of unused 'noise' was removed making it easier to understand, maintain and improve. - Blank_if_zero is back to False default. The zero values are now shown in a muted gray color. - (and some more little misc changes) Task-id 3251726 Forward-Port-Of: odoo/enterprise#43885
Issue: Even if Employee Editing is deactivated in the employee settings, the user can edit the relationship from my profile. Fix: In this commit, we have fixed If Employee Editing is Deactivated then the Relationship is readonly in my profile. Step: - Install l10n_in_hr_payroll module - Create user (without any access) with Employee - Got to employee Setting - Deactivated Employee Editing - Login without any access user - Go to My Profile - Chec
Original PR description
Issue: Even if Employee Editing is deactivated in the employee settings, the user can edit the relationship from my profile. Fix: In this commit, we have fixed If Employee Editing is Deactivated then the Relationship is readonly in my profile. Step: - Install l10n_in_hr_payroll module - Create user (without any access) with Employee - Got to employee Setting - Deactivated Employee Editing - Login without any access user - Go to My Profile - Check relationship task-3434020 Forward-Port-Of: odoo/enterprise#44440
Steps to reproduce the bug: - change "Quality Tests" decimal accuracy to 4 digits - Go to quality check - Select “Control per”: product Problem: The “Quantity Tested” is in 2 digits instead of 4 opw-3425294 Forward-Port-Of: odoo/enterprise#44335
Original PR description
Steps to reproduce the bug: - change "Quality Tests" decimal accuracy to 4 digits - Go to quality check - Select “Control per”: product Problem: The “Quantity Tested” is in 2 digits instead of 4 opw-3425294 Forward-Port-Of: odoo/enterprise#44335
With a Belgian company setup Create an intracommunity invoice so that it shows on the EC Sales List Issue a credit note that fully reverses the invoice The report shows a blank line rather than saying zero opw-3301307 Forward-Port-Of: odoo/enterprise#43723
Original PR description
With a Belgian company setup Create an intracommunity invoice so that it shows on the EC Sales List Issue a credit note that fully reverses the invoice The report shows a blank line rather than saying zero opw-3301307 Forward-Port-Of: odoo/enterprise#43723
Using Spain's code for Canary Islands does not work with DHL. They use a specific code: "IC" OPW-3334468 Forward-Port-Of: odoo/enterprise#44378
Original PR description
Using Spain's code for Canary Islands does not work with DHL. They use a specific code: "IC" OPW-3334468 Forward-Port-Of: odoo/enterprise#44378
Steps to reproduce: - Open Documents on small screen - Selected a record (and close the Inspector if open) - Scroll until a stacked kanban card passes at the bottom of the screen ==> the "x document selected" button is under the stacked kanban card This commit fixes it by defining a base z-index for kanban stack used to calculate the related elements' z-index (document selected button, kanban stack's layers...) Forward-Port-Of: odoo/enterprise#43742
Original PR description
Steps to reproduce: - Open Documents on small screen - Selected a record (and close the Inspector if open) - Scroll until a stacked kanban card passes at the bottom of the screen ==> the "x document selected" button is under the stacked kanban card This commit fixes it by defining a base z-index for kanban stack used to calculate the related elements' z-index (document selected button, kanban stack's layers...) Forward-Port-Of: odoo/enterprise#43742