Sharani

they just issued a wordfence plugin update earlier today – did you install that yet? maybe that will help?

I increased the memory to 300 and it finally ran. Now just to figure out what it means that bots are trying to log into the site almost once a minute from around the globe even though the scan didn’t show any problems.

Yesterday and today I am getting a similar issue that hangs up my scan – it says
[Dec 01 09:09:46] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 50703451 bytes) in /home/content/73/11014273/html/wp-includes/wp-db.php on line 1301

any thoughts on how to fix this?

thanks!

Our site runs on a Windows Server and gave this error message when I had 2 plugins that wanted upgrading today after upgrading to WordPress 3.5 a couple of days ago. To get the 2 plugins to upgrade successfully, I first tried putting this code mentioned in this thread and it did not work.
define(‘WP_TEMP_DIR’,’/path/to/a/temp/dir’);

Then I tried this code mentioned in this thread and it did work.
define( ‘WP_TEMP_DIR’ , ABSPATH . ‘wp-content/’ );

I installed TAC and it didn’t find any malicious code. Today I activated Twenty-Eleven and it reverted to default from this theme as well. It only seems to be happy if I keep the theme from before the upgrade activated – an old version of K2 which doesn’t interface completely in the dashboard since the 3.4 upgrade – nothing happens when clicking on widgets to edit, nothing happens when clicking on upload media in add new post. Until I can find someone to perhaps hire to fix this, I will just add and edit content in another theme and switch back to K2 for the site’s display.

I was not familiar with Base64, etc. Right now my host is taking a look and seeing if she can find something with the files, etc. Thank-you for posting and I will check back in here again after we do more investigating.

I wonder if I should try 24 hours with a different theme than my one before the upgrade to 3.4 (K2) and my one since the upgrade (Weaver II and Weaver).

And I don’t know if this could be related to the theme reverting to the default or not. Just playing a guessing game at the moment.

Not that I am aware of. I have been searching this setting on the Web and it appears it might be a default setting of newer versions of WordPress. But I am really not an expert at the back end of these things.

Do I need to change the settings below? The theme developer for Weaver recommended I turn off Quick Cache and the Weaver theme lasted the day yesterday without reverting. When I came in at noon today, it was back to the default. Our host wrote:
“I noticed the wp-config.php file was updated at 9:25 today. This is in the config: define(‘ENABLE_CACHE’, TRUE);
The wp-content/cache folder also has a timestamp of today, at the same time.”
Should we change this setting to something else?

thanks I will try that.

I had to switch to a different theme to get all of the above working again. Now I am back to the drawing board to try understand how to get stuff to lay out the way I had it before. Oh well…

ditto for waiting to upgrade (although I am running 3.1 with the canonical redirect plugin)

After the last upgrade fiasco with our Windows Server, I am waiting to upgrade. Sounds like a good thing if I understand correctly and both 4rapiddev and antioch got the same error with 3.1.1. Wish they would spell out more clearly whether Windows users are supposed to still use the Canonical Redirect Plugin or not and if not, why did two Windows Server users find differently…