Users listed as member_id

Yes this is intended behavior. I should change the reports of whats been fixed, so instead of showing "guest" (as part of the confusion to why guest would show up), the member_id will display instead. you can remove these.

I'll add a task in 1.0.4 that will clean these up automagically.

@Michael Excellent!  Thanks for the support!

I've added in "Prune Non Members" in the acp for cjdml, when run a queue that will iterate over the cjdml table and try to load the members, if it can't (which indicates they no longer exist) it will remove them from cjdml and including any children accounts they might have attached to them. it processes 50 at a time, so it shouldn't be too taxing on your server, if it is, let me know and i'll bump the number down.

Hi @Michael. Thanks for creating this button. I've upgraded to the new version and clicked on the button. The problem is that it deleted ALL records (8000+)...

i don't see how it could've done that...i still have that database you sent i think, i can send it back to you. I'll do some additional test on it, but when i ran it on my test db last night, it only delete the records that a member wasn't there for.

Hi @Michael,

I've just logged in into my MySQL server and actually the table is still populated, and the number of records decreased to about 6,000, so about 2,000 records were deleted. However, in the ACP, nothing is shown, see screenshot.

I will send you the current table in private, meanwhile I am still trying to figure out what is going on.

sorry, i see in the code what happened. if you have a back up, you can restore from that? I'll get it fixed later tonight or tomorrow morning in 1.0.6.

Hi @Michael, I can restore the backup, but is the current database valid or the prune function actually deleted data it shouldn't? I ask you this because the backup may be a little bit outdated, and if the current data is still valid and this is only a PHP/front-end issue, we can leave it like that until you fix the plugin.

the data is useless, as it deleted the parents, so its okay to drop/truncate the table and restore from there. and the problem is in the php code, so don't run it again till 1.0.6

Restoring the backup in 3...2...1...

@Michael Working fine now with the 1.0.6 version. Many thanks for the support.