Monday, December 16, 2024
13 changes · 17.0
Resolved issues and error corrections
When users click to calculate the full total in large list or kanban views, Odoo now uses the same viewing settings as the page itself. This prevents incorrect totals when filters or visibility options affect which records should be counted.
Original PR description
Have a list or kanban views with more than 10k records such that the count limit is reached, and the pager displays something like "1-80/10000+". Click on "10000+" to compute the real count. Before this commit, the context wasn't given to that call, which could obviously return a wrong result, for instance if the context has the "active_test" key set to false. task~4331708 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Valid Spanish electronic invoice certificates no longer fail just because the Organizational Unit field is missing. This prevents unnecessary errors when using otherwise valid certificates for Facturae invoicing.
Original PR description
The 'OU' (Organizational Unit) field is not required for valid certificates. Requiring it will result in a traceback even when a certificate is considered valid. This PR makes the 'OU' field optional. opw-4325514
Fixed an eCommerce product page layout issue where the Buy Now button could appear excessively large when quantity selection was disabled. This keeps the purchase area looking consistent and professional for shoppers.
Original PR description
Versions -------- - 17.0+ Steps ----- 1. Edit a product page in eCommerce; 2. enable "Buy Now" button; 3. disable "Select Quantity". Issue ----- The "Buy Now" button becomes comically large. Cause ----- In 16.0, this specific configuration also enlarged the "Add to Cart" button, so a conditional was added to keep the "Buy Now" button the same size. With the UI changes in 16.3+, the cart button no longer changes size, but doing the same for the "Buy Now" button was overlooked. Solution -------- No longer change the button size on `not hasQuantities or not hasBuyNow` opw-4404060
Fixes an issue where custom gradient backgrounds set on website headers did not appear in the mobile navigation menu. This keeps the mobile website design consistent with the desktop version and with the branding configured in the Website Editor.
Original PR description
Since commits [1] and [2], the gradient background colors for headers in the mobile version were not applied. This commit resolves the issue. Steps to reproduce: - Open the Website Editor. - Click on the header. - Change the background color of the header and select a custom gradient. - Exit edit mode. - Click on the mobile icon to view the mobile version. - Click the hamburger icon. - Observe that the gradient background is not applied. opw-4329423 [1]: https://github.com/odoo/odoo/commit/2dc3b28e570492b0484d185eb656e74df9c59d68 [2]: https://github.com/odoo/odoo/commit/bc13176de8d66bbdc1c536017b1f046c5fd31a86
This update corrects a formatting issue within the WhatsApp composer, ensuring phone numbers are correctly displayed without spaces or dashes. Previously, incorrect formatting caused errors preventing message delivery and channel linking. Now, users can reliably send WhatsApp templates from within Odoo.
Original PR description
**Before this Commit :** - When using the whatsapp composer on a record to send a whatsapp template, the number (phone/mobile) taken from the partner comes with the phone widget format (including spaces and dashes). - This would cause an error when linking the response received to the associated record, thus not creating an associated whatsapp channel, printing a link to the related SO,lead,etc and not posting a message on the record with a link to the whatsapp channel. **With this Commit :** - The composer phone field has the correct format when opened, preventing this behaviour to occur.
Miscellaneous changes
Gateway processing creates values from incoming emails. However we have to pop those that are not going to populate real fields, like x_odoo_message_id. Forward-Port-Of: odoo/odoo#190731
Original PR description
Gateway processing creates values from incoming emails. However we have to pop those that are not going to populate real fields, like x_odoo_message_id. Forward-Port-Of: odoo/odoo#190731
Probably a copy-paste error, causes sync to throw an error probably due to pot files not expecting to have translated terms in it. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Original PR description
Probably a copy-paste error, causes sync to throw an error probably due to pot files not expecting to have translated terms in it. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Improve loop detection and break. Indeed heavy usage of mailgateway on Odoo servers lead us to face email loops. Those lead to email being disabled on our servers due to email limit, and to other issues (spam, never ending notifications, ...) on hosted servers. Three scenarios are fixed with this PR. See individual commits for more details. Those are * having followers using alias email, and using a mail provider that rewrites msg-id: we cannot detect message duplication and this ma
Original PR description
Improve loop detection and break. Indeed heavy usage of mailgateway on Odoo servers lead us to face email loops. Those lead to email being disabled on our servers due to email limit, and to other…
Improve loop detection and break. Indeed heavy usage of mailgateway on Odoo servers lead us to face email loops. Those lead to email being disabled on our servers due to email limit, and to other issues (spam, never ending notifications, ...) on hosted servers. Three scenarios are fixed with this PR. See individual commits for more details. Those are * having followers using alias email, and using a mail provider that rewrites msg-id: we cannot detect message duplication and this may generate loops. Several mail providers rewrite message IDs and that is a pain for us. We therefore add a custom header allowing to keep message ID in envelope; * replying to bounce may create bounce in loops: this is fixed using the loop detection custom reference; * detect loops on record update in addition to record creation: do not limit loops detection on aliases creating records, also check updated records; Task-3895869 OPW-4051539 OPW-4295745 OPW-4302257 Forward-Port-Of: odoo/odoo#187696
Steps to reproduce: - define your language as French/BE - create a bill (facture fournisseur) - edit the vat with '20.13' using the numpad decimal key Issue: the amount is '2013.00' Cause: numpad decimal in belgian layout is a comma `,` which in this is interpreted as a thousands separator. Solution: Use the `useNumpadDecimal` hook opw-4284370 Forward-Port-Of: odoo/odoo#189582
Original PR description
Steps to reproduce: - define your language as French/BE - create a bill (facture fournisseur) - edit the vat with '20.13' using the numpad decimal key Issue: the amount is '2013.00' Cause: numpad decimal in belgian layout is a comma `,` which in this is interpreted as a thousands separator. Solution: Use the `useNumpadDecimal` hook opw-4284370 Forward-Port-Of: odoo/odoo#189582
Description of the issue/feature this PR addresses: - The last update on Mexican banks was five years ago. Since then, several new banks have emerged, while others have closed. Current behavior before PR: - 3 banks in our data no longer exist in real life. - 3 banks have outdated names. - 15 new banks aren't included, since they emerged after our bank data was updated. Desired behavior after PR is merged: - To align the bank list with those specified by the SAT (_Servicio de Administr
Original PR description
Description of the issue/feature this PR addresses: - The last update on Mexican banks was five years ago. Since then, several new banks have emerged, while others have closed. Current behavior before PR: - 3 banks in our data no longer exist in real life. - 3 banks have outdated names. - 15 new banks aren't included, since they emerged after our bank data was updated. Desired behavior after PR is merged: - To align the bank list with those specified by the SAT (_Servicio de Administración Tributaria_, Mexico's highest tax authority responsible for tax collection), you can refer to their [official documentation](http://omawww.sat.gob.mx/fichas_tematicas/buzon_tributario/Documents/catalogo_bancos.pdf). opw-[4327242](https://www.odoo.com/odoo/project.task/project.task/4327242) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189387
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#190489
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#190489
Before, when using reconcile models that wanted to match invoice/bills to statement based on the Label and/or Note and/or Reference, if there is no real match with the statement label, the bank reco would mount/ suggest another entry from the same partner. This is misleading as we expect to only have mounted lines that match with the statement, as stated in the reconciliation model. task-4194671 Forward-Port-Of: odoo/odoo#181620
Original PR description
Before, when using reconcile models that wanted to match invoice/bills to statement based on the Label and/or Note and/or Reference, if there is no real match with the statement label, the bank reco would mount/ suggest another entry from the same partner. This is misleading as we expect to only have mounted lines that match with the statement, as stated in the reconciliation model. task-4194671 Forward-Port-Of: odoo/odoo#181620
When creating a supplier invoice for a provider of type "2nd category voucher issuer," the system incorrectly defaults the document type to 56 (Electronic Debit Note) instead of 71 (Electronic Fee Receipt). This results in additional manual corrections and risks errors if the document type is not updated before confirmation. This fix ensures the system automatically selects document type 71 for providers of this category, streamlining the process and reducing error potential. opw-4217228
Original PR description
When creating a supplier invoice for a provider of type "2nd category voucher issuer," the system incorrectly defaults the document type to 56 (Electronic Debit Note) instead of 71 (Electronic Fee Receipt). This results in additional manual corrections and risks errors if the document type is not updated before confirmation. This fix ensures the system automatically selects document type 71 for providers of this category, streamlining the process and reducing error potential. opw-4217228 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#188166