Daily updates from Odoo
Sunday, April 27, 2025
4 changes · 18.0
New functionality added to Odoo
This pull request adds several custom “awesome” add-ons, including dashboard, gallery, kanban, and clicker features. The commit history also indicates a theme change was added and then removed, so the lasting business impact appears focused on new custom app functionality rather than a platform-wide theme update.
Original PR description
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
Miscellaneous changes
Previously, when using a payment method integrated with the Bank App (QR code), a QR code was shown on the customer display. This functionality was lost during the refactoring of the customer display into a standalone OWL app: https://github.com/odoo/odoo/commit/acf78c27b12cf014cd80d20ea5853e63ab9ca03f It was later removed entirely with the deletion of the point_of_sale.CustomerFacingQR template: https://github.com/odoo/odoo/commit/49116abd0916ac835e0ad1f6ba1714b8e80c4272 This commit
Original PR description
Previously, when using a payment method integrated with the Bank App (QR code), a QR code was shown on the customer display. This functionality was lost during the refactoring of the customer display into a standalone OWL app: https://github.com/odoo/odoo/commit/acf78c27b12cf014cd80d20ea5853e63ab9ca03f It was later removed entirely with the deletion of the point_of_sale.CustomerFacingQR template: https://github.com/odoo/odoo/commit/49116abd0916ac835e0ad1f6ba1714b8e80c4272 This commit reintroduces the QR code on the customer display. Forward-Port-Of: odoo/odoo#206872
Description of the issue/feature this PR addresses: mailing.mailing model is reused between Mail Marketing and SMS Marketing apps, however warning message defined in Mail Marketing about incorrect mail server is not relevant for SMS Marketing. Affected versions : 16.0+ (probably since v13.0 but older versions not maintained anymore) Current behavior before PR: In some cases, you can end up with a warning on SMS mailing form stating "This email from can not be used with this mail server.[..
Original PR description
Description of the issue/feature this PR addresses: mailing.mailing model is reused between Mail Marketing and SMS Marketing apps, however warning message defined in Mail Marketing about incorrect…
Description of the issue/feature this PR addresses: mailing.mailing model is reused between Mail Marketing and SMS Marketing apps, however warning message defined in Mail Marketing about incorrect mail server is not relevant for SMS Marketing. Affected versions : 16.0+ (probably since v13.0 but older versions not maintained anymore) Current behavior before PR: In some cases, you can end up with a warning on SMS mailing form stating "This email from can not be used with this mail server.[...]" For instance you can end up in this case if : - You have defined an ir.config_parameter mass_mailing.mail_server_id - from_filter from this mail_server does not match email_from from user creating SMS Marketing Desired behavior after PR is merged: The above warning is only relevant for Mail marketing but not for SMS marketing. This PR therefore proposes to generate warning message only if mailing_type == "mail" --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#205912
When submitting message templates to the WhatsApp API, the request could occasionally time out before receiving a response. This resulted in templates being created on Facebook's side, but not registered in Odoo, as the template ID assigned by Facebook was never received. Since template names must be unique, resubmitting the same template fails, leaving the systems out of sync. This commit increases the request timeout to (10s connect, 30s read) to reduce the chance of timeouts. opw-470
Original PR description
When submitting message templates to the WhatsApp API, the request could occasionally time out before receiving a response. This resulted in templates being created on Facebook's side, but not registered in Odoo, as the template ID assigned by Facebook was never received. Since template names must be unique, resubmitting the same template fails, leaving the systems out of sync. This commit increases the request timeout to (10s connect, 30s read) to reduce the chance of timeouts. opw-4706852 opw-4720635 Forward-Port-Of: odoo/enterprise#83581