Daily updates from Odoo
Tuesday, May 26, 2020
10 changes · master
Security fixes and vulnerability patches
Sensitive values such as passwords, tokens, PINs, and SMS verification tokens are now stored using a dedicated secret field across several Odoo apps. This reduces the risk of unauthorized viewing by making these values visible only to superusers while remaining usable for configuration and integrations.
Original PR description
Community branch: https://github.com/odoo/odoo/pull/47103 Passwords, tokens, pins and other secret values have always been stored in Char fields with limited accesses usually restricted to the superuser. Such values are sensitive yet there was no standard easy way to prevent unauthorized access. We introduce a new Secret field type behaving just like the standard Char field it inherits from. The notable difference is that the secret field value is empty to all users except the super user. On other words, for regular users, it behaves like a write-only field.
Enhancements to existing features
Document attachment cards now show a subtle grey divider between the thumbnail and the card details. This small visual improvement makes the layout easier to scan and helps users distinguish image previews from related information.
Original PR description
PURPOSE add grey border between the thumbnail and card body to seperate image and content SPECIFICATION added a border on the right side of attachment image LINKS PR https://github.com/odoo/enterprise/pull/10711 Task: 2259683
Resolved issues and error corrections
The mobile app no longer vibrates when connection is lost or restored while running in the background. Users will still see the in-app text notification, reducing unnecessary interruptions and confusion.
Original PR description
Before this commit, the phone vibrated and a notification was displayed in case of connection loss/restore. This vibration seems annoying when the Odoo app is on background as we don't know what's happening. This is why we decided to remove it. The text notification inside the webview is enough. Task ID : 2207465
This fix makes an automated Web Studio test wait for the sidebar to fully refresh before continuing. It helps avoid intermittent test failures, supporting more stable quality checks without changing user-facing behavior.
Original PR description
Adding the second rule will trigger a complete redraw of the sidebar's content, which might make the content of the selector for the first domain button stale by the time it tries to run. Instead of waiting for the snack bar to be done, wait for a second approval rule to be present in the dom to ensure that this step only runs once the sidebar's dom is completely redrawn.
In the accounting list view, action buttons for grouped journal items now remain visible when users hover over any row within an expanded group, not just the group header. This makes common actions like edit, reverse, and duplicate easier to access and reduces confusion during review work.
Original PR description
PURPOSE: Currently, In account_move_line's new default grouped by list view, when we mouseover on the grouped by header row then it will display the buttons for edit, reverse and duplicate. but when you mouseover on the expanded rows of that particular group will not show the buttons for that group. SPEC: we have resolved this issue by toggling class on hovering on the expanded rows. and used that class in css to check the visibility of the group buttons. Task : 2069688
Code cleanup and technical improvements
This update reorganizes and expands the automated tests for marketing automation, making them easier to maintain and more reliable. It adds stronger coverage for email and SMS marketing flows, helping reduce the risk of regressions in future releases.
Original PR description
PURPOSE Improve marketing automation tests: improve their reading, add more tests and notably SMS tests. SPECIFICATIONS Reorganize module before working on tests: move models in their right place, split tests in main files (flow and internal details). Add dependency on marketing_automation_sms to write SMS related tests as well as on test_mail_full to benefits from all tools available in those test modules. Better use existing mail-related asserts and use them in marketing automation asserts to check sub modules did their job without having to manually check their result in unit tests. Rewrite models and tests to be more understandable, test more in-depth marketing trace values. LINKS Task ID 2247037 Community PR odoo/odoo#50384 Enterprise PR odoo/enterprise#10266 Upgrade PR odoo/upgrade#1122
Miscellaneous changes
Steps to reproduce the bug: - Let's consider a pricelist PL in € with 50% of discount on product P and discount_policy = without_discount - Let's consider a suscription product P with a sales price = 100€ - Create a subscription of P with PL Bug: The subtotal was 50€ but the discount was not displayed on the line opw:2255060 Forward-Port-Of: odoo/enterprise#10733 Forward-Port-Of: odoo/enterprise#10603
Original PR description
Steps to reproduce the bug: - Let's consider a pricelist PL in € with 50% of discount on product P and discount_policy = without_discount - Let's consider a suscription product P with a sales price = 100€ - Create a subscription of P with PL Bug: The subtotal was 50€ but the discount was not displayed on the line opw:2255060 Forward-Port-Of: odoo/enterprise#10733 Forward-Port-Of: odoo/enterprise#10603
The timer will appear when the timer is started, even if the timesheet grid has a manually encoded entry before today's date. Task-ID: 2243313 Forward-Port-Of: odoo/enterprise#10286
Original PR description
The timer will appear when the timer is started, even if the timesheet grid has a manually encoded entry before today's date. Task-ID: 2243313 Forward-Port-Of: odoo/enterprise#10286
Before this commit, changing the recurrency frequency without changing the until date would cause an error message. The previous value of `repeat_until` was not taken into account when creating the new recurrency. TaskID: 2252795 Forward-Port-Of: odoo/enterprise#10453
Original PR description
Before this commit, changing the recurrency frequency without changing the until date would cause an error message. The previous value of `repeat_until` was not taken into account when creating the new recurrency. TaskID: 2252795 Forward-Port-Of: odoo/enterprise#10453
traceback when trying to open an expense report if the user has no access rights in expense. as per task 1967791, reimburse in next payslip(refund_in_payslip) field is only visible for hr_expense.group_hr_expense_team_approver. for now this field is always invisible, so we have removed the groups from field defination. afetr this commit issue will be solved. TaskID: 2246587 Closes: Forward-Port-Of: odoo/enterprise#10492
Original PR description
traceback when trying to open an expense report if the user has no access rights in expense. as per task 1967791, reimburse in next payslip(refund_in_payslip) field is only visible for hr_expense.group_hr_expense_team_approver. for now this field is always invisible, so we have removed the groups from field defination. afetr this commit issue will be solved. TaskID: 2246587 Closes: Forward-Port-Of: odoo/enterprise#10492