bonjon9
Forum Replies Created
-
I got the same report, plus one that the backup.php file changed.
It was:
if (file_exists($fullpath.’/.donotbackup’)) {
$updraftplus->log(“Skip directory (.donotbackup file found): $use_path_when_storing”);
return true;
}and now that is deleted.
This is for version Updraftplus 1.9.17Forum: Plugins
In reply to: [Contact Form DB] after update to v2.8.4 get error message trying to activatesame here – help please! Can’t get back to site at all.
Forum: Plugins
In reply to: [Contact Form DB] after update to v2.8.4 get error message trying to activatesame here – help please!
Found the answer. Sorry for bugging anyone here.
In case someone is looking for this issue, here’s what the developer of UpdraftPlus said on that forum:
“The fault is in Google Analyticator – on every page load, it loads an old, incompatible copy of the Google SDK (instead of only loading it when needed) – which pollutes the function space for other plugins. The fatal conflict comes because of it being an old version, which conflicts with the new version. There’s no opportunity for another plugin to load its version of the Google SDK.
I’ve added some code in UpdraftPlus to specifically detect Google Analyticator, and prevent it doing this. If you de-install and then install UpdraftPlus, then it’ll still be 1.9.5 – but should work (it fixed it for me on the site I reproduced it on).
This is an ugly solution, really – custom work-arounds for brokenness in other plugins are really inefficient ways of solving things…. Hence, I’ve opened a support request in Google Analyticator’s forum – hopefully they’ll fix it soon:
https://wordpress.org/support/topic/dont-unconditionally-load-old-google-sdk
Best wishes,
David”Thanks! It’s working great now!
In case more info helps, I just tried to scan on another site – one that I haven’t done anything to yet today – and got the same error. Both sites were updated overnight to WP 3.8.2. This 2nd site is still running Wordfence 5.0.1. (I’d updated the 1st one to Wordfence 5.0.2.)
An auto scan on this 2nd site completed successfully at 3:34 am EDT.
These 2 sites are with separate providers. 1st at 1and1; 2nd at goDaddy.Here’s the response I got from 1and1.
Thank you for contacting us.
Due to resource limits on our Shared Hosting machines, it is not possible to allocate more memory to PHP than the maximum for your package. Using a php.ini file or the memory_limit directive to increase memory for PHP may result in the phpinfo() output reflecting the change however the server will not allocate more memory than the limit imposed by 1&1.
Older packages were limited to a maximum of 30MB for PHP memory regardless of package. Starting with the Dual Hosting packages, the limits have increased. You can view the PHP Memory Limit for each Dual Hosting package on our order site.
So far, I’ve been unable to find a good comparison of the differences between our current business package and any dual hosting packages they offer. (We currently have up to 3 domains, unlimited subdomains, unlimited mailboxes, unlimited webspace, unlimited traffic, unlimited MySQL databases, 10000 FTP accounts, SSL, 1 SSH account.) I’m working with a small new blog now, but was hoping to rewrite our main site in WordPress. Obviously, 30MB for PHP memory is not going to suffice.
Thanks camu. That’s what I’m thinking – so must wait for 1and1 to respond. And thanks for your WP Slimstat plugin! The stats are just what I was looking for.