Monday, March 4, 2024
11 changes · 17.0
Enhancements to existing features
A README file has been added to the SEPA Direct Debit payment module to document how the payment integration works, including technical implementation details. This helps users and developers understand the payment flow and makes it easier to maintain the module as payment standards evolve.
Original PR description
Each payment acquirer has its own implementation specificities: some implement a 'payment with redirection' flow and others a 'direct payment flow'; sometimes the 'payment with redirection' flow is…
Each payment acquirer has its own implementation specificities: some implement a 'payment with redirection' flow and others a 'direct payment flow'; sometimes the 'payment with redirection' flow is even implemented as a 'direct payment' flow through an iframe; one payment acquirer could support webhooks while another does not and relies on another mechanism to fetch payment status updates... It can be tricky to guess where to look in the code to determine how a payment acquirer is implemented. On top of that, the online payments ecosystem evolves at a fast pace due to competition, buyouts, and legislation enforcement. Acquirers are thus frequently migrated to new APIs that might differ in implementation from the previous API. To help figure out the *which*, *why*, *how*, and *when* of payment API implementations, a README.md file is added to the main directory of all payment acquirer modules. They can be browsed in human-readable format on GitHub. task-2374916 See also: - https://github.com/odoo/odoo/pull/153016 Forward-Port-Of: odoo/enterprise#57842 Forward-Port-Of: odoo/enterprise#56182
This update makes course sections more visually distinct from regular content by increasing their font weight in the backend interface. This helps instructors and administrators better organize and navigate course materials by making section headers stand out more clearly.
Original PR description
Purpose ======= Increase the bold of the sections in back end to better differentiate them from the content. Specifications ============== Adding !important next to the css bold style (value = 700) applied on the sections to make sure it takes the priority over the default list view sections "fw-bold" class (value = 500). Task-3759152 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The portal task view now shows the remaining days or hours on the sales order in the right position and with consistent styling. This makes the task details easier to read and keeps the customer portal presentation aligned with other fields.
Original PR description
In portal tasks view, the "Remaining Days/Hours on SO" field is misplaced and the styling is incorrect. It should be set in last position, and the styling should be the same as the other fields. This PR fixes it. task-3756260
This update fixes incorrect or duplicated identifiers in some Odoo screens. It helps keep views more reliable and avoids confusion or conflicts when those screens are customized or extended.
Original PR description
**Description of the issue/feature this PR addresses:** There are some instances where duplicate or wrong element ids exist in some view files. **Desired behavior after PR is merged:** The element ids have been changed to remove duplicates and fix wrong ones. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Portal users can now make the comment box taller when adding messages on shared tasks. This makes it easier to write and review longer comments without being constrained by a fixed-size text area.
Original PR description
**Current behavior:** The textarea where a portal user can leave some comments is not vertically resizable. **Expected behavior:** A portal user can resize this textarea vertically. **Steps to reproduce:** 1. Share a project with a portal user 2. Login as the portal user, on your account page navigate to /my/tasks and click on one 3. Observe that the box to leave a comment cannot be vertically resized **Cause of the issue:** In the XML defining this webpage, the textarea corresponding to this input has style="resize:none". **Fix:** Override this style definition in the .scss file for this page to allow for vertical resizing. In master it could be better to fix it by modifying the XML file to not have conflicting a style definition. opw-3757555
This change prevents Belgian payroll accounting tests from failing when optional demo data is unavailable or only partly loaded. It helps keep module validation and merge workflows moving while still allowing demo data issues to be investigated separately.
Original PR description
In case test_l10n_be_hr_payroll_account demo data is not loading, the tests are failing, as demo data is referenced from the init of the tests. Of course if demo data is not loaded due to error, it should be investigated, but it should not block module. Moreover, as the reference is in init, it's impossible to deactivate it for a while and it blocks the merging process for everyone.
This update fixes a crash that occurred in the Web Studio export test when running tests for individual apps that don't have a currency field. The system now automatically creates the necessary currency field when needed, ensuring tests run smoothly without interruption.
Original PR description
…t in test Before this commit, the test /web_studio.test_export crash in single app testing because the model on which the test is done did not have a currency field. After this commit, there is no crash as we create a new currency field if necessary. runbot-error-57418
This update corrects the alignment of total labels in Field Service worksheet PDF reports. Previously, the 'total' labels were not properly aligned to the right side of the report. The fix applies CSS styling to ensure consistent and professional formatting when generating worksheet reports with product line items.
Original PR description
Steps to reproduce: - go to the field service - go to any task add product to it - generate the pdf report 'worksheet report pdf' Issue: - 'totals' labels is not aligned to the right Solution: - aligned the 'labels' to the right us css class Task:3549234 Forward-Port-Of: odoo/enterprise#57899 Forward-Port-Of: odoo/enterprise#50101
This update corrects an incorrect value used in the payroll testing process for Morocco. The fix ensures that contract creation tests run properly, which helps maintain the reliability of the payroll system for Moroccan operations.
Original PR description
Fix wrong value for crontract creation in test file test_payroll_ma.py. task : 3774041 Forward-Port-Of: odoo/enterprise#57721
This fix corrects where the "Landed Cost" option appears in product forms. Previously, it was incorrectly showing up for Event Tickets, Event Booths, and Gift Cards. Now it will only display for Service and Storable products where it's actually needed. This prevents confusion and ensures users only see relevant options for their product type.
Original PR description
Steps to Reproduce : - install sales, stock modules - go to products and create new - select product type as Event Ticket,Event Booth or Gift Card - Landed cost boolean is suppose to be visible for a…
Steps to Reproduce : - install sales, stock modules - go to products and create new - select product type as Event Ticket,Event Booth or Gift Card - Landed cost boolean is suppose to be visible for a service type product under purchase. Issue : - Landed cost boolean is suppose to be visible for a service type product under purchase, But currently it is visible on other type of products specific to other models like event tickets, event booths etc. Cause: - In product Module there are two Selection fields like detailed_type and type. The detailed_type Selection field contain service, consumable, event booths, event tickets, storable product And the type selection field contains service, consumable, storable product - In xml views for that landed cost boolean the invisible attribute contains the condition like type != service, because of this the landed cost boolean is visible for the product type of event tickets, event booths and gift Cards. Solution: - if we use detailed_type instead of type selection field, then the landed cost boolean field will be invisible on other product types. task- 3725202 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 Forward-Port-Of: odoo/odoo#153371
A test for the calendar month view was failing intermittently because it assumed the calendar was always in week view when trying to change the display scale. This fix improves how the test selects the scale option, making it work regardless of the current view mode. This ensures the calendar feature works reliably across different user scenarios.
Original PR description
The `test_calendar_month_view_start_hour_displayed` makes sure that start hour is display in calendar month view.
The test was failing because when clicking on scale selector, it used '.dropdown-toggle:contains("Week")' however it might happen that the current scale is not week.
This commit fixes this issue by changing the way we access the scale selector.
fixes runbot-59023