• Resolved richsadams

    (@richsadams)


    Immediately after updating to v2.0.6 our feed displays the following warning three times:

    Warning: date() expects parameter 2 to be long, string given in /home/stluhcom/public_html/wp-content/plugins/google-calendar-events/includes/class-gce-event.php on line 55

    The events, etc. are displayed normally following the warning.

    Any help you can give us would be appreciated.

    TIA!

    Rich

    https://www.ads-software.com/plugins/google-calendar-events/

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Contributor Nick Young

    (@nickyoung87)

    Is this using a widget or the shortcode?

    Thread Starter richsadams

    (@richsadams)

    I’ve run into a second issue after updating to v2.0.6.

    We use W3 Total Cache. When I attempt to clear all caches I receive this error:

    Parse error: syntax error, unexpected T_IF, expecting T_FUNCTION in /home/stluhcom/public_html/wp-content/plugins/google-calendar-events/includes/class-gce-event.php on line 51

    Can you help us sort that out as well?

    Thank you.

    Rich

    Thread Starter richsadams

    (@richsadams)

    Sorry, this is using a widget in the sidebar. However when I view the the actual “feed” the same warning appears.

    You can view it here:

    https://stlukechurch.com

    https://stlukechurch.com/gce_feed/st-luke-church-portland-calendar/

    Thread Starter richsadams

    (@richsadams)

    Hi Nick,

    FYI I reverted back to v0.7.3.1 to avoid this issue for now. Please let me know if you need me to upgrade again to check out the problems noted above.

    Otherwise I’ll wait for the next update.

    This is a terrific plugin BTW and we really appreciate the hard work you’ve put into it.

    Best wishes,

    Rich

    Plugin Contributor Nick Young

    (@nickyoung87)

    Thanks Rich.

    I have not been able to reproduce this issue on my own setup. I can see potentially where the issue lies but I will be changing it blindly since I can;t really test it. Once I have something I may have you try it out for me to see if it gets the job done. I will keep you updated on that.

    Thanks for your help and pointing out this issue.

    Thread Starter richsadams

    (@richsadams)

    Thanks Nick and no problem. Thanks very much for your hard work on this great plugin!

    Plugin Contributor Nick Young

    (@nickyoung87)

    @richsadams,

    Could you please email me at [email protected]

    I am attempting to fix this, but would like your help since you can see the error and I can’t.

    If you would rather not then I understand.

    Thanks!

    Thread Starter richsadams

    (@richsadams)

    Hi Nick. I just sent you an email. Thanks very much!

    Plugin Contributor Nick Young

    (@nickyoung87)

    ( Comment removed, made a mistake )

    Thread Starter richsadams

    (@richsadams)

    Hi Nick,

    The most recent update, Version 2.0.6.2, resolved both of these issues. Everything is working perfectly now.

    Thanks for the awesome support and the terrific plugin!

    Best wishes,

    Rich

    Thread Starter richsadams

    (@richsadams)

    Apologies, I spoke too soon. v2.0.6.2 resolved one issue (W3 Total Cache error) but did not correct the warning problem. Although I cleared the cache I must have been viewing a cached version. Rolled back to v0.7.3.1 for now.

    Thanks for the continued support!

    Plugin Contributor Nick Young

    (@nickyoung87)

    Just released 2.0.7 please let me know if it resolves your issue.

    Thanks!

    Thread Starter richsadams

    (@richsadams)

    Hi Nick. Per my email, yes! It appears that v2.0.7 has resolved the last “warning” issue. So far it’s working perfectly.

    Thanks very much for all of your great work and support, it’s truly appreciated.

    Rich

    Plugin Contributor Nick Young

    (@nickyoung87)

    Thank you for confirming. Thanks for using the plugin!

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘v2.0.6 Update Creates Warning’ is closed to new replies.