• Resolved TrishaM

    (@trisham)


    I’m getting the following message in both my Dashboard (overview) and the Simple History page (under the Dashboard sub-menu):

    “Hm, the log could not be loaded right now. Perhaps another plugin is giving some errors. Anyway, below is the output I got from the server.

    There has been a critical error on your website.”

    I’ve enabled debugging in WP using define(‘WP_DEBUG’,true) as well as logging and combed thru my log…..there are a few minor PHP warnings, but no “critical errors”……

    I’m on WP 5.3.2. I was able to see my Simple History log last week and have made no changes recently.

    Hoping there is an easy fix…….

Viewing 4 replies - 1 through 4 (of 4 total)
  • I’ve been getting the same error. In my case I’d just had to re-install the server so was assuming it was connected with that and went down a few false leads.

    But it also was, for me anyway, an easy fix. The problem was caused by a bad plugin, specifically the WP-GPX-Maps plugin which had an update recently, and clearly from the review comments, it has caused a few problems.

    Disabling this plugin also solved another problem I was having, which was plugin searches not returning any results. The spinner would spin indefinitely.

    Thread Starter TrishaM

    (@trisham)

    Hi @dougienisbet – interesting, I don’t use that particular maps plugin, but i’m sure you’re right that I have a conflict somewhere with another plugin so I’ll explore that route….I don’t allow anything on my site to auto-update (even though I do regular backups), call me paranoid but I like to do all updates manually after I’ve backed up and test everything in between each (plugin) update….things have improved much in recent years, but too many experiences of things going haywire – or even crashing – after something updated itself has left me very wary!

    Plugin Author P?r Thernstr?m

    (@eskapism)

    It’s difficult to say why you see this message but most likely it’s a conflict with another plugin. And my guess is that something has changed, for example WordPress has updated, another plugin has updated, the server has updated. I would disable all other plugins and see if the history loads fine. If it loads, then enable the other plugins one-by-one until you find the one that causes the error.

    Thread Starter TrishaM

    (@trisham)

    Thank you @eskapism – I appreciate the reply! For whatever reason it started, it cleared up on its own within the last day or so….I’ll be sure this is marked as ‘resolved’ if it isn’t already.

    In any case, thank you so much for such a great plugin – I love it and use it on all of the sites I manage!

    • This reply was modified 4 years, 8 months ago by TrishaM.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Getting “Hm, the log could not be loaded…”’ is closed to new replies.