hummelmose

Yes, which is why you only let it run long enough to clear out the excessive entries, and then delete the file. You don’t *leave it there*, you run it only once and then remove it.

Well. Why put it in the mu-plugins then. Wouldn’t it have been smarter to just call the fix.php from another folder once ?

Is there an easy way to delete all the jobs this fix created ?

I’m running Nginx + CloudFlare + Varnish

I get no white screen after implementing the script

I can validate that the fix above solves the problem – Please be aware that the “FIX.PHP” in mu-plugins gave me a astronomic load for aprox. 4 minutes. I have 4 cores, and I was at 17 – It fell to below 1 after 4 minutes. and now the CPU load is back to prior 4.3 levels.

@jp

Thanks a mill. That did the trick.

/Jens

But why?

Why create a new thread – Since this here was allready 18 posts long?

Same here on several sites on different themes!

I was a bad wp-all-import 4.0.9 plugin.

Disabled all plugins, and found the bad guy.

Solved it myself On the new server <? was not valid, it needed <?php

sorry for my stupidness.