Sunday, June 29, 2025
7 changes · saas-18.4
Resolved issues and error corrections
The website builder now displays only the relevant chat panel at a time, avoiding duplicate conversations. Visitors' live chat appears while previewing the website, while the internal web client chat appears during editing so staff can use editor-specific chat features.
Original PR description
Before this commit, website builder page was showing 2 chat hubs at once: - chat hub from the web client - chat hub from the website (live chat) The website builder is in web client so makes sense to…
Before this commit, website builder page was showing 2 chat hubs at once: - chat hub from the web client - chat hub from the website (live chat) The website builder is in web client so makes sense to enable chat windows from web client. Some feature are specific to backend and need to be shown while editing the website. The website builder also previews how the website look. Therefore it makes sense to show website chat hub because it's part of the actual website page being previewed. The problem with showing the 2 chat hubs is that chats are duplicated due to being shown in both hubs. The chats are intended to be seen from the website so the underlying problem is showing both chat hubs at once. This commit fixes the issue as follow in website builder: - when not editing the website, show the website chat hub and hide the web client chat hub - when editing the website, show the web client chat hub and hide the website chat hub. This works because web client chat features at desired when actually editing the website. Viewing the website hub when not editing the website works because this is the actual showing of website with the website chat hub. There's also no feature on website editor that affects the website chat hub.
Miscellaneous changes
Previously, when using SDI on a child branch, the file name was generated using the branch’s sequence. However, since we now send invoices using the parent company’s proxy setup, this could lead to duplicated sequence numbers between the parent and its child companies. To reproduce: - Create an Italian company and a branch with the same VAT and Codice Fiscale. - Send an invoice from the parent to SDI - Send another from the branch: duplicate file name error since the sequence is the same f
Original PR description
Previously, when using SDI on a child branch, the file name was generated using the branch’s sequence. However, since we now send invoices using the parent company’s proxy setup, this could lead to duplicated sequence numbers between the parent and its child companies. To reproduce: - Create an Italian company and a branch with the same VAT and Codice Fiscale. - Send an invoice from the parent to SDI - Send another from the branch: duplicate file name error since the sequence is the same for both companies. We can fix this by using the parent company to generate the file name when relevant. Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4881219) opw-4881219 Forward-Port-Of: odoo/odoo#215782
Added the dirty hook `_get_additional_robots_rules_web` to allow modules to add extra rules to the robots.txt file whenever it's needed. Previously, it was blocking all the user-agents when we didn't have website installed. Part of https://github.com/odoo/enterprise/pull/85990 opw-4726371 Forward-Port-Of: odoo/odoo#216137 Forward-Port-Of: odoo/odoo#211734
Original PR description
Added the dirty hook `_get_additional_robots_rules_web` to allow modules to add extra rules to the robots.txt file whenever it's needed. Previously, it was blocking all the user-agents when we didn't have website installed. Part of https://github.com/odoo/enterprise/pull/85990 opw-4726371 Forward-Port-Of: odoo/odoo#216137 Forward-Port-Of: odoo/odoo#211734
After the new design applied for the appointments pages, the propagation of the params was removed when clicking on the appointments cards. This was leading to issue to access the corresponding records when sharing a link to multiple appointments for which the user didn't have access like the unpublished ones. task-4893791 Forward-Port-Of: odoo/enterprise#88330
Original PR description
After the new design applied for the appointments pages, the propagation of the params was removed when clicking on the appointments cards. This was leading to issue to access the corresponding records when sharing a link to multiple appointments for which the user didn't have access like the unpublished ones. task-4893791 Forward-Port-Of: odoo/enterprise#88330
To reproduce: ============= - Activate and set up the SMS authentication for the Sign app. - Send a document for signature request with sms validation for a contact. - Go sign the document via the signature request link, sign and validate. - validate the recieved code and you will get the error: 'Error message: Sorry, an error has occurred. Please complete the document again.' Problem: ======== when constructing the signature request link, we retrieve the `accessToken` from `props`, wh
Original PR description
To reproduce: ============= - Activate and set up the SMS authentication for the Sign app. - Send a document for signature request with sms validation for a contact. - Go sign the document via the signature request link, sign and validate. - validate the recieved code and you will get the error: 'Error message: Sorry, an error has occurred. Please complete the document again.' Problem: ======== when constructing the signature request link, we retrieve the `accessToken` from `props`, while `accessToken` is not defined in the `props` of the `Document` component. Solution: ========= `accessToken` is defined directly in the `Document` component we can retreive it from `this.accessToken` opw-4813339 Forward-Port-Of: odoo/enterprise#88333
Allows the use of less expensive models. GPT-4 is much more expensive than 4o and 4.1. Forward-Port-Of: odoo/enterprise#88781
Original PR description
Allows the use of less expensive models. GPT-4 is much more expensive than 4o and 4.1. Forward-Port-Of: odoo/enterprise#88781
Lately we have seen that when trying to upload to Instagram throught the media link, the request is blocked by the robots.txt file. This is because Facebook crawler is trying to access our image url and it is not being able to get the image in their side. This commit tries to add this user-agent to the robots.txt for both when we have and do not have website installed, without altering any of the existent templates. This will silently add it for website, so the user will be able to modify the
Original PR description
Lately we have seen that when trying to upload to Instagram throught the media link, the request is blocked by the robots.txt file. This is because Facebook crawler is trying to access our image url and it is not being able to get the image in their side. This commit tries to add this user-agent to the robots.txt for both when we have and do not have website installed, without altering any of the existent templates. This will silently add it for website, so the user will be able to modify the robots.txt file if needed, but won't be able ot remove it. Community side: https://github.com/odoo/odoo/pull/211734 opw-4726371 Forward-Port-Of: odoo/enterprise#88667 Forward-Port-Of: odoo/enterprise#85990