Tuesday, November 5, 2024
7 changes
1 change
Resolved issues and error corrections
Fixed timesheet reports so they show only tasks or subtasks that actually have recorded time. This prevents empty parent tasks from appearing and makes subtask entries easier to trace back to their origin.
Original PR description
Steps to reproduce: - Project app > New Project > New Task - On Task > Subtask tab > Add subtask > Save - On Subtask > Timesheets tab > Record a timesheet - On task > Print timesheets The report shows a line for Task with no timesheets in saas-17.2 and saas-17.4, while it is completely blank in 18.0 (Due to an extra condition added in https://github.com/odoo/odoo/pull/178397). We'd expect only tasks with recorded timesheets to be on the report, regardless of whether their parent tasks are there or not. Additionally, since subtasks can now appear without parent, the titles have been updated to make tarcking subtask origin easier. opw-4292481 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1 change
Resolved issues and error corrections
This fix prevents customers on Mexican and Chilean e-commerce sites from being blocked at order confirmation by a missing shipping method. Checkout now follows the normal delivery selection step, improving successful online order completion for affected localizations.
2 changes
Resolved issues and error corrections
Brazilian webshop orders now correctly trigger Avatax tax calculation during checkout. This prevents payment-blocking errors caused by missing goods operation details, helping customers complete online purchases successfully.
Original PR description
With a BR Company Setup: Settings > Website, assign 'My Website' to BR Company Configure Avatax Brazil in General Settings > Taxes > Avatax Publish the Product "Regular Consumable Product" to be available in the website. Open the web shop as Public User Add "Regular Consumable Product" to cart Go to checkout Fill valid Brazilian customer info Pay Issue: Error will popup ``` odoo.http: Odoo could not fetch the taxes related to S00040. It is not possible identify the CFOP ``` This occurs because the sales order is missing the "Goods Operation Type" and the call to Avatax is not done opw-4239483
3 changes
Resolved issues and error corrections
This update fixes an issue where renewed subscriptions were incorrectly forecasting stock decreases. Now, the stock forecast accurately reflects only the new subscription created during the renewal process, ensuring more precise inventory management. This change improves forecast accuracy and reduces potential overstocking.
Original PR description
Steps to reproduce: - New product > Storable; Recurring; Edit 'On Hand Quantity' to 10 - New subscription > Add your product > Confirm - Create Invoice > Confirm > Back to sub - View forecast on order line > 1 reserved; 1 forecasted for next period (This is correct, the subscription is ongoing) - Renew > Confirm > View forecast - 1 reserved for original sub (OK); 2 forecasted for next period This is wrong because renewed subscriptions should no longer have recurring invoices, meaning there is no reason to forecast a stock decrease for them. i.e here it should only forecast 1 unit for the next period corresponding to our new subscription (Created by renew). Prior to 17.0 a storable product cannot also be recurring, so this issue is irrelevant there. opw-4239989
Original PR description
In Mexican (or Colombian) e-commerce websites, a customer may face an issue where they are unable to confirm an order because no delivery method is selected. ### Steps to reproduce - Install…
In Mexican (or Colombian) e-commerce websites, a customer may face an issue where they are unable to confirm an order because no delivery method is selected. ### Steps to reproduce - Install `l10n_mx_edi_website_sale` - Ensure the website is configured with a Mexican company - Enable 'Automatic Invoice' in website settings - As a public user, proceed through checkout and try to confirm the order The issue occurs if the user is prompted to fill in delivery information and hasn't previously provided an address. This can be consistently reproduced using a new incognito session. Upon attempting to confirm the order, the following error is shown: "No shipping method is selected." ### Cause The delivery information form (`/shop/address/submit`) normally redirects to `/shop/checkout`, where the user selects a delivery method. However, the `_get_extra_billing_info_route` hook can alter the redirect, bypassing the checkout step and causing the delivery method to remain unset. ### Fix The extra billing info flow is already handled in the checkout steps. Therefore, `_get_extra_billing_info_route` is no longer necessary. opw-4205135 opw-4222398
Users who run into an Amazon onboarding issue now see a clear error page instead of a generic internal server error. This helps them understand what went wrong and reduces confusion during setup.
Original PR description
When an onboarding error occurred, the error page failed to render and the user would see "Internal Server Error" instead of a more helpful error message. The server error had two causes: - The original onboarding error not being properly cast to a string. - The onboarding return route not passing the lang code to the QWeb context.
This update resolves a confusing issue in the Odoo Web Studio where users weren't correctly controlling the visibility of certain fields based on group membership. Previously, toggling a group visibility setting had no effect. Now, the system properly handles 'not' group attributes, ensuring accurate field visibility and a consistent user experience.
Original PR description
Have a node that goes: ```xml <div groups="!module.some_group" /> ``` Before this commit, this case was not handled and that not-group was just ignored. This created confusion as the node, when the user was part of the group, would be invisible, the checkbox invisible would be ticked, and uniticking it had no effect. After this commit, we handle the case, with a second selector in the studio sidebar. opw-4273853
This update fixes an issue where rental order descriptions didn't automatically update when the rental start and end dates were changed in the cart. The system now recomputes the description after date modifications, ensuring accurate order details are displayed to the customer. This improves the user experience for rental orders.
Original PR description
Problem: When rental dates are changed in the cart, the update occurs via an API call, which doesn't trigger the `_onchange_rental_start_date` and `_onchange_rental_return_date` methods. Additionally, we cannot add `rental_return_date` and `rental_start_date` as dependencies for `_compute_name` as outlined in this [commit](https://github.com/odoo/enterprise/commit/de5f3c7521d839e7549f5d44c7832e610fad7f29). Solution: Recompute the description after changing the dates in `_cart_update_renting_period` Steps to reproduce: - Add any rental product to the cart. - On the cart page, modify the rental start and end dates. - The order description does not update to reflect the new dates. opw-4259443