Wednesday, September 24, 2025
77 changes
1 change
Resolved issues and error corrections
Customers who add items without choosing a pickup point will now have the checkout page's default pickup location properly applied. This prevents confusing checkout failures where a visible pickup location appeared selected but the order could not proceed to payment.
Original PR description
Description of the issue/feature this PR addresses: This commit fixes the issue where the pickup location does not get set even though it is present on the checkout page. This happens when the user…
Description of the issue/feature this PR addresses: This commit fixes the issue where the pickup location does not get set even though it is present on the checkout page. This happens when the user directly adds an item to cart without specifying the pick up location before adding to cart. This results in the location not being set but at the checkout page, the default pick up location appears as one of the warehouses given the way the default pickup location is set when loading the checkout page values. This makes the user think that the pickup location is set, but when they try to go to the pay page, an error is thrown saying the pick up location was not specified. This commit sets the pickup location data in such a case. [This commit] refactored the way in which the default location would be set on the checkout page but did not take into account the possbility that the customer might not select the pickup location when they are adding to cart, thus only rendering the value at the checkout page but not actually setting it. Refactored the test cases to avoid the redundancy in the setup process. Steps to reproduce on runbot: 1. Set the pick up in store as the default delivery method by updating the sequence 2. Go the shop on the website and add any item to cart which has stock in the specified pickup location, but don't select the pickup location here 3. Go to the cart and click checkout 4. The default pickup location will be set here 5. Click on Confirm 6. An error will appear saying the location was not set opw-4954187 [This commit]: https://github.com/odoo/odoo/commit/1d3942c75e59ac9538d112df43b4e39f2462fee4 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#227826
1 change
Resolved issues and error corrections
Customers can now change product options on website product pages even when some option combinations are excluded. The unavailable choices still look unavailable, but they no longer block shoppers from switching to another valid variant.
Original PR description
Versions -------- - saas-18.4+ Steps ----- 1. Create a product with attributes A & B; 2. for attribute A, create values A1 & A2; 3. for attribute B, create values B1 & B2; 4. add an attribute exclusion on A1 for B2; 5. add an attribute exclusion on A2 for B1; 6. open the product's website page. Issue ----- It's impossible to change attributes. Cause ----- Commit bbb2d98d9ab97 prevents selecting impossible combinations, as a consequence, it's impossible change product variants whose attributes exclude each other. Solution -------- Do not add the `disabled` attribute for excluded attributes, but maintaining the visual cues. Suggestion for future [IMP]: disable attributes as they were defined, without also disabling their inverse, e.g. if A1 is selected, disable B2, but don't disable A2 because B1 is selected. opw-5019677 opw-5050472 Forward-Port-Of: odoo/odoo#226612