• We got this error twice yesterday, running My Calendar 3.1.8, WordPress 5.4.1. I don’t think we’ve previously seen this error (and we’ve been running My Calendar for years). Any ideas? Thanks.

    Kim

    May 09, 17:45:18

    Fatal error: Uncaught Error: Call to a member function getTimestamp() on boolean in /wp-includes/functions.php:191

    Stack Trace
    1.
    date_i18n(‘F’, 5192789048531315840)
    /wp-content/plugins/my-calendar/my-calendar-output.php:2679
    2.
    my_calendar_prev_link(Array, ‘F’, ‘month’, 1)
    /wp-content/plugins/my-calendar/my-calendar-output.php:2271
    3.
    mc_nav(Array, ‘list’, ‘month’, 1, ‘mc-37da6d457a7c…’)
    /wp-content/plugins/my-calendar/my-calendar-output.php:2119
    4.
    mc_generate_calendar_nav(Array, ‘all’, 1, 1, ‘mc-37da6d457a7c…’, false, Array, ‘164552936250-01…’)
    /wp-content/plugins/my-calendar/my-calendar-output.php:1708
    5.
    my_calendar(Array)
    /wp-content/plugins/my-calendar/my-calendar-shortcodes.php:68
    6.
    my_calendar_insert(Array, ”, ‘my_calendar’)
    /wp-includes/shortcodes.php:343
    7.
    do_shortcode_ in /home/onenameg/public_html/wp/wp-includes/functions.php on line 191
    [internal function]:0

Viewing 1 replies (of 1 total)
  • Plugin Author Joe Dolson

    (@joedolson)

    This looks like it might be a core error. At least, I can’t clearly see how it would be caused by My Calendar right now. It’s being *triggered* by My Calendar, but I can’t see an error that’s in My Calendar.

    It could have something to do with your timezone setting; you may want to check that in the WordPress General Settings.

Viewing 1 replies (of 1 total)
  • The topic ‘Fatal error on getTimestamp()’ is closed to new replies.