Hello,

The ordering will use date time of the event.

And if the same, it will be depending on the ID of each event.

Maybe an idea (didn't test it if it works...) is to add 1 second for the start datetime of the event to be after the other one, as second not display on frontend, but could be manually included in the datetime picker input.

But check too the id. Maybe best for an order in creating the event, for example, always first Standard, and second VIP (or the other order).

For information, many improvements are planned for the registration system and many to come in the next months. One of the feature i've planned is the possibility to have different ticket (seat) for one event (example : children, adults... or in your case: "VIP", "standard") each one with different settings, and possibilities to have paiement (in pro versions) for tickets with paypal.
So, many things in process (and to come in the next 3/6 months) to give better functionnalities and flexibilities to manage registrations tickets, and much more for the Pro versions

Best regards,
Cyril

I tried the trick with the start date/time but unfortunately it did not work. The seconds are being stored as you mentioned but it does not have an impact on the sort mechanism.

I was wrong... in fact, i've already removed seconds before ordering is process...

In fact, the idea would be to introduce new options as ordering... i add it in my todo list for when it will be possible

However, there is one case (two entries with same time/date) where I still have a reverse order in the event list on the front page.

Well, this is curious about this one, as id is the only database ordering proceeded in SQL request... Ordering on date is done before list display.

Do you have an online link to this list ?

Regards,
Cyril

Hi!

I understand the ordering difference for ID !
Well... not the human logic, but PHP logic...

16 is before 6 because "1" comes before "6" (does not take into account the full number...

That's why the difference...

Will check if this is a "php" ordering or due to Joomla api's for sql request...

Hello,

Yes this is the reason, but i will see to fix it for next release (it is in my list of todo things for next 3.6.7)
And to have a real ID ordering.

Regards,
Cyril