Events 2.0 message and venues/organizers error

[Diego]

Hi, we are seeing all post types (posts, downloads, EDD payments…) in both venues and organizers.

Furthermore, we are seeing this text in all the event pages in the admin, our current version of TEC is 3.4.1 and EDD Tickets 3.4:
Welcome to Events 2.0! This is a HUGE upgrade from 1.6.5. Please make sure you have backed up before proceeding any further. You can easily revert to an old version if you want to backup first. This upgrade includes two major steps, migrating data & updating your templates as necessary. There have been significant changes to the template tags and functions. Check out our walk-through on the upgrade before proceeding and check out the FAQ & Knowledge base from the support page. If you’re new to The Events Calendar, you may want to review our new user primer.
You have events that need to be migrated. Please visit the bottom of the settings page to perform the migration.

Any idea what’s going on?

Thanks!

[Barry]

That definitely doesn’t sound right :-/

Can you confirm which version of The Events Calendar you are using? That piece of text is not even within our 3.x codebase to the best of my knowledge.

Every now and again we do come across other themes/plugins which bundle their own (sometimes out of date) copy of The Events Calendar, and so you should also try deactivating all other plugins and switching to a default them to check if this behaviour persists – though making sure your copies of our plugins are up-to-date ought to be the first priority here.

Does that help?

[Diego]

Well Barry, your answer is not very comforting… Firstly, we said already the version we are running in order to save time. Here it goes again: TEC 3.4.1 and EDD Tickets 3.4 on WP 3.8.1
Secondly, every time we have a problem with TEC/EDD Tickets by default we are told to deactivate all plugins and switch to default theme, no matter the nature of the problem.
Anyway, the problem persists making the obvious steps like deactivating everything and reinstalling the plugin. The piece of text is part of your 3.4.1 release. A simple search shows it in line 64 of tribe-the-events-calendar-import.class.php
The problem appears to be self::hasLegacyEvents() but we created all events on TEC 3.3.1 and then upgraded to 3.4.1 Anyway, we also tried to delete all events and still the message displays…
In our opinion, the question here is how is possible that TEC 3.4.1 thinks that we have legacy events from 1.x? And moreover, how can be a possible solution in TEC 3.x upgrading to 2.0?

[Barry]

Hi Diego,

Apologies first of all for missing that. Yes, you’re quite right.

With regards to your first few points, you’re obviously pretty frustrated and I’m sorry about that.

I did see that you had listed the version numbers in use on your site, but given I couldn’t locate that string initially (my fault) I felt asking you to confirm the version numbers was a sensible step – believe it or not, people routinely supply us with the wrong information.

Often we do recommend the standard steps of deactivating other plugins and switching to a default theme – that’s partly because, where it makes sense to do so, we treat each separate problem as a standalone case – so if you post a number of different threads then yes, it’s quite likely we will ask this a number of times. However, we do not always do so and we also provide a field you can complete to indicate you carried out these steps when you create threads, which you are free to take advantage of.

I hope that explains where we are coming from and sorry once again for failing to meet your expectations here. To the issue at hand:

In our opinion, the question here is how is possible that TEC 3.4.1 thinks that we have legacy events from 1.x? And moreover, how can be a possible solution in TEC 3.x upgrading to 2.0?

We clearly need to amend this on one or more levels and I’ll make a note for that to happen. Right now though the logic seems to be that it is looking for any posts containing event meta data that have also been categorized with the events term (and here I am referring to regular ‘post categories’).

Have you integrated your events with regular categories and do any of them belong to an Events category? If so, can you even if only temporarily remove that code and/or recategorize them?

Does that make sense?

[Diego]

Hi Barry,
we do not have categories in events. I deleted all regular posts. Also all regular categories except uncategorized. I deleted all events also but it was not working, still get the message. Finally, i deleted all EDD downloads related to tickets but i still get the message. No idea how this is triggered.

[Barry]

That is strange. Do you remember the version of The Events Calendar/Events Calendar PRO you first installed on this site (even approximately)? Could you have had or generated events with an early 1.x release?

[Diego]

Yes, we installed first TEC version 3.3.1. We decided for TEC like a month ago, so nothing from 1.x should be there.
We researched a bit on our own. hasLegacyEvents() seems to be the origin of the problem.
On line 188 is tested whether legacy event exist or not:
public static function hasLegacyEvents() {
return count( self::getLegacyEvents( 1 ) );
}
On line 232 of tribe-the-events-calendar-import.class.php is defined the function getLegacyEvents()
For example, we do not see the message “Install has 1 or more legacy event!”. Actually, like said, we do not have events, so we are clueless on how getLegacyEvents() can be true.

[Barry]

OK. I’m going to need some insight into what is being returned when the legacy query runs. Would it be possible for you to add this snippet to your theme’s functions.php file? Within the admin environment you then ought to see something like this near the top of the screen:

Of course, the actual data may be something other than array (size=0) in your case and if so it would be interesting to see what it is. Beyond that, can you confirm which version of PHP you are using within your hosting environment?

[Diego]

Thanks Barry for taking the time of creating the snippet. We added to our functions.php and certainly the result is other than an empty array, here is the result:

