Monday, August 26, 2024
5 changes
1 change
Resolved issues and error corrections
Products configured to keep selling when out of stock will no longer show a “Temporarily out of stock” warning in the ecommerce wishlist. This avoids confusing shoppers and keeps the wishlist messaging aligned with the merchant’s selling settings.
Original PR description
When the product has the "continue selling" box when "out-of-stock" checked, and you add the product to the wishlist from ecommerce, "Temporarily out of stock" message/warning will appear in the…
When the product has the "continue selling" box when "out-of-stock" checked, and you add the product to the wishlist from ecommerce, "Temporarily out of stock" message/warning will appear in the wishlist. To Reproduce on Runbot: 1. Make sure ecommerce module is installed 2. Go to a storable product (for example: Cable Management Box) 3. In the sales tab, make sure the option "Continue Selling" for Out-of-Stock field is checked 4. Go to ecommerce, search for the product (here, let's search for Cable Management Box), click on it 5. Click on add to wishlist 6. Go to wishlist. 7. We'll see "Temporarily out of stock" message. But, we don't want this because we want to continue selling even if it's out of stock, and don't want to customer to get confused with the message. So, since the message/warning doesn't align with the concept of continue selling when out of stock, we want to get rid of the message/warning if the product has "continue selling" box checked. opw-4121929
2 changes
Resolved issues and error corrections
The spreadsheet version history side panel now uses the correct padding, making the panel look cleaner and easier to read. This minor visual fix improves consistency in the spreadsheet editing experience without changing functionality.
Original PR description
Task: [4131488](https://www.odoo.com/web#id=4131488&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
2 changes
Resolved issues and error corrections
A spacing issue in the Mexican EDI payment report has been corrected where a space was missing between the VAT label and account information. The fix adds consistent styling to ensure proper spacing between these elements, improving the readability and professional appearance of payment reports.
Original PR description
In the payment report, a space was missing between the VAT label and the span "Emitter Acc. Ben.". In order to don't rely on spaces, a ps-1 class was added in both "Emitter Acc. Ben." and "Emitter Acc. Ord.". --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#53722
Fixed an issue that could prevent the IoT device page from working after a shared system update removed a library it depended on. The page now loads the needed component so device monitoring and related updates continue to work normally.
Original PR description
As a result of community PR #174213, jQuery has been removed from the backend JS bundle. The IoT device page relied on jQuery for longpolling requests. This PR simply adds a call to ensure jQuery is loaded. PR that caused the bug: https://github.com/odoo/odoo/pull/174213
This fix addresses a performance test failure in the Appointment module where database queries were exceeding expected limits. The issue occurred when the Appointment module was tested in isolation, and the fix ensures consistent test conditions by warming up the cache to prevent unexpected query increases from being missed in future updates.
Original PR description
Before the commit the [appointment single module build](https://runbot.odoo.com/runbot/build/66250461) is breaking due to query_count being more than 9 (11) The increase was introduced in b3487219c070cdc03c933d92bc0d362ad733e11f in `_unavailable_intervals_batch`. It wasn't detected because the are less queries in the standard build all modules installed) because of a warmer ormcache. (get_lang) This commit proposes to warmup the test in all case to avoid the extra queries when appointment is installed alone, hopefully avoiding to miss the increased query count next time.