TOPIC: Sorting by date and time is not correct in fornt-end

I create two events repeating daily. One event has a time slot of 17:00-17:30, the second event has a time slot of 17:30-18:00.
Registrations are open 6 weeks before the event and close 5 minutes before event start.

I'm using in event listing a setting of Past events set to hide and sort by newest first.

The front end shows the events correctly by date and time however only for the period the registration is open. When the event is not open yet for registration (thus all events 6 weeks from now) seem not be sorted at all.

Is there any other way to get the sorting right?


After creation of the repeating event, I also see in the backed that the sorting of the "sub" events are random as well.

Is there a way I can hide all events which are not open yet for registration? Unpublish event(s) in the back-end is not an option because manual selection of the events is painful due to random sort order of the "sub"event.

System J1.5.22 DT register 2.7.2e.
I Have tried the saem on the demo system and that shows exactly the same issues.

Please hlep.
Thanks

Update
I checked in some more details. The sorting issue is related to repeating events. The sorting of these "sub" events seem to be random at least it is not following any date rules or eventid. If you set the ordering to newest first you get the oldest in date first, which I think is wrong and the longer the list the more random the order becomes.

The more repeating events you add the more the sorting order is getting a mess. It tries to follow some sorting rules for dates, however I cannot discover the rules and it just goes from one date to another and back again. It is a real mess.

Has anybody found a clue how to fix this or is there a patch I may have missed?
Thanks

i am also seeing this and it is a big problem for me.

Any repeating events do not seem to be sortable in front or back end for me. specifically for me i need to find an event in the csv export area it is almost impossible as they are in seemingly random order.

On the front end i need to be able to show the next event first going down to the furthest time away last. i dont seem to be able to do this in any way.

Pls Hlp

You're correct.
Sorting is impossible and is in nearly random order. Also when you open the repeating event in back-end and save gain, the sorting order is changing.

With some 12 repeating events each covering some 200 days (so total 2400 events) the extension becomes useless.

I have two tickets outstanding on repeating events, one related to this the other related to loosing all registrations after save of a repeating event. Sofar, I have one reaction on it acknowledging the issue on losing registrations. On the other (sorting) I have total radio silence.

I'm sure they are very busy with solving all kinds of other bugs, but no reaction at all is not giving much hope.

Another issue I discovered with sorting is that the ordering field in the table jos_dtregister_group_event is limited to tinyint(3) menaing that the maximum number of events being ordered is 255. As repating events can span a much larger time frame you immediately will run into sort order issues.
Thsi explains part of the probelm I'm experiencing.

Still awaiting a solution to this sorting and the loss of registrations after save of repeating events.