Friday, October 11, 2024
12 changes · 17.0
Enhancements to existing features
The Peppol setup wizard no longer shows the demo mode selection to regular users. This keeps an internal testing and demonstration setting out of the main interface while still allowing it to be managed through system configuration when needed.
Original PR description
The demo mode option in the Peppol connection wizard is primarily used by internal teams (BA, support, sales) for demonstrations or testing. It is more appropriate to manage this mode through a system parameter instead of exposing it to all users in the wizard interface. This commit mirrors the change from (commit 6d222885f41f5136c690dcd56953f1a9775204ae pr odoo/odoo#182893), but without removing the related fields, making it suitable for stable versions. task-4215904
This update improves the French translation in the accounting module by refining a key phrase. The message "Vous avez lettré 2 transactions dans 45 secondes" has been corrected to "Vous avez lettré 2 transactions en 45 secondes" for better grammar and clarity. This ensures French-speaking users see more natural and professional language when using the accounting features.
Original PR description
In this context, the sentence seems better phrased with "en" rather than "dans": - Vous avez lettré 2 transactions dans 45 secondes. Becomes: - Vous avez lettré 2 transactions en 45 secondes. Forward-Port-Of: odoo/enterprise#70449
Resolved issues and error corrections
Odoo now ignores a specific type of vague browser error caused by Chrome extensions, such as Honey PayPal, when it is not useful for users. This prevents unnecessary error pop-ups from interrupting work while keeping normal debugging behavior available for developers.
Original PR description
Before this commit, when some extension in chrome threw an unhandledrejection event, Chrome apparently redacts it. The error popped into Odoo as very generic one. The error Dialog was spawned, intempestively. After this commit, we use a heuristic to block that kind of errors: Apparently, the error event is a CustomEvent, with no `reason`. opw-4246402 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
Miscellaneous changes
Since [1], the ".o_default_text_snippet" class has not been correctly removed when text is modified within a content-editable element. This commit resolves the issue. Steps to reproduce: - Drag and drop the "Pricelist block" into the page. - Click on the snippet newly inserted to display the options on the right panel. - Enable the "Descriptions" option under the Pricelist block options to display descriptions. - Edit some descriptions directly in the snippet. - Disable and re-
Original PR description
Since [1], the ".o_default_text_snippet" class has not been correctly removed when text is modified within a content-editable element. This commit resolves the issue. Steps to reproduce: - Drag and drop the "Pricelist block" into the page. - Click on the snippet newly inserted to display the options on the right panel. - Enable the "Descriptions" option under the Pricelist block options to display descriptions. - Edit some descriptions directly in the snippet. - Disable and re-enable the "Descriptions" option. - Bug: The edited descriptions are replaced by the default text. [1]: https://github.com/odoo/odoo/commit/03c552690b15cbf2e7d6b7812386ac64042219af#diff-52a4f9d2c217548e69e6b7fd097f286f1754a6389734eea254b87255e501cbef task-4084956 task-4147162 (first part) Forward-Port-Of: odoo/odoo#177588
Opening an event ticket link that is missing required ticket details now fails gracefully instead of causing a system error. This prevents confusing error pages for users who access incomplete or modified ticket URLs.
Original PR description
Currently, an error occurs while opening an event ticket with an invalid URL. Step To Produce: - Install the 'event' module. - And Open any booked event, click on 'Attendees', and open any record, Click on 'View Ticket' in chatter. - Copy the ticket URL and try to open this ticket URL without 'registration_ids' which is included in it. ``` TypeError: EventController.event_my_tickets() missing 2 required positional arguments: 'registration_ids' and 'tickets_hash' ``` An error occurs when the system tries to call a route '/event/<int:event_id>/my_tickets'' without certain parameters at [1]. Link [1]: https://github.com/odoo/odoo/blob/5945b8340ba4797c8224ab3464ec87e8f285d75a/addons/event/controllers/main.py#L31 To handle this issue, provide a default value to the parameter of the route method. sentry-4952598215 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where creating a related record inside a form could leave leftover child-record changes on the main record after saving. Users should see cleaner, more reliable form saves without unintended pending changes.
Original PR description
When adding a m2m record in a form view, although record is correctly add and virtual record should no longer be part of `web_save`, trigger save on parent/main record still has changes left from children's records. This fixes issue #178541 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Survey answer images on the participant results page now display at an appropriate size instead of overlapping. This makes quiz and survey results easier to review and presents uploaded answer images more neatly.
Original PR description
Steps to reproduce: 1. Create a live session for a 'Quiz about your company' survey 2. Add images to your answers 2. Complete it with one user 3. Review your answer in the last 4. The images are getting overlap Technical Reason: on the user-side results page, images that were not properly handled were displayed at their default size. After this commit: it should be perfectly aligned. Task-4208130
This pull request appears to make a small change related to the website menu behavior. The provided description is a test and does not include business details, so the expected user impact is likely limited.
Original PR description
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
### Steps to reproduce: - In Settings, enable "Multi-Step Routes" - In the Routes, unarchive MTO - Create 2 storable products P1, P2 with routes MTO + Buy - Set a different vendor on P1/P2 and ensure you have 0 units in stock - Create and confirm a sale order with 2 lines: - 1 x P1 - 1 x P2 > A delivery and 2 purchase order were created (one for each product) - Cancel the purchase orderfor P2 (it will not work with P1 hehe) - Go back to the SO and decrease the qty of P2 to 0 ###
Original PR description
### Steps to reproduce: - In Settings, enable "Multi-Step Routes" - In the Routes, unarchive MTO - Create 2 storable products P1, P2 with routes MTO + Buy - Set a different vendor on P1/P2 and ensure…
### Steps to reproduce: - In Settings, enable "Multi-Step Routes" - In the Routes, unarchive MTO - Create 2 storable products P1, P2 with routes MTO + Buy - Set a different vendor on P1/P2 and ensure you have 0 units in stock - Create and confirm a sale order with 2 lines: - 1 x P1 - 1 x P2 > A delivery and 2 purchase order were created (one for each product) - Cancel the purchase orderfor P2 (it will not work with P1 hehe) - Go back to the SO and decrease the qty of P2 to 0 #### > A return is created from patner to stock instead of updating the P2 move of the delivery ### Cause of the issue: When the sale order was confirmed the moves created for the delivery were both used the same procurment group and their `procure_method` was set to `make_to_order`. When the purchase order for P2 is cancelled, the delivery move associated with the related sol is cancelled and its `procure_method` is set to `make_to_stock` here: https://github.com/odoo/odoo/blob/c424fded8660de628bfcf3937806cc72c8410434/addons/purchase_stock/models/purchase.py#L148 Then, when you decrease the qty of the SOL from 0 to 1, a procurement for -1 unit of P2 will be created and run by the `_action_launch_stock_rule`. A negative move will then be created and confirm with a `procure_method`: `make_to_stock` here: https://github.com/odoo/odoo/blob/c424fded8660de628bfcf3937806cc72c8410434/addons/stock/models/stock_rule.py#L275-L277 Because the `procure_method` used at the creation of the negative move is determined from the `procure_method` of the first move related to the procurement group with a positive qty (here the P1 move): https://github.com/odoo/odoo/blob/1fd336e5f321e5256accff6b5a4032b237dce528/addons/stock/models/stock_rule.py#L257-L260 As such, the negative P2 move will have a different `procure_method` than the positive P2 move and they will not be merged here: https://github.com/odoo/odoo/blob/1fd336e5f321e5256accff6b5a4032b237dce528/addons/stock/models/stock_move.py#L1384 ### Fix: The fix proposed in commit 65d5e7900f41aa7f65159f8f4cdb0c6638eaf8ca and introducing the lines: https://github.com/odoo/odoo/blob/1fd336e5f321e5256accff6b5a4032b237dce528/addons/stock/models/stock_rule.py#L257-L260 works perfectly fine in most situtations but should considers only the moves related to the procurment group that concerns the same product to also work in the above case. opw-4214369 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#182802
Steps to reproduce: - Install serbian (latin) language - Add a keyword in serbian via SEO optimize menu - Traceback occurs This fix ensures that language variants, such as "sr@latin", are properly handled when making requests to the Google Autocomplete API for SEO suggestions. A test has been added. task-4210707 Forward-Port-Of: odoo/odoo#181400
Original PR description
Steps to reproduce: - Install serbian (latin) language - Add a keyword in serbian via SEO optimize menu - Traceback occurs This fix ensures that language variants, such as "sr@latin", are properly handled when making requests to the Google Autocomplete API for SEO suggestions. A test has been added. task-4210707 Forward-Port-Of: odoo/odoo#181400
Currently, a traceback occurs when the user creates a link tracker having no scheme in the URL. To reproduce this issue: 1) Install website_link, email marketing 2) Create a new link tracker with a target URL from email marketing/configuration 3) Now remove the `http://` from the target URL 4) Navigate to website/site/link tracker Error:- ``` AttributeError: 'str' object has no attribute 'to_url' ``` This is because when the target URL has no `http://` the URL scheme will be
Original PR description
Currently, a traceback occurs when the user creates a link tracker having no scheme in the URL. To reproduce this issue: 1) Install website_link, email marketing 2) Create a new link tracker with a target URL from email marketing/configuration 3) Now remove the `http://` from the target URL 4) Navigate to website/site/link tracker Error:- ``` AttributeError: 'str' object has no attribute 'to_url' ``` This is because when the target URL has no `http://` the URL scheme will be an empty string. So it executes the else block in the below line. https://github.com/odoo/odoo/blob/8a1e6bef82fdaa98c60ef1e3fa519a03206a6788/addons/link_tracker/models/link_tracker.py#L54-L58 Clearly in the else block the value of `tracker.get_base_url()` is the string, when joining the `url` and `tracker.get_base_url()` it becomes a string. which leads to a traceback when `to_url()` is accessed from the string. sentry-5925121505 Forward-Port-Of: odoo/odoo#182556
- Set up Avatax Credentials - In Fiscal Position "Automatic Tax Mapping (AvaTax)" enable "Automatic Detection" - Create an invoice with avatax product and register payment - Open payment entry and duplicate it Issue: Validation Error will raise "The following customer(s) need to have a zip, state and country when using Avatax:" This occurs because the system checks for customer data validity when duplicating the payment record but it should not occur opw-4119958 Forward-Port-Of: od
Original PR description
- Set up Avatax Credentials - In Fiscal Position "Automatic Tax Mapping (AvaTax)" enable "Automatic Detection" - Create an invoice with avatax product and register payment - Open payment entry and duplicate it Issue: Validation Error will raise "The following customer(s) need to have a zip, state and country when using Avatax:" This occurs because the system checks for customer data validity when duplicating the payment record but it should not occur opw-4119958 Forward-Port-Of: odoo/enterprise#69757