Problems in Upgrading to Events Pro

[Mariruth Kennedy]

After upgrading to the Pro Version I receive this error both on front end and backend of site.
Fatal error: Uncaught exception ‘Exception’ with message ‘DateTime::__construct() [datetime.–construct]: Failed to parse time string (@) at position 0 (@): Unexpected character’ in /home2/metrowcc/public_html/wp-content/plugins/events-calendar-pro/lib/tribeeventspro-recurrenceinstance.php:13 Stack trace: #0 /home2/metrowcc/public_html/wp-content/plugins/events-calendar-pro/lib/tribeeventspro-recurrenceinstance.php(13): DateTime->__construct(‘@’) #1 /home2/metrowcc/public_html/wp-content/plugins/events-calendar-pro/lib/tribeeventspro-schemaupdater.php(56): TribeEventsPro_RecurrenceInstance->__construct(‘7250’, false) #2 /home2/metrowcc/public_html/wp-content/plugins/events-calendar-pro/lib/tribeeventspro-schemaupdater.php(38): TribeEventsPro_SchemaUpdater->convert_recurring_event_to_child_posts(‘7250’) #3 /home2/metrowcc/public_html/wp-content/plugins/events-calendar-pro/lib/tribeeventspro-schemaupdater.php(26): TribeEventsPro_SchemaUpdater->recurring_events_from_meta_to_child_posts() #4 in /home2/metrowcc/public_html/wp-content/plugins/events-calendar-pro/lib/tribeeventspro-recurrenceinstance.php on line 13

The only way to be able to access the website was to change the plugin name via ftp.

Events are being displayed using just the regular version of the plugin but
all events are displaying about four times. I checked the database and duplicate entries were made for them.

[Barry]

I’m sorry to hear you are experiencing difficulties. Can you confirm a few details to help us build up a better picture of what might have happened here?

• When you say you upgraded to the PRO, do you mean you did not previously use it or that you upgraded from an older version (if so, which version)?
• Alternatively, has the core plugin recently been updated from an older release?
• Last but not least could you visit Tools > Export and export only events, then share the resulting CSV file with us (via Dropbox or some similar service – even by uploading the file back to your blog – you can of course share the link as a private reply if you prefer)

Thanks 🙂

[Mariruth Kennedy]

This reply is private.

[nelly]

Hey Barry,

Today we updated from 3.4 to 3.5 and we also received that error. I tried both automatic update, and also deleting the current plugin & replacing it by uploading the new version.

It caused all sorts of memory errors and internal server error. So the site was down for a while.

I reverted back to 3.4 for Pro (although events calendar and community events are at 3.5) and everything is working.

Any light you can shed on the issue would be appreciated.

Thanks,
Karl

[nelly]

This reply is private.

[Barry]

This is pretty puzzling and it sounds like perhaps – for some reason – you have _EventStartDate entries in the database for one or more events, but those entries are empty.

We’re not sure why that would be or how that situation would arise, but we’re investigating ways to deal with this. One approach you could use in the meantime (though normally we don’t recommend editing core code, but if you feel fairly comfortable working with code and take some precautions like making a backup you should be good) is to open:

events-calendar-pro/lib/tribeeventspro-schemaupdater.php

Then locate the convert_recurring_event_to_child_posts() method, which begins on or near line 50. Within that, look for:

foreach($start_dates as $date) {
	$instance = new TribeEventsPro_RecurrenceInstance( $event_id, $date );
	$instance->save();
}

Change this to:

foreach($start_dates as $date) {
	if ( empty( $date ) ) continue;
	$instance = new TribeEventsPro_RecurrenceInstance( $event_id, $date );
	$instance->save();
}

Hopefully that provides you with a working solution until we can roll out a substantive fix.

Once again – our apologies for the inconvenience.

[Author]

Posts