error

  • Resolved koullis

    (@koullis)


    6 years, 2 months ago

    hello

    i keep getting this error lately

    analytics.js doesn’t exist or hasn’t been updated for more than two days. Try running Update analytics.js in Settings > Optimize Analytics to fix this. If this message returns in the next few days, make sure your cron is running healthy.

    any help to fix it is appreciated

    regards

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    Hi!

    Making this error a global one, was a feature request, which has been implemented in the latest update.

    But I’m getting the same on one of my sites. Is your site a low traffic site, by any chance?

    oprekin

    (@oprekin)

    6 years, 2 months ago

    same here, get this error, was try to running Update analytics.js in Settings > Optimize Analytics to fix this, but error still appear.

    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    @oprekin,

    Is yours a low traffic site, by any chance?

    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    Just to let you guys know. This is a confirmed bug, I don’t know what changed, but the implementation of the cron is faulty.

    I’ll keep you guys posted!

    Thread Starter koullis

    (@koullis)

    6 years, 2 months ago

    thanks for the update..let us know when this is fixed

    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    In the latest version I implemented a possible fix. Still testing it, though. Would be great if you guys could chime in on this.

    Thread Starter koullis

    (@koullis)

    6 years, 2 months ago

    i got error but dont remember if it was after new update or not.
    made manual update and got this notice about date

    “CAOS is running healthy. analytics.js was last updated on 2020-04-10 08:55:54 and the next update is scheduled on 1970-01-01 00:00:00.“

    • This reply was modified 6 years, 2 months ago by koullis.
    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    I’ve seen that one come by as well. Strange thing is, is that I can’t reproduce the issue. So it must be an issue with server configuration. I think wp_next_scheduled() is returning null (0) at some point, which, when formatted, returns 01-01-197 00:00:00.

    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    6 years, 2 months ago

    But, luckily, it’s just a wrongly formatted string. It doesn’t, by definition, mean that the cron isn’t running correctly.

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

The topic ‘error’ is closed to new replies.