Error in logs

  • Resolved Dave

    (@go3asy)


    9 years, 6 months ago

    Any ideas? Plugin would appear to work fine, but I have to keep clearing log files

    PHP Fatal error: Uncaught exception ‘Exception’ with message ‘DateTime::__construct(): Failed to parse time string (LcAocQKiQYosn-01) at position 0 (L): The timezone could not be found in the database’ in /home/nhsforth/public_html/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php:3555
    Stack trace:
    #0 /home/—-/public_html/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php(3769): DateTime->__construct(‘10121985-01’)
    #1 /home/—-/public_html/wp-content/plugins/the-events-calendar/public/template-tags/month.php(290): TribeEvents->previousMonth(‘10121985-01’)
    #2 /home/—-/public_html/wp-content/plugins/the-events-calendar/public/template-tags/month.php(243): tribe_get_previous_month_link()
    #3 /home/—-/public_html/wp-content/plugins/the-events-calendar/views/month/nav.php(22): tribe_events_the_previous_month_link()
    #4 /home/—-/public_html/wp-content/plugins/the-events-calendar/public/template-tags/general.php(89): include(‘/home/nhsforth/…’)
    #5 /home/—-/public_html/wp-content/plugin in /home/—-/public_html/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php on line 3769
    [30-Sep-2014 23:35:10 UTC] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘DateTime::__construct(): Failed to parse time string (10121985-01) at position 7 (5): Unexpected character’ in /home/—-/public_html/wp-content/plugins/the-events-calendar/lib/the-events-calendar.class.php:3769

    My server is WHM/Cpanel and running London/Europe time and wordpress set to london so it shouldn’t be a timezone issue on the server side.

    https://wordpress.org/plugins/the-events-calendar/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Brook

    (@brook-tribe)

    9 years, 6 months ago

    My apologies for our delay in response, I missed this topic last week when we do our do pass.

    First thing I would do is update the plugin if you have not already. That error comes from someone or something inputting an invalid date. This could happen if another plugin is doing something like replacing the boostrap datepicker with one of its own. Someone might have been trying to hack your site, or even just a robot attempting to post spam. Either way their attempt would be foiled because there input is cast as a date. But, since they are not inputting a proper date an error is thrown.

    If you see this issue crop up in the logs again you might consider doing a conflict test. But, if it is just a one-of problem you probably will not be interested in spending more time on it. http://tri.be/support/documentation/testing-for-conflicts/#test-for-conflict

    Please let me know if you have questions. Cheers!

    – Brook

    Thread Starter Dave

    (@go3asy)

    9 years, 6 months ago

    This is not a one off I have been getting it regularly. Nobody can publicly post anything kn the site and it’s fairly locked down on the admin side. Only company IP address etc can access.

    I never had it when first outing the plugin on our site which was only recently and shortly after we put the plugin on there was an update of which its on he latest then I noticed these logs. Any ideas?

    Brook

    (@brook-tribe)

    9 years, 6 months ago

    Well that is terrible. I think we might have encoutnered another person with a similar issue. Checkout the last couple of comments in this thread, do either of the solutions work for you?

    http://tri.be/support/forums/topic/multisite-you-do-not-have-sufficient-permissions-to-access-this-page/

    If that does not help, have you had a chance to do a conflict test yet? That could shed a lot more light here.

    – Brook

    Plugin Contributor leahkoerper

    (@leahkoerper)

    9 years, 5 months ago

    It’s been a month since we last heard from you, so in accordance with our forum guidelines I’m marking this thread resolved. Thanks for your support!

    ~Leah

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Error in logs’ is closed to new replies.