Forum Replies Created
-
AuthorPosts
-
nrcaknightsParticipant
I was able to resolve the issue by moving my code into the content.php file for the month view.
nrcaknightsParticipantGreat! I installed the update and the mobile calendar is displaying correctly. Thanks for the fix.
Doug
nrcaknightsParticipantSorry I forgot to include the code I’m using in the custom month.php file to get the month. Here is the code:
$date_array = explode("-", tribe_get_month_view_date()); $month_shown = tribe_wp_locale_month($date_array[1], full);
I then just stick this in a div.
Thanks,
Doug PennynrcaknightsParticipantThank you for the response. I will be looking for the update.
Sincerely,
Doug PennyAugust 21, 2018 at 9:53 am in reply to: Imported Events not Updating or Deleting (now with Google Calendar) #1602317nrcaknightsParticipantI will test this with Event Update Authority set to overwrite changes. However, bases on the link you sent me we should be able to have Event Update Authority set to “Import events but preserve local changes to event fields.” and the events should be updated, with the exception of any fields that were editing through The Events Calendar. There is nothing on the knowledgeable page provided that states event does will not be updated with preserve local changes is selected.
August 18, 2018 at 8:51 am in reply to: Imported Events not Updating or Deleting (now with Google Calendar) #1600427nrcaknightsParticipantThis reply is private.
nrcaknightsParticipantThis reply is private.
nrcaknightsParticipantThis reply is private.
nrcaknightsParticipantThe updated event shows correctly when I preview the import, but when the import is complete the event has not been updated. We are running scheduled imports every 30 minutes.
Thank you,
DougnrcaknightsParticipantThank you for that info. What about events that are modified or changed, for example a date change?
nrcaknightsParticipantJust following up on this issue. I’ve seen a couple of updates come out, but this doesn’t seem to be fixed yet. Any idea when we might see this land in a release version? I’m currently having to search my database everyday for “America/Tortola” and change it to “America/New_York” to work around this issue.
Thanks,
DougnrcaknightsParticipantThanks of the update Brendan. Any idea when this fix might be released?
Doug
nrcaknightsParticipantSure, attached is the file.
Doug
nrcaknightsParticipantAfter further research, I can confirm that events are being imported/created with the Aggregator plugin with the timezone set as America/Tortola. After doing some queries in the database, I found that all of the events imported from the feed provided above are being created with “_EventTimezoneAbbr” set to “AST” and “” set to “America/Tortola”. I did a mass find and replace for all of these events and changed them to “EST” and “America/New_York” and all of the events are now displaying correctly. Obviously this is a temporary solution since any new events will be created with the wrong timezone.
It seems like the Aggregator plugin is interpreting the iCal feed incorrectly and assigning the wrong timezone to the event. For reference, here is the timezone portion of the iCal feed:
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONEI either need some information on where the timezone is interpreted and inserted into the event post or a hook that can be used to check each event post being created so I can check the timezone and adjust as required.
Thanks,
DougnrcaknightsParticipantI’m not at my computer right now, but yes, when I click the link it allows me to change the time zone. If I change the time zone to New York, all of my events display with the correct time.
After more investigation, I’m guessing that the issue is happening when the Aggregator plugin is importing the events. For some reason it is a signing the incorrect time zone to the event when it is being created.
-
AuthorPosts