[SudarKeymaster]

Try to delete posts in batches by selecting the “Only delete the first x post” checkbox and choose a very small number like 50 or 100. This will let us know whether there are any other issues.

Once the addon is able to delete this small number of post, you can increase the number upto the point where it runs out of memory again.

[SudarKeymaster]

Find out how much memory is allocated to PHP and WordPress. You can find this by accessing the system information from Bulk WP -> System Info. In particular you have to look under PHP Memory Limit and WordPress Memory Limit.

If WordPress Memory Limit is less than PHP Memory Limit then you can increase it by adding the following line in your wp-config.php file and replace 256M with the value that is there in PHP Memory Limit

define( 'WP_MAX_MEMORY_LIMIT', '256M' );

This is the first step. If this doesn’t solve it then you might have to find out how much memory is available in your server. Contact your web hosting company and they should be able to tell you how much memory is available for your server.

[SudarKeymaster]

Marking this thread as resolved. Feel free to post again if you still have any more questions.

[SudarKeymaster]

@Dennis,

I guess your WordPress installation is running out of memory and is not able to handle 410,000 posts. If you enable WP_DEBUG in your wp-config.php file you will be able to see it your php error log.

Even if you increase your memory you wouldn’t be able to delete 410,000 in one go. So I would suggest you to delete posts in batches. Almost all modules and addons support deleting in batches. You can use the “Only delete the first x post” checkbox.

[SudarKeymaster]

Disable the addon from the plugins page and it will not delete anymore.

This is really strange and should not happen at all. So kindly post a screenshot of the WP-Control page and also attach your system info. You can get system info from Bulk WP -> System Info.

[SudarKeymaster]

Marking this thread as resolved. Feel free to post again if you still have any more questions.

[SudarKeymaster]

Marking this thread as resolved. Feel free to post again if you still have any more questions.

[SudarKeymaster]

Is your website getting external traffic around the time you have scheduled the jobs?

WP_CRON uses pageviews as trigger for the cron job. It is enough even if you are getting 1 or 2 pageviews. But if there is no page view at all then it may not trigger the job.

[SudarKeymaster]

There seems to be some problem in your server. I suspect that your DB is having some issues.

When I try to view the last post page in WordPress admin console, even that is getting timed out. Check this link http://topic-hub.com/michaeljackson/wp-admin/edit.php?paged=24

I guess you might have to run mysql compact and optimize on your DB. If you have access to your mysql db then you can do it or otherwise contact your web hosting company.

[SudarKeymaster]

Okay let me have a look again.

[SudarKeymaster]

No. I just meant that you have to manually schedule on each blog and there is no way to automate it.

Once I add support for multisite, then you can just schedule the job once and execute it on all the blogs in the network.

[SudarKeymaster]

Right now it is not possible, but adding support for multisite is on my todo list since a couple of my other users have also requested it. I will let you know once I add support for multisite.

Meanwhile if you have any more feature requests or sugggestions then kindly post them in the feature request forum http://bulkwp.com/support/forum/feature-requests/ and I will update the posts once they are implemented.

[SudarKeymaster]

@Alvin,

Deleting 100 posts takes about a 40-60 seconds and scheduling things every minute will still make the server run out of RAM.

Can you kindly schedule jobs with interval of 10 minutes each and restrict the number to 100?

[SudarKeymaster]

Cool, try it out and let me know if you face any issues.

[SudarKeymaster]

Thanks for giving me access to your site. My suspicion is correct. Your server is running out of memory when trying to delete 400 posts at a time.

I tried varying this number and your server is able to delete around 150 posts at a time without any issues. Anything above that it is running out of memory. (I have restored all the posts that I deleted)

So to be safe you can try to schedule deletion of 100 posts at a time and then run the scheduler 5-6 times a day instead of just twice.

You can delete the old scheduled job from Bulk Delete -> schedules and the schedule a new one by limiting the number of posts to around 100.

Try it out and let me know if you continue to face any issues.

[Author]

Posts