bjstarmans
Forum Replies Created
-
Thank you, although this doesn’t actually work either so you may want to review again. I’ve followed a similar guide for a different plugin though and have been able to set it up correctly by substituting the oauth for this plugin.
From SiteGround after many back and forth tickets:
SG Optimizer, the latest version introduced a Wpephpcompat checker and it is likely the cause and nothing to be alarmed about.
For anyone who did not check their Securi logs, there were two entries per plugin. One that set from from private to published and another that deleted the published version. They happened within a minute or so of each other.
Did anyone else who had this happen at SiteGround on the 27th have the HackAlert service? Wondering if these alerts were generated during the process when SG recently changed the scanning service from HackAlert to SG Site Scanner.
I’ve had the same on several websites. The alerts included both
‘Wpephpcompat_jobs (private to published)’
and shortly after a corresponding ‘Post deleted’. My host assures me this was nothing that they were running and that they believe it was related to my wp-cron process that maybe needed a re-initialization of some sort or due to some other update / dependency actions that were (automatically or not) imposed via your website’s internal mechanics.