Answered Error - table class/name for class: modAccess

After getting some rest, I have some time to dedicate to Discuss right now, so I will try to get all errors defined at least, even if no easy fix exists.

I just got this error on Modx manager login, this should come just from straight logging in...but I couldn't reproduce it just now, it has happened several times a couple days ago, but at that time I think probably no one was messing with the forum...

[2015-02-17 01:13:58] (ERROR @ /index.php) Could not get table class for class: modAccess
[2015-02-17 01:13:58] (ERROR @ /index.php) Could not get table name for class: modAccess
[2015-02-17 01:13:58] (ERROR @ /index.php) Error 42000 executing statement:
Array
(
[0] => 42000
[1] => 1064
[2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AS `modAccess` WHERE `modAccess`.`principal` = 335' at line 1
)

Ok thanks for the background. In this case I don't think it was a delete user action, I was assigning a board mod which presumably needed to check user access.

So, no worries I guess. Thanks for the info.

I figured out what is going on here. Bots are registering and I think some safety in the system identifies them and tries to delete them. But then modAccess can't be gotten so the user isn't deleted. I can see a list of zombie users in my user list, all unconfirmed and inactive.

Quote from: gissirob at Feb 17, 2015, 10:09 AM

There is a known bug that generates this message any time a user is deleted. It is possible that this occurred for some other reason, but I would check there first. Supposedly it is harmless, but it would be nice if it was fixed (it's been around for a number of years).

And it's still there.

Quote from: BobRay at Jul 14, 2018, 10:52 PM

Quote from: gissirob at Feb 17, 2015, 10:09 AM

There is a known bug that generates this message any time a user is deleted. It is possible that this occurred for some other reason, but I would check there first. Supposedly it is harmless, but it would be nice if it was fixed (it's been around for a number of years).

And it's still there.

yep

By coincidence, it just hit me 5 minutes ago, triggered by an old version of SiteCheck, which was not deleting any users.

with me it seemed to be user permissions, it was the board mod change or assigning

For me it was I needed to set primary_group for modUser!

Quote from: mrhaw at Aug 25, 2018, 12:59 AM

For me it was I needed to set primary_group for modUser!

you're using Evo I guess? couldn't find that key in Revo