spam users in wp_users after wpsc upgrade

@desktopmasters: It appears that once I’m at version 3.8.13.4, I no longer can downgrade to 3.8.12.1. I might have to completely reinstall the entire website, which will be a huge waste of my time precious time and resources.

WPSC is getting from bad to worse, and considering to migrate to WooCommerce.

I thought this had been resolved ?

We are having problems with running out of CPU capacity because of cron jobs running.

Looking at our database Database: marcshos_bonfiremain »Table: wp_users I see over 30’000 rows – this is despite only four users showing in the WP dashboard ????

Ours support has brought our attention to these cron jobs:
PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND
298993 300306 288063 288063 ? -1 RN 532 134:52 /usr/bin/php /home/marcshos/public_html/bonfire.co.uk/wp-cron.php
331635 335918 288063 288063 ? -1 RN 532 87:16 /usr/bin/php /home/marcshos/public_html/bonfire.co.uk/wp-cron.php
357681 366000 288063 288063 ? -1 RN 532 47:10 /usr/bin/php /home/marcshos/public_html/bonfire.co.uk/wp-cron.php
398611 398843 288063 288063 ? -1 RN 532 15:01 /usr/bin/php /home/marcshos/public_html/bonfire.co.uk/wp-cron.php

These are running despite following these guidlines https://support.krystal.co.uk/entries/23117312-wp-cron-php-consuming-too-much-memory-and-cpu
to try and control WP cron jobs and adding appropriate code “define(‘DISABLE_WP_CRON’, true);” to WP-config file.

Before WPEC made changes we had no problems now it looks as if the problem has been “glossed over” rather than sorted.

Anyone more technical got any ideas as to what problem is – and whether it is with site or update ?

i am seeing the details for 3.8.14 and it looks like they resolved this problem, can anyone verify this?

also, of anyone that can verify, can you also give warning if there are more bugs? bad ones… at least i know how to control the version im using now, all i need is to upgrade and get a bunch of new crap i have to figure out.

thanks for any feedback, opinions etc on 3.8.14

Hey Justin-
Can you give me an update? i see that 14.1 is available.
i really appreciated your input last time, maybe you can let me know if its time to pull the trigger finally!

Gaaah! I just upgraded to 3.8.14.1 and it made me update the database – And the 139,000+ users I had (9 of which were real) went from almost all being anonymous to almost all having no role so even the bulk erasers (which could only delete 1000 at a time anyway) couldn’t touch them … Which meant that I had to follow Pheriche’s advice and use SQL to fix it directly.

Since that was a few pages back, I’ll summarise:

# mysql –host=localhost –user=SECRETUSER –password=SECRETPASSWORD
Welcome to the MySQL monitor. Commands end with ; or \g.
mysql> use wpblogdb;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> DELETE FROM wp_users WHERE ID >10;
Query OK, 139201 rows affected (2.17 sec)

mysql> DELETE FROM wp_usermeta WHERE user_id NOT IN (SELECT ID FROM wp_users);
Query OK, 2259447 rows affected (1 min 5.54 sec)

mysql> select * from wp_users;
(just to check)
10 rows in set (0.00 sec)

mysql> exit;
Bye

… The id>10 was worked out by the fact I only had 9 legitimate users, I deleted the last spammer by hand – I was leaving a little safety gap because I am odd that way.

Thanks Pheriche… Grrrr to whoever caused this!

hi ocean dg-
i followed this problem for months, i even avoided upgrading for about 2 months while i watch this.

i had to daily-delete anon users 1-2 a day for those 2 months.

as of 14.1 (or 14.3 i think) the database structure was changed so that anon users were no longer used to store that info.

you can look and see (depending on what version you are using) here
http://a1decals.com/wp-admin/users.php?role=wpsc_anonymous

if you have no users you are fine, if you do, read up on doing a database backup from myphp/cpanel and upgrade to the newest wp ecommerce.

so to anyone late to the game, if you are using the newest wpec or at least newer than version 3.8.14.1/3 you should be fine and can disregard this post.