known issue RSVP leave Webhook

[LADR]

Hello,

I've implemented webhook for RSVP status change. It works well for RSVP going and not going. But when a user is leaving an already joined event, there is no trigger. Is it a bug ? Because regarding the documentation, it should triggger for a change "Fired when somebody changes his RSVP status".

 

Regards

[Daniel F]

I can't reproduce this, it's working fine for me.

In fact the same webhook is fired for all 3 RSVP states, you have to look for the "action" parameter in the payload, which can be "yes", "no" and "maybe"

[LADR]

18 hours ago, Daniel F said:

I can't reproduce this, it's working fine for me.

In fact the same webhook is fired for all 3 RSVP states, you have to look for the "action" parameter in the payload, which can be "yes", "no" and "maybe"

@Daniel F

Action "no" is for : no I'm not coming. But there is no statut and no call when someone cancel their subscription.

[Daniel F]

Can you please explain what exactly you mean? It is also fired when one changes his status

[LADR]

@Daniel F When I click on "Leave event", the webhook is not fired. So i'm not aware when someone leave the event. So if it should be fired, there is an issue, because it does not work on my side on this case.

 

 

[Daniel F]

4 minutes ago, LADR said:

@Daniel F When I click on "Leave event", the webhook is not fired. So i'm not aware when someone leave the event. So if it should be fired, there is an issue, because it does not work on my side on this case.

 

 

Thanks a lot! I can confirm that it's missing here. I have filled a bug report for this and a missing language string which I noticed while testing this.

[LADR]

13 minutes ago, Daniel F said:

Thanks a lot! I can confirm that it's missing here. I have filled a bug report for this and a missing language string which I noticed while testing this.

Thanks. Can you inform me when the issue will be fix ?

[Daniel F]

2 minutes ago, LADR said:

Thanks. Can you inform me when the issue will be fix ?

I have just pushed the fix to our repo. Once it was reviewed and approved, it will be shipped in a future release:)