[Robert]

Hi @George,

I’m happy to say I’m not seeing any errors on the import or the calendar page now. Thanks for your help!

Best,
Robert

[Robert]

Hi @George,

Thanks for your quick reply.

1. This is a customised version of the-events-calendar-filterbar. We actually found that this approach was a bad idea, because we can’t get future updates to the-events-calendar-filterbar without clobbering custom code. So, we are going to refactor this completely and use a standalone plugin that leverages filters/hooks where possible to achieve the same effect.

2. Are you saying deactivate just the PRO plugin before doing the import? I don’t think we can safely deactivate the free plugin, or the custom post types defined there won’t exist and the import will fail.

Let me know if this is what you mean, in #2 above, and I’ll try deactivating both PRO and the custom filterbar and see if we can get a clean error-free import that way.

Thanks again for your help!

Best,
Robert

[Robert]

Hi @George,

Thanks for your reply. I have posted a few private replies with system information and a link to download the WPXML file.

Note that stage.msia.org is the server we want to import to (target), and http://www.msia.org is the server we are getting the live events from (source). The system information for stage.msia.org that I sent shows all plugins active and our custom theme, but to reproduce this we also disabled all but EC and wp-importer plugins, and ran the 2014 theme. We still get the error messages in that case as well.

Looking forward to your thoughts! Thanks again.

Best,
Robert

[Robert]

This reply is private.

[Robert]

This reply is private.

[Robert]

This reply is private.

[Robert]

Thanks, Brian. That points us in the right direction and we’ll give this a try.

[Robert]

Hi Brian,

These are good clues, thanks. It’s all users (once an admin with Admin in English activated visits the page), so hence my suspicion of “cache poisoning”. We have the plugin deactivated for now, but I’ll check if Admin in English is modifying the top admin bar as well (I suspect it is!).

My aim will be to make Admin in English compatible with ECP if possible, since it’s really useful to our admins who don’t speak Spanish. Any pointers there appreciated as well.

Best,
Robert

[Robert]

Digging deeper, it appears the Admin in English plugin was causing a problem. The plugin itself would seem to behave as expected, but I believe some form of “cache poisoning” was going on here.

We are now trying to determine where the cache poisoning is happening–in an Event Calendar PRO cache for the month, etc.–or in our front-end Varnish caching for WordPress.

Is it possible that, if we browse Spanish URL endpoints with this plugin active, the Event Calendar Pro will pick up that an admin is browsing and set the wrong language (thus not being able to route the endpoint and giving a 404–in English)? Does ECP operate such a cache? And is it language-sensitive/language-aware?

Thanks for any pointers.

Best,
Robert

[Robert]

After flushing the WP rewrite rules and clearing the front-end cache, it now appears that these endpoints:

/es/events/fotos
/es/events/semana

are working without having to redirect to their English URL equivalents, whereas:

/es/events/mes
/es/events/hoy

still give a 404 if not redirected.

Very strange–any clues?

[Robert]

Thanks, Brian. As I say, if I can be of any help in moving the timeline along on an official release (answering questions, etc.) please don’t hesitate to contact me.

[Robert]

Hi Brian,

Would be great to get an update from the development team at some point as to whether and when they plan to support WPML fully. Also happy to answer any questions they might have about the sample code.

Best,
Robert

[Robert]

This reply is private.

[Robert]

Hey Barry,

I just wanted to update to give some good news. I inspected the code for the TribeEventsGeoLoc class, and it looks like it just assumes geolocation has already happened correctly if the _VenueGeoAddress property has been set. Our export was setting that value explicitly (but not setting _VenueGeoLat or _VenueGeoLng). Once we removed that, the script was able to detect that a geocoding was needed and execute. So, in the end, running:

wp eval 'TribeEventsGeoLoc::instance()->generate_geopoints_for_all_venues()'

from the command line did in fact loop through all of our outstanding venues and geocode them!

Many thanks for your help.

Best,
Robert

[Robert]

Hi Barry,

Unfortunately, running:


wp eval '$t = TribeEventsGeoLoc::instance(); var_dump($t->generate_geopoints_for_all_venues());'


gives back the integer value of zero (0). Do you think that could be because wp-cli is executing too soon? Or is it more likely to be some issue with the dataset? Again, when we manually update individual Venues in the wp-admin, they geocode just fine.

Thanks for any thoughts you can spare!

[Author]

Posts