Viewing 6 replies - 1 through 6 (of 6 total)
  • It’s the pm that causes the problem. The plugin regards pm as being after midday and then calculates the elapsed number of seconds. The datestamp thinks it needs to add 12 hours making it midnight. Remove the pm and it works.

    I’m going to add a filter to the plugin to ignore the pm if the time has a 12 in it.

    Thread Starter sirih

    (@sirih)

    The inclusion of the pm was the final my attempts to get the order right. I have reverted to my previous format which was to use the first field only in Time and input 12.00-2:00 for the first event and 2:00-3:30 for the second event. (I have also used the first field for start time and second field for end, which makes no difference to the ordering of the events.)

    In a further attempt to get them ordered, I also edited the Published date so that the second event was published after the first (the later event was in fact added to the events list before the earlier event).

    As you can see at https://religion.utoronto.ca/, they still refuse to play nice!

    The problem is the 2.00. This is interpreted as 2 o’clock in the morning (02.00). Have you tried changing this to 2pm – 3.30pm?

    Thread Starter sirih

    (@sirih)

    OK, this tweak has done the trick, thank you.

    I can see that a problem arises from my using what is regarded as 24-hour formatting to express the time (i.e. I should say 12:00-14:00, not 12:00-2:00). I don’t like to use 24-hour expression, as a slip of the brain in many people will somehow ‘see’ something like, 16:00 as six o’clock.

    Just to be clear: QEM regards 12:00 as noon; noon is 12 pm; midnight is 12 am; and 00:00 in the 24-hour clock – correct?

    Thank you for your help – much appreciated.

    If you contact me through the plugin website I will send you an update that fixes the 12 o’clock problem.

    Even 12pm can cause problems for some people. For me it means midnight.

    But so does 12am. Which is why don’t use AM and PM. Normally you won’t have a problem, it’s only when you have multiple events on one day it all goes a bit pearshaped.

    Update sent and installed and it all works OK. Update added to V5.10

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Event Ordering by Time – Noon seems to confuse QEM’ is closed to new replies.