Naz
Staff member
Not currently, no. It's super easy to add support for it though so I may try it and see how well it works in practice.Nifty! Does it check editor contents as well?
Not currently, no. It's super easy to add support for it though so I may try it and see how well it works in practice.Nifty! Does it check editor contents as well?
You get a notification if they RSVP. If they change their RSVP to something else, you'll get a notification for that too. If they remove their RSVP, you won't get a notification.If a user click on the "Changed your mind?" function do I get a notification?
They're displayed in RSVP order, IIRC.And are the users displayed according to the registration order?
Entire event but they'll be able to remove their RSVP for subsequent events.If i use reccuring events is it only possible to sign up for the next one? Or can one only register for the entire event, not for the individual days? :'(
This would me importent for me too :/If they remove their RSVP, you won't get a notification.
so you sign up for all days and then you must remove RSVP for subsequent events?Entire event but they'll be able to remove their RSVP for subsequent events.
Are you referring to 1.0.4?Got a nice little release coming up. Significant natural language processing improvements, widgets, stuff under the hood for venue and organiser support and some QoL stuff. Almost done.
That was 1.0.3, actually. I suspect you’re interested in the venue and organiser stuff? That’s mostly under the hood stuff so it isn’t quite ready at the moment but it’s coming along great. I hope to have that fully available in the next version so 1.0.5.Are you referring to 1.0.4?
The code is pretty standard and explicit in what it does. It just gets events that don't have a read date for that particular user, only gets visible ones and only considers events that were created AFTER read marking cut off (defined in options, usually 30 days). So by default, you'd only get new events that were created in the last 30 days that haven't been read by the logged in user.v1.0.4 caused ALL events to be triggered as new!
How do I fix this, for all users?
View attachment 837
Where is this? I don't recognise/find anything within /admin.php?event-calendar/options that look like mark read cut off date.only considers events that were created AFTER read marking cut off (defined in options, usually 30 days).
Yes, created_date was the issue. Apologies, thanks!I suspect that it might actually be related to your import. The same update was applied here and it works as expected. Did you maintain the original created_date's from your XenAttendo events?
Is it possible to include this feature?This would me importent for me too :/
It's a core XF option under "Threads, Discussions and Conversations".Where is this? I don't recognise/find anything within /admin.php?event-calendar/options that look like mark read cut off date.
No worries. My other hunch was a MySQL quirk which would've been annoying.Yes, created_date was the issue. Apologies, thanks!
There are notifications for subscribing / RSVP'ing.notifications for subscribing and unsubscribing
You mean for recurring events? No, not yet.subsequent insertion or removal of individual event days
if I'm not informed when a player signs out the whole thing doesn't help meThere are notifications for subscribing / RSVP'ing.
I don't follow that argument. The event planner needs to know everything. Imagine you strictly get NO notification that 50% have jumped of and due to time restrictions you check in very late and close to the actual event date, then your plans go down the toilet.Its a bit similar to putting someone on ignore or unfollowing them. its a negative action that people can get pissed about.
'Why are you not going to my event?'