|
J
|
April 18, 2016 at 1:54 am
Hi All
We have EE3.1.32.2 and are based in Sydney, Australia.
The iCal import link we have on our event registration pages shows the wrong date across all events (1/1/1970). There is probably an easy fix but I haven’t been able to put my finger on it – your help would be appreciated.
Regards
Joe
|
|
Tony
|
April 18, 2016 at 6:22 am
Hi Joe,
The latest version of Event Espresso 3 is 3.1.37.8 and I would highly recommend updating to that version.
WP 4.2 introduced multiple security features that cause problems with older version of Event Espresso (mainly due to events/price name lengths) and we added fixes to the latest versions of EE3 to prevent that.
In either case, can you link me to an event I can view the iCal on please?
|
|
J
|
May 3, 2016 at 6:40 am
Thanks Tony
Sorry about the delayed reply. Here is the link to one of our event registration pages showing the issues with the Ical: https://lawsense.com.au/register-law-for-aged-care-managers-qld
We looked at updating,but were informed that updating would remove some of the modifications we have made so we ended up delaying this. We have had some issues with registering attendees with long names/ email addresses and more than 4 attendees- is that the sort of issue you mean?
Regards
Joe
|
|
Tony
|
May 3, 2016 at 2:43 pm
It could be yes, values exceeding their expected length will now cause problems within WP 4.2+ so it’s a possibility.
Registering more than 4 attendees shouldn’t be a problem but it will also depends on the modifications you have to your version of EE.
The problem with the iCal is being caused by the date format you are using to output the dates. The formatted date is being passed to strtotime() which does not work well with some formats. We have a branch of EE3 that has fixes for this here:
https://github.com/eventespresso/event-espresso-legacy/tree/BUG-9342-ical-using-formatted-dates
You will need to apply the changes from:
includes/functions/ical.php
and
templates/registration_page.php
From within that branch to your version of Event Espresso to work around this.
|
