mitchie wrote:Hello Geraint,
Thanks for your explain.
I understand very well the background of Jevents. If you designed the code like this you have your reasons. I would have done in another way, to let user have access/edit to each single repetition. In a theatre scenario you could need to edit just 1 repetition (for example for weather condition). In this case you don't need to edit all repetition and for users could be much easier to edit just one event instead to re-enter all event repetition data. Better, in this case user can edit the repetition to highlights canceled (or postponed) the repetition. It could allows to list each repetition in the data-range events list. It even could allows users to add more than 1 repetition for each day (sometimes theatre have 2 repetition in 1 day) or have different (not regular) intervals. But it is just to share an idea.
That is my point - JEvnets allows the Theatre to change repeats because of public holidays, bad weather etc. The problem is AFTER making these changes if the main primary event date/times are changed then we can no longer guaranteed to be able to match the newly generated repeats with the exceptions that have been created.
Yes, my scenario is a non-repeating event with a menu link pointing to it. Sometimes I need to edit the date/time and in this case it breaks the menu link.
However, with Jevents v3.0.2 I cannot use SEO anymore because Jevents doesn't works at all (even without edit the event). It just show the events list for the current date... and not the event details.
The SEF Urls for non-repeating events work fine for my site UNTIL I edit and change the date/time and then they change. I'm looking today and relaxing this constraint for non-repeating events so that you can edit and change the date/time of non-repeating events without changing the URLs.