bobbyh

Here’s the edited version of the main wpomatic.php file: https://pastebin.com/MQnjfW6k

The other files are the same.

@tevya, I am not the original developer. I just fixed a function in his code so the plugin works without pegging the CPU at 100% when there are lots of existing posts…

Anyway, I can verify the code works fine with 3.1, which is the WP version I am currently using on my wp-o-matic site.

@mv5869: Can you confirm that the new code works on your site(s)? ??

mv5869, here are a few other things you can do:

* Ironically, running the cron job more often can lower load spikes. However, if you do this, you need to stagger your campaigns so they’re not all running at the same time. Click into each campaign and click the “options” tab. Set the Frequency to a number such that all the campaigns aren’t running every time the cron runs. I set the Frequency to a number larger than the frequency of the cron job, so not all the campaigns are checked at the same time.

* If your server still has trouble with load, you can disable the cron job and run Campaigns manually one at a time by clicking Fetch for each Campaign. Make sure each Campaign finishes before running the next one. If your server is really weak, you might need to do this during off-peak traffic.

Good luck! Let me know if my code works for you! ??

My garbage collection was set high, that was definitely an issue. I lowered it, and that helped. But to avoid the problem in the future (as the site scales), I also switched to this variant of super cache that uses eaccelerator as a backend: https://murmatrons.armadillo.homeip.net/features/experimental-eaccelerator-wp-super-cache. donncha, it’d be awesome to integrate that into the plugin itself. ??

I don’t have a solution, but in case it’s helpful, that looks like the error for the wp-nonce function.