[Tojo John]

Sure, here is the info you asked for:

1. WP Timezone: America/New_York
2. Server Timezone: America/New_York
3. Screenshot attached
4. Defaults to America/New_York and we do not change them. The affected events are showing America/New_York

Thanks,
Miah

[Tojo John]

Hunter,

After the latest update of the Events Calendar plugins, the ordering issue seem to have resolved.

However, if we keep the debug more on, we see a number of calendar related error notices here and there.

Some of it was in our theme template which was copied from a version more than a year ago. We updated our template to rid of such notices by removing all deprecated functions and hooks.

But there are still some error notices remaining that is not coming from the theme customization. Please let me know if we need to create a new support post for this. If not, what we need to do to resolve this.

Thanks,
Miah

[Tojo John]

We will carry out your requests for testing and follow up.

Miah

[Tojo John]

Hi,

We have more information about this and need your team’s urgent attention on this.

After taking some of the actions you recommended (i.e. turning on debug mode and importing data to a fresh WP install without any other plugins), doing further tests and making observations, we documented several findings and are more certain of the issue and need your tech/dev team to get involved for resolving this issue.

Here are the findings:

1. The Issue is Persistent: Even in a fresh WP install with our event data imported, the events for a specific date in the grid/month view are not always ordered by start date/time. The issue persists and is consistent from our live site to the fresh WP install.

We were also able to replicate this in a fresh WP install even without importing our data, by simply adding test events.

2. Start Date is not always Getting Priority for Sorting: When we played around with the events of a specific date, we noticed that events start to reorder within that date when an event is updated/modified without changing the start date. Meaning, the logic your team has used to order events in the month view grid cell (specific date) has something to do with last_update_date or other fields and EventStartDate is not always taking precedence for some reason. This needs to be investigated and corrected by your team.

By any standard and acceptable logic of developing calendars, events should be normally ordered by start date – not anything else, if unless someone has a special scenario. This is extremely important and all of our clients using your plugin are requesting that your team needs to look into this and correct this issue as soon as possible.

3. Error Notice: On debug mode, while logged in as a subscriber, there is a WP DB error on the month view. Here are the printed details from the website:

WordPress database error: [Unknown column ‘wp_postmeta.meta_value’ in ‘field list’]

SELECT DISTINCT wp_posts.*, MIN(wp_postmeta.meta_value) as EventStartDate, MIN(tribe_event_end_date.meta_value) as EventEndDate FROM wp_posts LEFT JOIN wp_postmeta as tribe_event_end_date ON ( wp_posts.ID = tribe_event_end_date.post_id AND tribe_event_end_date.meta_key = ‘_EventEndDate’ ) WHERE 1=1 AND wp_posts.post_type = ‘tribe_events’ AND (wp_posts.post_status = ‘publish’ OR wp_posts.post_status = ‘acf-disabled’ OR wp_posts.post_status = ‘tribe-ea-success’ OR wp_posts.post_status = ‘tribe-ea-failed’ OR wp_posts.post_status = ‘tribe-ea-schedule’ OR wp_posts.post_status = ‘tribe-ea-pending’ OR wp_posts.post_status = ‘tribe-ea-draft’ OR wp_posts.post_author = 5 AND wp_posts.post_status = ‘private’) ORDER BY EventStartDate DESC, wp_posts.post_date DESC LIMIT 0, 1

We have some very important businesses like the Harvard Club of NYC and the Olympic Club that are using your plugin for their websites and our clients take serious issues with the wrong sorting behavior reported above that impact their businesses and user base in a negative and critical way. We urge that your team takes this issue with the same seriousness and offers prompt solutions to the issues listed above. We are here to offer additional info including access to our staging environment, if needed.

Thank you for your cooperation.

Miah Morshed.

[Tojo John]

Andras,

We tried to implement your recommendation of using GUID. But when we tested, we realized that any time the software re-generates events with new ID and the GUID is also changed because the GUID has date and post ID listed in it.

I will try to remember to come back and ask for this ticket to stay open.

When your team can look into this, it would be great if they can add and give us a hook that we can call when such changes happen. The hook could pass us possible matches of events where dates stayed the same but IDs changed, so we can change the IDs of our child post type objects.

Thanks,
Miah

[Tojo John]

We have to try what you’re asking on our staging environment and possibly give you access to our site/code base.I have to schedule that with our client.

For now, here is a screencast that shows the symptom from http://www.hcny.com – Harvard Club of NYC. Please notice how the events at the bottom of the date box is an earlier time than the ones on top. I gave two examples but we have many more.

I am not sure if this is a bug because it has always been like this for us. We assumed this is how the program was coded. Only recently the number of complaints about it has increased so we contacted your team on this.

Please don’t close this thread as we get budget/approval for doing more tests as you have asked.

Miah

[Tojo John]

Andras,

That is interesting. I guess I will talk to my team to see if we can tie in GUID and improve the situation. However, I would really interested to learn what new feature in 4.5 can help with this scenario.

Ideally, if your team can add a new hook (action or filter …) that we can utilize when such things happen, so we can keep the child objects (i.e. the event staff) of a recurring event continue to link to the same event after such changes.

I will keep this thread open for a little longer to allow my team to work with your recommendation.

Miah

[Tojo John]

We can make that work from the code snippet you provided.

Thank you,
Miah

[Tojo John]

Cliff,

Thank you for the response. This is not going to work for us since we don’t show the WP Admin Bar on the front-end of the website.

I’d like our developers to replicate those “Edit Event” links on the front-end UI. I can see that most of it is quite straightforward but some links include a wp-nonce (_wpnonce) parameter. We’d need to know what the ‘action’ value for generating the nonce is.

I am assuming it is something like “$nonce = wp_create_nonce( ‘some-action-name’ );” – if you’re supplying a custom action name, please let us know what it is.

Is there anything else to this? Can you please direct us so we can get this implemented on our custom UI?

Regards,
Miah

[Tojo John]

I guess, we will play around with the info from other thread you gave a link to and custom search box to disable the AJAX search.

Is it possible to keep this thread open until we get a resolution?

Miah

[Tojo John]

Geoff,

We went through a massive amount of testing on our staging website and finally figured this out with a multi-step process.

1. We manually deleted ALL auto-save and ALL revisions – not something we were too inclined to do
2. We manually connected all child events to their parents

It seems now the events are updating as expected (not locked anymore). FYI – these locked events included some events that were not recurring – jus stand long single events.

Thank you for all of your responses.

Miah

[Tojo John]

I just had a discussion with my editorial team. It looks like the issue is a lot worse than I originally thought.

They now have multiple events that behave the same way (as if locked) and not all of them are recurring events and there was no auto-save message. Also, this happened after we disables the auto-save feature.

This is becoming a great concern. We really need your help. Is there any way to connect with your team over the phone?

Thanks,
Miah

[Tojo John]

We actually did find the auto-save and deleted it from the DB (with backup before that of course). Strangely, that did not unlock the set of recurring events. Is it possible that the recurring events are linked to each other and removing the single auto-save we found in the DB is not enough to resolve this?

I am still scratching my head on this. Please let me know if you have ideas.

Thanks,
Miah

[Tojo John]

We have updated the modernizr tool so it is no longer giving that warning. And we have already disabled auto save by increasing the auto save interval to a very long length of time (30 days) so it never fires. Hopefully this will solve the issue going forward.

However, the existing set of recurring events that we are unable update, remains as such. How do we get back to updating these events again?

Thanks,
Miah

[Tojo John]

I knew it would be something simple. Thank you for clarifying and the quick response.

Miah

[Author]

Posts