[SudarKeymaster]

Hello Dallas,

Please give me the list of options that you choose while deleting the contact messages.

[SudarKeymaster]

Hello Scott,

Apologies for the delay. I was out for the weekend and was not able to get back to you earlier.

When a new user is created through WordPress (instead of directly inserting them through SQL), it creates a row in wp_users table and also a couple of rows in wp_user_meta table. In addition to it there are also other changes that are made.

My plugin uses WordPress functions to delete these users so that in addition to deleting the users from the wp_users table it removes these additional data and also safely removes allocation from posts if the users who are getting deleted have any posts associated in their name or have any additional meta data.

If you delete the users directly from wp_table using PhpMyAdmin, then these additional data are not cleaned up properly. That is the main use of my plugin.

In your case it looks like the users were directly inserted through SQL injection. When you initially deleted the users through my plugin, it removed all the additional meta data and when they got inserted again, the meta data is not mapped properly. That is the reason why my plugin is not able to display them properly since their additional data is broken. Honestly at this point my plugin (or built-in WordPress functions) are not useful to you.

Since the users are not getting created again when you directly delete them through SQL in PhpMyAdmin, I am suspecting that your vulnerability is fixed.

To make it easier for you to delete the users from PhpMyAdmin, you can use a SQL statement. Find out the ids of the users whom you want to keep and then use a SQL statement like Delete from wp_users where ID not in ( ids of users seperated by comma ).

But be careful when you use this query since if you don’t mention the user id then it will be deleted. It would be better to take a DB backup before you make this change.

[SudarKeymaster]

Hello Scott,

Looks like the problem is much deeper and there is a very high possibility that either your server is compromised or the hackers have access to a vulnerable script in your server.

They are basically re-creating these users using either vulnerable script or a backdoor in your server after Bulk Delete has deleted them. Also these users are getting directly inserted into the DB and that is the reason they have the user role set as ‘none’.

Even if you delete them directly from the DB, these users would get created again.

You need to solve it in two steps.

1) Find out which backdoor or vulnerability that hackers are using and the fix/block it.
2) Once that is done, delete the spam users from the DB directly.

Also make sure you backup everything. Since the attackers have access to your DB, it may be very easy for them to delete everything that is present in your DB.

[SudarKeymaster]

Hello Scott,

Please answer the following questions, so that we can debug this issue further.

• How were the users created initially? Were they directly inserted into DB?
• Is your site a multisite?

Also can you please post the screenshot of your users page with the ‘none’ user role selected. Thanks.

[SudarKeymaster]

Hello Axel,

Apologies for the delay in getting back to you. We had a major cyclone in our city and I have difficulty getting good internet connection for the past couple of days.

Looks like you have only installed the base plugin and have not installed the add-on.

In the receipt email (which I have resent again), you will find a link to download the add-on. Instructions to install the add-on can be found at http://bulkwp.com/docs/installing-addon/

Please follow the instructions to install the add-on and once the add-on is installed and activated, you should be able to find the field where you can enter the license key.

[SudarKeymaster]

Helo Lala,

Right now it is not possible to schedule two fields simultaneously.

You can create two seperate cron jobs though, one for each field.

[SudarKeymaster]

Hello John,

You can schedule the deletion by going to Bulk WP -> Bulk Delete Posts page and then to the “Bulk Delete Posts by Duplicate Title” module.

[SudarKeymaster]

Hello Jordi,

Just got the confirmation from the accounts team that paypal resolved the issues and we were able to successfully do the refund.

The balance should already reflect in your paypal statement.

Kindly acknowledge the refund.

[SudarKeymaster]

Hello Jordi,

We tried making a full refund to your paypal account and it was rejected by paypal.

Does paypal allow refunds in your country?

[SudarKeymaster]

Hello Jordi,

Apologies for the issue that you faced.

This add-on deletes all images that are not attached to any post. If you are directly using the image url then they may get deleted.

Please give me your order number and then we will process a full refund.

[SudarKeymaster]

Glad to know that you like our support.

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

[SudarKeymaster]

We have replaced the add-on in your order.

Feel free to reach to us again if you need anything else to be done regarding this order.

[SudarKeymaster]

I want to make it clear I used another free product and deleted more than 130 000 users in a few minutes with minimal effort. I didn’t have to restart a complicated set up procedure time and time again as with your plug-in. So don’t give me the lacking resources part thank you.

The only way this could be achieved by this other plugin is by directly deleting the user rows from the user table using a custom SQL query without calling WordPress built-in function. This may be fine for quickly deleting data from the db, but this is going to leave lot of residual data in the db. For example user will have user meta in user meta table, roles, user options, transients, cache etc. Also if the user has some posts associated with them, then those posts will become orphaned in the db. My plugin calls WordPress built-in functions to delete users (or posts) and they remove all these additional information when you delete a user (or post). But these additional steps need additional server resources.

I don’t have time to look trough 10+ plug-ins and then get into each and every little difference and detail of variations of one like yours. Please guide potential customers better and make these things MORE CLEAR. OK?

Thanks for this honest feedback. I agree that the website and the add-on checkout process is quite complex right now. My plugin (and add-ons) provide very granular control and this has increased the complexity. I am currently working on making the website and the entire checkout process much simpler for users by introducing bundles and buy-all options etc and this feedback was very useful.

[SudarKeymaster]

Well the reason this plugin is called ‘Bulk Delete’ is because this plugin allows you to delete posts/pages/uses/post meta etc in “BULK”. This is what the free plugin does.

If your server is able to handle the load then you don’t have to buy the add-ons at all. Even if you have thousands or millions of posts, the free plugin itself is perfectly capable of deleting all of them in a single go. The only limitation is your server’s resources. There is nothing in the plugin code that prevents the number of posts or users that can be deleted.

You buy the pro add-ons only when your server is not able to delete all of them in one go because of resource constraints and you want to delete them in batches by scheduling them.

Hope this clarifies the reason why I am calling it ‘Bulk’. Let me know if you still have any other questions.

[SudarKeymaster]

Hello Cheri,

Glad to know that the issue is resolved.

Do feel free to ping us again if you face any issue again.

[Author]

Posts