Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • upgraded to 1.10.11-standard

    I didn’t read the changelog, and what effect it would have on my calendar or to my website. As such, it’s a mistake I won’t make again.

    1) Changing Timestamps property to an Integer
    2) All scheduled events start and stop times 16 hours earlier
    3) Recurring events are in a different time zone (16 hours earlier) (sensing a pattern)
    4) I’ve tried to find a fix, scour the support and didn’t find.
    5) All In One Version 1.10.11-standard would cause several other plugin’s to fail and would cause the Install Plugin page on my Dashboard to be blank.

    I tried twice to reactive the All in one and twice it’s the deactivation that resolves the issue. There won’t be a third try.

    Guess what?! I quit.
    As soon as I have a replacement calendar up, running and updated, this plugin is gone.

    No need for a reply… not interested.

    Upgraded to 1.10.11-standard was the biggest mistake EVER!

    It’s screwed up ALL of my dates and times. My mistake was NOT reading the release information! NEVER AGAIN will I trust any updates unless I read and study the release info and understand the impact.

    First of all, who the hell changes database properties. Time Stamp properties from a datetime to an integer.

    Now, all views of my calendar views (calendar, poster board and agendas are all affected. I’m still learning PHP, but I understand data, databases. It’s too late to roll back to a restored version as it’s been a few days and I do NOT want to lose any other updates of work by other people.

    So, is that a fix, a patch that will fix what appears to be a time zone difference? It appears the update didn’t include the link to the WordPress Default Time zone (for us, it’s Los Angeles aka UTC-8

    https://www.d57tm.org/calendar/

Viewing 2 replies - 1 through 2 (of 2 total)