Wednesday, August 9, 2023
11 changes · master
Enhancements to existing features
Odoo now refreshes the relevant business data more reliably after certain on-screen actions are completed. This helps users see up-to-date information without needing extra manual reloads, reducing confusion and improving workflow continuity.
Odoo now has a more targeted way to recognize guest users when they access mail, discussion, public page, and live chat features. This helps make guest access more consistent while avoiding unnecessary processing on unrelated requests.
Original PR description
This PR adds the `add_guest_to_context` decorator in order to provide a generic way to extract the guest from a request. It will be used to unified guest extraction from cookie/param based on its provenance (external livechat/public page). This is better than the `pre_dispatch` method since it can be applied to specific routes instead of adding this logic to every request. part of task-3332628
Website editor drag-and-drop rules are now defined directly on the relevant building blocks, helping prevent users from placing form fields or tables of contents in invalid locations. This makes page editing more reliable and reduces the chance of broken layouts or unsupported content structures.
Original PR description
Since [1] form fields cannot be moved outside of their form and since [2] table of contents cannot be nested within another table of content. Those were implemented with specific references to website classes within web_editor. This commit introduces declarative mechanisms for both situations: - `data-drop-lock-within`: prevents dropping outside the closest parent that matches the specified selector. - `data-drop-exclude-ancestor`: disallows dropping within a parent that matches the specified selector. [1]: https://github.com/odoo/odoo/commit/638d0e875dcb05191fe833d2f889235891dfb46a [2]: https://github.com/odoo/odoo/commit/55339cd6a7b7916184893c0fe27b5483683a047a task-3131384
This update reorganizes and strengthens the internal structure behind Odoo's mail services. It helps developers catch integration issues earlier and makes the mail module easier to maintain, with minimal direct impact on day-to-day users.
This update improves internal test support for scenarios where visitors or guests interact with messaging, live chat, calendar, and related website features. It helps Odoo validate future guest-based live chat and messaging behavior more reliably before it reaches users.
Original PR description
*: bus, calendar, im_livechat, web, website_livechat. This PR adds the possibility to set the current user during tests as well as the mail guest. This will be used to test mail guest page and livechat once the visitors will be treated as guests. part of task-3332628 enterprise: https://github.com/odoo/enterprise/pull/45331
When a forum question is deleted, users are now taken back to the forum home page instead of staying on the deleted question page. This avoids a confusing dead-end experience and makes navigation clearer after deletion.
Original PR description
before this commit, on deleting a question from forum is redirecting to the same question page with deleted tag. after this commit, user will be redirected to forum home page after deleting a question --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo users can now see more details about their IAP services and available credits directly from Odoo. They can also update warning settings, access their IAP accounts more easily, and buy credits from the account form.
Original PR description
Description of the issue/feature this PR addresses: Refactoring some IAP functionalities Current behavior before PR: - Very minimal view of IAP accounts Desired behavior after PR is merged: - Information about services available to view from odoo - Can edit some iap services fields from odoo - Change the redirect route of view services to view my IAP accounts --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The forum post form now only shows closing-related fields when a post is actually closed. It also limits answer-specific fields to child posts, making the form clearer and reducing confusion for users managing forum content.
Original PR description
before this commit, in the forum post form view, the closing related fields, is visible even if the post is not closed and question field should not be shown in the parent post. after this commit, closing fields will be shown only once post is closed and parent_id and is_correct field will be shown only in child post(answer) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update supports the broader rollout of voice messages in Discuss chats and channels by ensuring related document workflows are covered in testing. It helps maintain reliability for users sharing and managing documents alongside chat conversations.
Original PR description
Adding voiceMessageService to document's tests. This PR is associated with [PR #117036](https://github.com/odoo/odoo/pull/117036) Task-3240168
Customer records can now store default Mexican e-invoicing values for payment way and Uso. These defaults flow into sales orders and invoices, reducing manual edits and saving time for repeat or subscription customers.
Original PR description
Before it is added 'Payment way' had to be updated manually in invoice. What does it do - 'Payment way' now updatable in sale_order and the set value is used when creating an invoice. - 'Payment way' and 'Uso' are now setable on the customer sheet; the values are used as default when creating a sale order and/or invoice. How does it work Use compute function to set the values, values are recomputed everytime the costumer is modified on the sale order or invoice. The compute functions read the partner_id relevant field values to check if they are set. task-3388110
The Documents app test coverage now includes scenarios for guest and dynamically created users. This helps ensure shared document workflows remain reliable for users who are not standard internal employees.
Original PR description
part of task-3332628 community: https://github.com/odoo/odoo/pull/130811