Event order incorrect when using tribeHideRecurrence

Home Forums Calendar Products Events Calendar PRO Event order incorrect when using tribeHideRecurrence

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #779481
    northpointe
    Participant

    When reoccurrences are hidden events are displayed in the wrong order…

    A fix I found is adding MIN to (tribe_event_end_date.meta_value) as EventEndDate on the post fields function. There does seem to be a slight performance dent though… https://gist.github.com/neverarriving/fcc23db7c7eb68250d26

    #781356
    Barry
    Member

    Hi northpointe,

    I’m sorry you’re experiencing difficulties, but thanks for reaching out – I’d love to get a little more context on this one if I can.

    • Just to be clear, you mean that this happens when the Recurring Event Instances setting (“show only the first instance of each recurring event (only affects list-style views” found in Events > Settings > General) is enabled?
    • Is it actually the main list view that is impacted or some other view/all other views?
    • I see you already tried our standard troubleshooting steps which is awesome: can you confirm if that enabled you to identify any conflicts that might be at work here?

    Thanks!

    #781545
    northpointe
    Participant

    The problem surfaces on list views with the option enabled, and/or when using the tribehiderecurrence query parameter. Here’s the incorrect SQL being outputted https://gist.github.com/neverarriving/4ef72e49536732a375ea
    … When an event is repeated the query incorrectly grabs whichever end date it wants rather than the first one (Like the start date), which results in incorrect ordering.

    It surfaces on all views, I was able to confirm the problem at the SQL level using the Query Monitor plugin.

    #794247
    Barry
    Member

    Hi northpointe,

    Apologies for the delay: for some reason the thread wasn’t marked as being in need of a further reply – sorry about that.

    This isn’t something I can replicate locally, but it does sound similar in nature to a reported bug we thought we had fixed in 3.8. At this point I’ve got just a few more questions:

    • Is this something you can reproduce after running through our standard troubleshooting steps?
    • Can you point me to a live example of the problem?
    • I see you noted that you are using 3.8 – just for the avoidance of doubt, is that the version you are using of both The Events Calendar and Events Calendar PRO?

    Thanks!

     

    #794342
    northpointe
    Participant

    Yes, it occurs after standard trouble shooting, switching out the theme etc… I’ve updated our installation with the patch I built in the gist above (Putting MIN before end_date) so it is working now at http://northpointe.org/events/, but you can see the issue in these screenshots with the standard query http://cl.ly/image/2x2Q1O2y1Y0m http://cl.ly/image/2j0c2y0A3D3x … It should be noted that the repeating events all occur on the same day.

    And yes I’m running both The Events Calendar & Pro
    Thank you!

    #810081
    Barry
    Member

    I apologize again, northpointe – as the same forum bug as before meant we did not see your reply as quickly as we should have done.

    Thanks for following up, though – it’s much appreciated. Would it be possible to get a database dump (which you might share via Dropbox or similar, posting the link here as a private reply)?

    #816355
    Barry
    Member

    Hi northpointe,

    We’ve dropped the proverbial ball on this thread a couple of times in that we didn’t see your updates on the last two occasions as promptly as we should have done – and so I just wanted to check in and ensure you saw my last update and see if that is something you want to explore further?

    Thanks!

    #849669
    Barry
    Member

    Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘Event order incorrect when using tribeHideRecurrence’ is closed to new replies.