This request is related to this og issue (corrupted node preventing the og access control from working).

The legacy node feature of the devel modules is good. Here is what it says:

Legacy Nodes

You have 3 nodes in your node table which are not represented in your node_access table. If you have an access control module installed, these nodes may be hidden from all users. This could be caused by publishing nodes before enabling the access control module. If this is the case, manually updating each node should add it to the node_access table and fix the problem.

In my case, these 3 nodes were corrupted (i.e. the author was not deleted properly, see the link above) and they were actually represented in my node_access table, with the wrong access rules. It also says that manually updating each node should fix the problem, but in my case, I couldn't access them, even with the admin account. The only fix was to edit the db manually.
I suggest you add something like this to the legacy nodes explanation:
"This could also be due to corrupted nodes whose user may have been deleted incorrectly."

Comments

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Closed (works as designed)

too obscure. we can't give text on every possible thing that could be wrong on a person's system. thye could have deleted anything.