You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just thought you should be aware of the problem when showing events from another site in EE using the MSM; essentially the RSVP stuff will only work on the MSM site where the channel originates.
EE 2.6.1
MSM 2.1.5
Here is an example of the template tag we are using that doesn't work. It's on a "community" MSM site showing events from an "events" MSM site:
Works fine if the template is used within the actual "events" site the "all-events" channel is ("RSVP is enabled" is visible). Just not in any other MSM site.
All of the exp:rsvp tags have the same problem.
I think the problem is
function get_rsvp_event_by_id($entry_id)
not returning anything when the tag is used on MSM sites. EG: in mod.rsvp.php, the function if_rsvp_enabled (line 51),
Thanks for the report. From memory RSVP does not actually support MSM, so this may be a limitation you will have to live with. Happy to accept a pull request if anyone wants to take it on though.
Just thought you should be aware of the problem when showing events from another site in EE using the MSM; essentially the RSVP stuff will only work on the MSM site where the channel originates.
EE 2.6.1
MSM 2.1.5
Here is an example of the template tag we are using that doesn't work. It's on a "community" MSM site showing events from an "events" MSM site:
Works fine if the template is used within the actual "events" site the "all-events" channel is ("RSVP is enabled" is visible). Just not in any other MSM site.
All of the exp:rsvp tags have the same problem.
I think the problem is
not returning anything when the tag is used on MSM sites. EG: in mod.rsvp.php, the function if_rsvp_enabled (line 51),
doesn't return anything (so the condition fails).
Wish I could help more, but I'm definitely not a PHP dev. Hopefully this makes enough sense.
The text was updated successfully, but these errors were encountered: