Daily updates from Odoo
Wednesday, October 16, 2024
9 changes · 18.0
Enhancements to existing features
The shop floor now again offers the optional "This Station" filter, letting manufacturing teams focus on orders that involve the currently selected work centers. This helps users reduce clutter and find relevant manufacturing orders without manually recreating a difficult dynamic filter.
Original PR description
Starting from 18.0, the default shopfloor filter "This Station" was removed from existence. See Commit 4e6038617586b669c00a23da0ea4355f869ecc94 This filter was initially added to odoo for performance reasons [1] and was removed since the shopfloor performance do not require it anymore to work properly. However, this filters appeard to be usefull for certain user in case for instance they want to filters out all the MO's that do not have an operation which belongs to at least one of the selected workcenter. In addition, this filter is reactive and quite hard to manually create since it requires that the user identifies the ids of its active workcenters. It was therefore decided to add it back to the list of filters that can be selected in the shopfloor in case the user would like to use it. [1] https://github.com/odoo/enterprise/pull/64551 opw-4241699
Resolved issues and error corrections
This fixes the invoice print template so VAT amounts show correctly in the totals section when invoices with standard tax are sent or printed. Businesses using GCC invoice localization will see accurate tax totals on customer-facing documents.
Original PR description
Create an Invoice with a standard tax Send&Print Issue: In totals section VAT amount will be wrong opw-4256242 opw-4256566
This fixes website editing behavior for SVG shapes and illustrations that still use older file paths after the content moved to a new location. Business users will see the correct editing options, such as Dynamic Colors, while unsupported actions like cropping illustrations remain blocked as intended.
Original PR description
In [1] shapes and illustrations were moved to `html_editor`. While some features have been adapted to the new path, others did not. No upgrade script was created to convert existing `/web_editor/shape/` paths to new `/html_editor/shape/` paths. Instead, the old route was kept available. However, some conditions, selectors and domains that recognized those paths have not been adapted to detect both kinds of paths. This commit adapts those conditions, selectors and domains so that both kinds of paths are identified as being shapes or illustrations. Steps to reproduce: - Add an SVG illustration in a website page - Select it => The "Dynamic Colors" options were not displayed [1]: https://github.com/odoo/odoo/commit/44129d85bdc993e37384536519a03d7c29ac7e83 task-4052712
This fixes an ecommerce issue where choosing the same product in multiple combo options only added it once to the cart. Customers now get a separate cart line for each selected combo item, so orders better match what they selected and expect to receive.
Original PR description
When using combo products in ecommerce, if two of the combos contained the same product and they were selected, only one row with a quantity of 1 would be created. e.g. if a you had a double burger combo product and the combos looked like: - Burger 1: Cheeseburger, Double Cheeseburger, Chicken Burger - Burger 2: Cheeseburger, Double Cheeseburger Currently if you were to choose double cheeseburger in both options it would only add 1 burger with quantity of 1 to the basket. Ideally it should be following the same practise as sale orders and create a line per each item. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix restores lot and serial number information in Maintenance when Inventory is also installed. It avoids a dependency issue that could prevent the feature from working reliably in existing databases.
Original PR description
Commit [1] is using models and data from `stock` module but `maintenance` does not depend on this one. A bridge would not be a solution on stable, since existing DBs that have both `stock` and `maintenance` would just lose the feature (the bridge would not be auto-installed) [1] https://github.com/odoo-dev/odoo/commit/1f2a5806b832529bd2ec53a878991e04800079bf sentry-5964505411
This fix lets users select multiple cells in tables when editing HTML content in Firefox. It removes a browser-specific editing issue, making table editing more reliable for users who work in Firefox.
Original PR description
This is a forward port of [1] to html_editor Issue: ====== - We can't select multiple cells in a table Origin of the issue: ==================== - When selecting multiple rows or columns inside a table in firefox, firefox creates multiples ranges per table cell selected. Solution: ========= - The first time we encounter more than 1 range, we merge them together and we manually update the selection - After the manual upadte, firefox will not trigger selectionchange anymore when we move the mouse, to deal with that we just manually call `handleFirefoxSelection` in `mousemove` event. task-4240675 [1]: https://github.com/odoo/odoo/commit/541c8baa550f072530c3ab9b7d3a9c32e2e6f095
Customers who must log in before ordering event tickets will no longer lose their selected tickets after signing in. This prevents frustration and avoids forcing attendees to restart the booking process.
Original PR description
Steps to reproduce ==================== - Say logging is mandatory to order (website settings). - Log in as a visitor, pick some tickets, and fill in the attendee details. - Try to confirm. - You are redirected to the login page and then to the event. - Your tickets are lost and you need to start again. After this PR ================== The cart will be restored with the ticket picked up, after login. Task-4039974
Posting tax closings for foreign VAT reports no longer changes the company tax lock date. This prevents unnecessary restrictions and exceptions when businesses still need to post activity for other jurisdictions.
Original PR description
Before this commit, posting any tax closing would always set the tax lock date. This was a bit restrictive, and required making lock date exceptions in order to post operations for other non-closed reports. We alleviate that by only setting the tax lock date when the domestic closing is posted ; the idea being it's the main one. So, tax closings posted for other countries for which a foreign VAT fiscal position is defined do not affect the tax lock date anymore.
This update prevents Odoo from creating duplicate Avalara tax records when taxes share the same visible name but have different jurisdiction codes. It reduces billing and tax calculation interruptions by aligning how taxes are matched with Odoo's uniqueness rules.
Original PR description
We recently reworked the way taxes are named [1]. It considered the description part of the "key" that uniquely identifies a tax. The description contains the jurisCode field returned by Avatax [2].…
We recently reworked the way taxes are named [1]. It considered the description part of the "key" that uniquely identifies a tax. The description contains the jurisCode field returned by Avatax [2]. This key is used to find an already existing tax, and creates it if it doesn't yet exist. _constrains_name() of account.tax however, doesn't consider the description field. This means that two taxes with the same name (e.g. CA STATE 6%) and different jurisdiction codes (e.g. 001 and 013) cause issues. The first one will be created as normal. When the second one is processed it will fail to find a match because the description is different, so Odoo will create a second one resulting in a constraint error. To resolve this, stop adding the jurisdiction code and stop looking at the description all together. In the end it's not critical information that needs to be in Odoo. For tax details the user already relies on the Avalara portal anyway. [1] https://github.com/odoo/enterprise/pull/68549 [2] State assigned code identifying the jurisdiction. Note that this is not necessarily a unique identifier of the jurisdiction.