Cheers - I'll take a look at that thread.
And re 2. - I'll explain in more detail...sorry, it's a bit of a long message, but there are possibly a few issues....
Basically, I think the links on the buddypress groups pages are a little confusing.
Firstly, if you're logged-in, when you visit the front end Group Events page (as per my url above), you see a list of upcoming events for that group - which is all fine!
However, (unlike if you're not logged-in) there's no way to view each event in the front end. (A bit frustrating... you have to find the event via another page, or log-out first.) An extra 'view event' link for each event would be great.
Secondly, I'm a bit worried that an ordinary user might not understand what's happening - for recurring events - when clicking on the links on this page. (In cases where they have the rights to edit these events.)
(When logged-in) clicking on the event title of a recurring event takes you to a front-end edit event page. Fine. But shouldn't it be more clear that if the event is edited, then this individual event will now be 'detached' from the series of recurring events??? (In the back-end, due to the labelling, it's clear that this will happen.)
Also, - perhaps more importantly as it could cause data loss - clicking on the right-hand 'Edit recurring events' link takes people to the 'My events' page.
BTW - not sure why you have to go through the 'My events page' to edit the event. Would it make more sense if the url pointed directly to the edit event page for that individual event???
Anyway, now clicking on the 'Edit recurring events' link on the 'My Events' page takes you to a front-end 'Reschedule Events' page editor. However - unlike in the back-end - there's no warning message:
"WARNING: This is a recurring event.
Modifications to this event will cause all recurrences of this event to be deleted and recreated and previous bookings will be deleted! You can edit individual recurrences and disassociate them with this recurring event."
I'm presuming that this still applies, regardless that the recurring event is being edited in the front-end.