Search
Navigate
Branch
Saturday, August 24, 2024
4 changes
1 change
Miscellaneous changes
For Mercado Pago to recommend odoo to customers they needed two changes: 1) Send a unique external reference to identify payments 2) Send the platform-id header to identify how many people use the integration. This PR addresses both: 1) Utilize the pos_reference field (uid) to identify records 2) Use a system parameter to store the platform id special value we needed to send for identification. task-4075847 Forward-Port-Of: odoo/odoo#177841 Forward-Port-Of: odoo/odoo#177300
Original PR description
For Mercado Pago to recommend odoo to customers they needed two changes: 1) Send a unique external reference to identify payments 2) Send the platform-id header to identify how many people use the integration. This PR addresses both: 1) Utilize the pos_reference field (uid) to identify records 2) Use a system parameter to store the platform id special value we needed to send for identification. task-4075847 Forward-Port-Of: odoo/odoo#177841 Forward-Port-Of: odoo/odoo#177300
2 changes
Resolved issues and error corrections
Clicking a device in the IoT area could show an error because of how the request was handled. This change updates the request method so users can open device details without that disruption.
Original PR description
There was an error message when clicking on a device in IoT model, due to a null value on a `$.ajax`. We replaced it by a simple `fetch` request.
1 change
Resolved issues and error corrections
This fix updates how WhatsApp message reactions are processed by replacing outdated partner and guest references with a unified personas system. This ensures the WhatsApp integration continues to work correctly with the latest client-side changes and prevents reaction-related errors.
Original PR description
`partners` and `guests` are not handled in the client side anymore. They should be replaced by `personas`.
Miscellaneous changes
**Steps to reproduce** 1).Log as Mitchell, create an appointment, and set Joel as an attendee 2).Log as Joel, open the appointment page, and cancel -> Cancellation mail is not sent **Before this PR** A cancellation email is only sent when the person who books the appointment cancels the appointment. **Technical** https://github.com/odoo/enterprise/commit/46f1b8aaeaa94d3ac7b72784a8fa7120f8a3e8a5#diff-394903898ffdd9f9e1f053ecda2afd00cda86d6cc96159268fbe4fefc62f3a83R187 Before the abo
Original PR description
**Steps to reproduce** 1).Log as Mitchell, create an appointment, and set Joel as an attendee 2).Log as Joel, open the appointment page, and cancel -> Cancellation mail is not sent **Before this PR** A cancellation email is only sent when the person who books the appointment cancels the appointment. **Technical** https://github.com/odoo/enterprise/commit/46f1b8aaeaa94d3ac7b72784a8fa7120f8a3e8a5#diff-394903898ffdd9f9e1f053ecda2afd00cda86d6cc96159268fbe4fefc62f3a83R187 Before the above commit we were archiving the meeting if there are < 2 attendees in the event. So now we restore that condition with the current conditions **After this PR** Now, a Cancellation email will also be sent if an event contains less than 2 attendee after the cancellation. Task-3975493 Forward-Port-Of: odoo/enterprise#68642 Forward-Port-Of: odoo/enterprise#64238