Thursday, February 6, 2025
13 changes
1 change
Resolved issues and error corrections
This fixes an incorrect test step in the online shop cart flow that was causing automated checks to time out. The change helps keep quality checks stable so future website sales updates can be validated more reliably.
Original PR description
Correct trigger which was wrong, causing JS test to timeout runbot-task-98520
1 change
Resolved issues and error corrections
The customer portal ticket list now uses ticket ID as the default sorting option instead of creation date. This removes a redundant sorting choice and makes the list order better match how users expect to review tickets.
Original PR description
In the ticket list view of the portal, we can filter tickets by create date and by ID. This is a bit redundant, and sorting by id reflects more accurately what we want to see. Therefore, this PR removes the filter by create date to default to the filter by ID instead. Task-4438387
11 changes
Resolved issues and error corrections
The French accounting upgrade now avoids assigning standard identifiers to bank records with unusual custom BIC codes. This prevents custom bank data from being mistaken for official module-provided records during migrations.
Original PR description
The upgrade script is supposed to create xmlids for french banks that were already created from csv, if it matches custom records that have unusual bic, it is better to skip the whole record. Standard BIC format is a capital alphanumeric only. Replacing the spaces or unsupported characters in the xmlid will result in custom records looking like they come from standard module. alternate fix for https://github.com/odoo/odoo/pull/191970 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change fixes a failing automated check related to the restaurant point-of-sale tip screen. It helps keep the restaurant POS workflow stable and prevents build failures from blocking future updates.
Original PR description
Error runbot: 111972
The GSTIN status button and update action now appear only when the user is working with Indian companies. This prevents incorrect GSTIN status checks in multi-company setups and helps ensure the right tax environment is used.
Original PR description
This commit fixes a few issues in multi-company context: - only show the GSTIN status/update button when user has at least one IN companies selected - only allow the update when user's active company is an IN company (to ensure we correctly determine the EDI test/production status) opw-4367302 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an error that could stop users from attaching files by URL when the external response did not include expected file type information. The change makes the editor handle that missing detail safely, improving reliability when adding linked attachments.
Original PR description
This error occurs when ``content-type`` is not found in the response when attaching any file with the type ``URL``. Traceback: --- ``` KeyError: 'content-type' File "odoo/http.py", line 2366, in…
This error occurs when ``content-type`` is not found in the response when attaching any file with the type ``URL``.
Traceback:
---
```
KeyError: 'content-type'
File "odoo/http.py", line 2366, in __call__
response = request._serve_db()
File "odoo/http.py", line 1894, in _serve_db
return self._transactioning(
File "odoo/http.py", line 1957, in _transactioning
return service_model.retrying(func, env=self.env)
File "odoo/service/model.py", line 137, in retrying
result = func()
File "odoo/http.py", line 1924, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 2171, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 329, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 727, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "addons/html_editor/controllers/main.py", line 355, in add_url
attachment = self._attachment_create(url=url, res_id=res_id, res_model=res_model)
File "addons/html_editor/controllers/main.py", line 256, in _attachment_create
mime_type = response.headers['content-type']
File "requests/structures.py", line 52, in __getitem__
return self._store[key.lower()][1]
```
https://github.com/odoo/odoo/blob/2fe55ae592e5812c5ee5e39ed1e8332bde608cb2/addons/html_editor/controllers/main.py#L257
sentry-6015024235
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis fixes Spanish localization tax data by restoring price-inclusion override settings that were removed by mistake. It helps ensure Spanish tax calculations keep the intended behavior for affected accounting setups.
Original PR description
On https://github.com/odoo/odoo/commit/06d3ef5853aa0a93ac2de1642fd11ea191a3bbd3 price_include_override were erroneously removed
This fixes an issue where users could not print checks when the payment account did not allow reconciliation and the payment was immediately marked as paid. Check printing is now allowed in this case, preserving prior behavior, while voiding or rejecting these paid checks remains blocked.
Original PR description
**Steps to reproduce:** - Install Accounting - Go to "Accounting / Configuration / Accounting / Journals" - Open "Bank" Journal - Go to "Outgoing Payments" tab - Set a check layout - For "Checks"…
**Steps to reproduce:** - Install Accounting - Go to "Accounting / Configuration / Accounting / Journals" - Open "Bank" Journal - Go to "Outgoing Payments" tab - Set a check layout - For "Checks" line, set "101401 Bank" (i.e. an account that doesn't allow reconciliation) as outstanding payments account - Create a vendor bill and confirm it - Pay the bill with "Checks" as payment method => The bill is directly marked as "PAID" and not "IN PAYMENT" because the "Bank" account doesn't allow reconciliation - Go the the check payment **Issue:** It is not possible to print it. The same configuration allows to print the check in previous versions. **Cause:** As the check payment is using an account that doesn't allow reconciliation, the payment is set in "Paid" state directly, but the printing is disabled for checks in that state. **Solution:** As it should be harmless to allow to print the check even if it is already paid, we will allow to print it to keep a consistent behavior with previous versions. Only printing the check will be allowed. Voiding or rejecting will still be impossible. opw-4498446 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents the point of sale Self Order flow from trying to subscribe to a missing or undefined communication channel. It helps avoid avoidable errors and improves reliability for customers using self-ordering.
Original PR description
Prevent subscription to undefined channel name in Self Order.
This fix corrects a few mislabeled Peppol electronic address scheme names that were introduced in a prior update. It helps users select the right invoicing identifiers and reduces confusion when configuring electronic invoicing partners.
Original PR description
Previous commit ([1]) tried to simplify with less technical names the Peppol EAS but introduced small errors. [1]: https://github.com/odoo/odoo/commit/5c7eefed412e676c6ddf67f62bce514e5bade44c task-no
This fix ensures stock-related actions triggered by subscriptions, rentals, and field service sales pass quantity information consistently. It reduces the risk of order processing errors and also avoids an access issue for project users working with field service sales orders.
Original PR description
The override of `_action_launch_stock_rule` was passing its `previous_product_uom_qty` keyword argument as a positional parameter to the `super` call, preventing other overrides from passing it with its key name. This commit ensures that the argument is now passed correctly with its key name. It also makes the override kwargs-agnostic by packing and unpacking them with `**`, thus preventing future issues related to signature changes in the parent method. See also: - https://github.com/odoo/enterprise/pull/77839 - https://github.com/odoo/documentation/pull/11823
The Overdue Invoices button on a partner now shows only sales-related documents, rather than including unrelated miscellaneous accounting entries. This helps users focus on the invoices that actually need follow-up and avoids confusion in customer account reviews.
Original PR description
When opening the Invoice Overdue through the partner form: 1 - Create over due MISC entries (through deferred entries for example) 2 - Open a partner 3 - Go the the Accounting tab 4 - Click the Overdue Invoices button -> Some MISC entries show while we only want to view sale document. This commit fixes that by adding a filter on the domain to reduce the search scope to only sale documents. task-4523037
Confirmed subscription sales orders no longer trigger an error when the Start Date or Next Invoice Date is changed or removed. This helps sales teams update subscription timing without interruptions.
Original PR description
This error occurs when attempting to change the ``Start Date`` or ``Next Invoice Date`` after the Sales Order has been confirmed. Steps to reproduce: --- - Install ``sale_subscription_stock`` module - Create a ``New`` Sale Order and fill in the required fields and order line - Now add ``Recurring Plan`` and in ``Other Info`` add ``Start Date`` > Confirm - Remove ``Start Date`` Traceback: --- ``TypeError: '<=' not supported between instances of 'datetime.date' and 'bool'`` At [1] this commit resolves the issue by verifying the presence of the ``Start Date`` and ``Next Invoice Date``. [1]- https://github.com/odoo/enterprise/blob/68fa2f5ea8c42ccb66823efb847d230fe3994527/sale_subscription_stock/models/sale_order.py#L21 sentry-6220852935