Hi Franklin, hi McKillo,I tried to reproduce this on clean test sites (Joomla 6.1.4, site timezone Europe/Amsterdam).
BackgroundThe field
(the event start converted to UTC) was added in JEM 5.0.1. Since 5.0.1 the JEM Basic Module sorts Upcoming and Unfinished events on that field first, and only then on date and time. Up to 5.0.0 it sorted on date and time directly. An event with an empty or wrong
is therefore sorted in the wrong place, regardless of its date. For example, an empty value always ends up at the top.
What I tested on a fresh JEM 5.0.1 installationHow the event was created
correct?Backend form: without time, with time, multi-day, custom timezone (New York)yesFrontend formyesSave as copy with a new date; changing the date of an existing eventyesUnpublish/publish from the listyes (unchanged)CSV import (JEM format, "Replace" on and off, even when the file contains an old or empty
)yes, recalculatedExternal import: CSV, JSON, ICSyesUpgrade 5.0.0 → 5.0.1 with existing events (including a recurring series)yes, recalculated by the installer
Recurring event: dates generated in 5.0.1no: every generated date gets the
of the first dateWith only individually created, non-recurring events, the module showed the correct order on 5.0.1 (next event first), both with "Upcoming" and "Unfinished". With a weekly series, the generated dates were listed too early, before events that actually come sooner.So with events created by hand and without recurrence, I could
not reproduce a reversed order on a clean 5.0.1. That makes me think something in the data is different. Possible causes:
- events created before 5.0.1, where the recalculation during the update did not run or did not finish (for example an interrupted update, or files copied manually instead of installed);
- changes made directly in the database or by another extension;
- in "Unfinished" mode, events that have started but not finished (for example multi-day events) are correctly shown first, as McKillo explained.
How to check (phpMyAdmin, read-only)Replace
with your table prefix:
Code:
SELECT id, title, dates, times, enddates, start_utc, recurrence_first_id
FROM jos_jem_events
WHERE published = 1
AND dates >= CURDATE() - INTERVAL 7 DAY
ORDER BY dates, times;
should be the date and time of the event converted to UTC: in summer 2 hours earlier than Dutch time, in winter 1 hour; without a time, it is the day before at 22:00 or 23:00. If an event at the top of your module has an empty or clearly different
, that is the cause. The output of this query, or a screenshot of it, would help a lot.
Workaround on 5.0.1 (tested)Make a backup first. Then install the same JEM 5.0.1 package again via
System → Install → Extensions (upload
over the existing installation). The installer recalculates
for all events. On my test site the module showed the correct order again afterwards. Events and settings are kept.
Fix in 5.0.2The current JEM 5.0.2 beta 1 package (refreshed on 15 October) contains McKillo's fix "Fix module event ordering and recurrence UTC dates". I tested it:
- new recurring dates get their own correct
;
- an empty value is sorted by its real date;
- existing wrong values are repaired during the update.
Hope this helps!
