Repository navigation
Conversation
|
@CarlosRoca13 Good point, thanks — done: |
|
@etobella please check this important change |
carlos-lopez-tecnativa
left a comment
There was a problem hiding this comment.
This error probably isn't related to this PR, but since the migration PR has been merged, could you check it? When I tested without this PR, the error didn't appear, but now, with these changes, I get this error. Maybe I just didn't notice it before and it was already there. I think it's more related to the migration.
etobella
left a comment
There was a problem hiding this comment.
Technically and functionaly ok.
According to AI Policy, Claude cannot be author/co-author, you should use assisted-by. Can you check that?
746983d to
8a4c942
Compare
|
@etobella Thanks for the review! Done — the commit now uses |
luisDIXMIT
left a comment
There was a problem hiding this comment.
Tested on runboat, LGTM! Thanks for your work!
|
@carlos-lopez-tecnativa Thanks for spotting this — your fix is applied in 8a4c942 (router.stateToUrl). Could you take another look when you have a moment? |
|
/ocabot rebase |
|
Congratulations, PR rebased to 19.0. |
|
Sorry to rebase again, but the new CLA Bot is there, and I want to check that everything works nicely /ocabot rebase |
The conditions of the "New Partner" and "Open Contact" thread actions started an async searchRead and then re-rendered the owner. Conditions are evaluated on every render, so this re-rendered DiscussContent while it was still mounting and the Owl fiber never completed: Discuss showed no messages in any channel. The gateway partner and the single guest of the channel are now sent with the channel store data, and the conditions only read them. Fixes OCA#319 Assisted-by: Claude Opus 5.5
_to_store runs for every channel of the user on Discuss load: search res.partner.gateway.channel once for the whole recordset instead of once per gateway channel.
stateToUrl is not exported by @web/core/browser/router in 19.0 (only through the router object), so building the URL of a gateway message failed as soon as such a message was rendered. It went unnoticed while Discuss did not render any message.
|
Congratulations, PR rebased to 19.0. |
8a4c942 to
96f2134
Compare
|
@vgavinas I think you need to sign the CLA |
|
@etobella Done — CLA signed, the check is green now. Thanks! |

Fixes #319.
The
condition()of theopen-gw-new-partnerandopen-gw-profilethread actions started an asyncsearchReadand then calledowner.render(). Conditions are evaluated on every render, soDiscussContentwas re-rendered while still mounting and the Owl fiber never completed: Discuss showed no messages in any channel, without any error in the console.Now the gateway partner of the channel and its single guest (if any) are sent with the channel store data (
gateway_partner_id,gateway_guest_id), and the conditions only read them. After the guest is managed, the channel data is fetched again, so "Open Contact" replaces "New Partner" without reloading.Tested on Odoo 19.0 CE with oca/mail 19.0 + #321 and a live WhatsApp Cloud API test number: Discuss shows the messages again, "New Partner" is shown for a guest sender and becomes "Open Contact" after creating the partner.
mail_gatewaytests: 0 failed, 0 errors (2 tests added).