Debug information array(1) { [0]=> object(WP_Post)#551 (24) { [“ID”]=> int(523) [“post_author”]=> string(1) “1” [“post_date”]=> string(19) “2014-02-10 02:58:48” [“post_date_gmt”]=> string(19) “2014-02-10 01:58:48” [“post_content”]=> string(14) “My description” [“post_title”]=> string(7) “Spende2” [“post_excerpt”]=> string(0) “” [“post_status”]=> string(7) “publish” [“comment_status”]=> string(6) “closed” [“ping_status”]=> string(6) “closed” [“post_password”]=> string(0) “” [“post_name”]=> string(7) “spende2” [“to_ping”]=> string(0) “” [“pinged”]=> string(0) “” [“post_modified”]=> string(19) “2014-02-10 02:58:48” [“post_modified_gmt”]=> string(19) “2014-02-10 01:58:48” [“post_content_filtered”]=> string(0) “” [“post_parent”]=> int(0) [“guid”]=> string(51) “http://example.com/?post_type=download&p=523” [“menu_order”]=> int(0) [“post_type”]=> string(8) “download” [“post_mime_type”]=> string(0) “” [“comment_count”]=> string(1) “0” [“filter”]=> string(3) “raw” } }

Please note that i changed our site url for example.com

After that, i was deleting the post #523 and here is the new result:

Debug information array(1) { [0]=> object(WP_Post)#434 (24) { [“ID”]=> int(454) [“post_author”]=> string(1) “1” [“post_date”]=> string(19) “2014-02-08 03:11:02” [“post_date_gmt”]=> string(19) “2014-02-08 02:11:02” [“post_content”]=> string(16) “[bitpay_payment]” [“post_title”]=> string(24) “Bitcoin: Payment Process” [“post_excerpt”]=> string(0) “” [“post_status”]=> string(7) “publish” [“comment_status”]=> string(6) “closed” [“ping_status”]=> string(6) “closed” [“post_password”]=> string(0) “” [“post_name”]=> string(23) “bitcoin-payment-process” [“to_ping”]=> string(0) “” [“pinged”]=> string(0) “” [“post_modified”]=> string(19) “2014-02-08 03:11:02” [“post_modified_gmt”]=> string(19) “2014-02-08 02:11:02” [“post_content_filtered”]=> string(0) “” [“post_parent”]=> int(4) [“guid”]=> string(54) “http://example.com/checkout/bitcoin-payment-process/” [“menu_order”]=> int(0) [“post_type”]=> string(4) “page” [“post_mime_type”]=> string(0) “” [“comment_count”]=> string(1) “0” [“filter”]=> string(3) “raw” } }

Of course the page checkout/bitcoin-payment-process we cannot delete, it is a part of the checkout process of EDD.

Any ideas?

[Barry]

OK. I’ve amended that snippet slightly. Can you try once more time and see what we get if you change it to match this one? The primary change is to let us see what if any terms are applied to the post and which meta fields might exist.

If it were not for the fact that you had deactivated all other plugins except for those by Modern Tribe and had switched to a default, unmodified theme already I would strongly suspect a conflict here where some other component filters and modifies queries – but of course that doesn’t seem to be the case based on what you’ve detailed so far … but, hopefully, this one will shed some further light on the issue.

Thanks!

[Diego]

This is the result with plugins activated:
Debug information ID=539 | TYPE=page | TERMS= | FIELDS=_edit_last:Array _edit_lock:Array _alp_processed:Array

This is the result without plugins (only EDD, TEC and EDD-Tickets):
Debug information ID=560 | TYPE=edd_payment | TERMS= | FIELDS=_edd_payment_meta:Array _edd_payment_user_id:Array _edd_payment_user_email:Array _edd_payment_user_ip:Array _edd_payment_purchase_key:Array _edd_payment_total:Array _edd_payment_mode:Array _edd_payment_gateway:Array wpml_language:Array

[Barry]

OK: thanks for running through those steps.

There are two key things I’m noting here – the first is that our code to detect legacy event data is looking for posts which meet specific conditions. Bizarrely, what it seems to be digging up (in your case) are posts that do not meet those criteria. The second notable facet of this is that yours is the only thread I’m aware of describing this particular issue.

To be honest I’m struggling to think of other options here, unless another piece of code somewhere is interfering with queries – of course, the basic troubleshooting steps you have already followed ought to have caught that.

Can we try things in reverse: can you set up, perhaps in a subdirectory within the same environment, a new WordPress installation and install only our plugins (avoid EDD and EDD Tickets at first, then introduce them after testing with just The Events Calendar). Does the problem happen at that point? Assuming for the moment it does not, can you add the same stack of themes/plugins as you do on your live site and see if the problem then surfaces?

The aim of this is threefold: to do a final check for anything that was missed during troubleshooting sofar, to determine if there might be something in the live site database that triggers this, and finally to verify if there might be some sort of environmental reason for this behaviour.

Thanks!

[Diego]

Hi Barry, this troubleshooting we cannot afford in our production environment, moreover when the rest of the functionality seems to be intact. I am already getting trouble trying to justify internally the resources spent on this issue that, as said, appears to be only cosmetic, i hope you understand it.
At this point, the most efficient for us would be waiting until the next version of your detect legacy event code is released and test again then.
When is that planned in your roadmap?
Thanks!

[Diego]

Hi Barry, we found the origin of the issue. The origin was not TEC, sorry for all the trouble.
Actually, this error was somehow related to a very different one that we had in EDD but we could not see the connection until today. Here it is explained:
https://easydigitaldownloads.com/support/topic/recent-purchases-on-edd-widget-stay/
Anyway, you may want to update the legacy text that invites to upgrade to version 2.
Thanks!

[Barry]

Closing this thread as it’s been quite a while – of course if we can help with anything else please do create a new thread. Thanks!

[Author]

Posts