|
Kevin Griffey
|
April 17, 2013 at 4:07 pm
I saw an earlier post about the same subject, but it was closed to comments and I was wondering if it had been resolved. Like the earlier post, Event Espresso is conflicting with Timely All-in-one calendar plugin. I am not using the EE calendar add-on, but it is throwing the times on my AIO calendar off by 5 hours. Would really like to get both to play nice together. Any ideas?
|
|
Josh
|
April 17, 2013 at 4:32 pm
I’m not sure. I tried to install all in one event calendar on a test site to investigate this and what happened was it threw an error when I tried to activate it. The error was “The plugin does not have a valid header.”
When I can get a chance to look into why that happened I’ll try to take a look. Please understand that we cannot guarantee 100% compatibility with all plugins in the WordPress ecosystem. Sometimes there can be overlap between plugins that share similar functionality which may be the case here as well.
|
|
Josh
|
April 17, 2013 at 4:40 pm
Update: I got past that initial installation hiccup and created an event with the All in one calendar plugin and the times display as expected. It might be a setting or something that you can change, but the default settings seem to work fine as I can’t reproduce this.
|
|
Kevin Griffey
|
April 18, 2013 at 9:29 am
Thanks for checking that out. I’m wondering if it has anything to do with the fact that it is receiving from google calendar feeds.
|
|
geobstel
|
April 18, 2013 at 9:50 am
I was the one who originally posted this topic and it was closed, but I never did hear anything about a solution: https://eventespresso.com/topic/plugin-conflict-with-all-in-one-event-calendar-by-timely/
I had someone (not affiliated with EventEspresso) suggest that I remove function *date_default_timezone_set* from the event espresso plug-in source code. This worked temporarily, however that has changed and I’m back to having the same issue – events are off by +4 hours.
I’d be happy to help in any way to get this resolved as quickly as possible. Please let me know.
Thanks.
|
|
geobstel
|
April 18, 2013 at 9:57 am
Update: I guess when I updated my EventEspresso plugin, that function was included. Removing it resolved my problem once again.
date_default_timezone_set
|
|
Josh
|
April 18, 2013 at 11:56 am
@geobstel
Thanks for the update. I’ve made a note in the issue tracker about using the date_default_timezone_set function. There might be a better way to accomplish what that’s doing.
|
|
geobstel
|
April 18, 2013 at 12:02 pm
Thanks Josh. Although I thought it resolved that problem, the issue is not totally dead. It appears that events checked as “all day” in my iCal calendar feed are being displayed on the following calendar day. The only solution I have found is to establish start and end times even though it’s an all day event (i.e. 8am-5pm).
I’m not sure if this issue is directly related to the first or not, but hopefully it can be examined, as well.
Thanks.
|
|
Kevin Griffey
|
April 18, 2013 at 1:30 pm
Thanks geobstel – I think that worked for me, at least as a temporary fix. Now to remember this fix after the next update.
|
|
Kevin Griffey
|
April 18, 2013 at 1:56 pm
Well, it doesn’t quite fix things. When I paste the short code for an EE event into the body of one of my All-in-One Calendar events, it changes the time of the event on that page. The calendar still appears to have correct times but the event page is showing wrong. Out of curiosity, I pasted the short code into different events with the same result. It shifts the time 5 hours.
|
|
Kevin Griffey
|
April 18, 2013 at 1:59 pm
Also, the time shows correctly when editing the page, it only displays the wrong time when viewing the actual event page.
|
|
Sidney Harrell
|
April 24, 2013 at 11:02 am
Can you change the first line of registration_page_display.php to be:
<?php echo date_default_timezone_get();
and then view the event registration page. It should give you a line at the top with the timezone that is being used on the frontend. If you are getting different times on the frontend than the backend, then maybe the timezone is being affected somehow.
|
