On 10/8/07, Vasileios Lourdas lourdas_v@yahoo.gr wrote:
On Monday 08 October 2007 08:25:16 Cog Rusty wrote:
Something else you can check is the 'node_access' table. Take one specific node which displays the problem, and get all the rows with that nid. Then check the 'realm' column to find out which module grants "view" access to whom. TACs 'realm' is "term_access" and its 'gid' column uses role IDs. Other modules have other realms (for example "og"), and their 'gid' may mean something else (for example an og group).
All tables rows have these data (x is the node id): x | 1 | 0 | all | 1 | 0 | 0 | Hm...
The columns should be only 6. But it is strange. If there is no other realm except "all" then TAC doesn't do anything at all...
I would disable and then uninstall TAC. Then I would empty the node_access table and I would insert only a single row with nid=0, like 'system.install' does in a fresh installation.
db_query("INSERT INTO {node_access} VALUES (0, 0, 'all', 1, 0, 0)");
Then I would start over, reinstalling TAC and trying again.
I am not sure what is going on with TAC these days. Rel.1.1 is 4 months old. I checked the issues pages and there was one issue a couple of months ago (http://drupal.org/node/168748) where keve replied "Module has been totally rewritten, please try to use 5.x-2.x-dev version."
This uncertainty is a bit sad, because TAC has been a pioneer module. It made things possible which couldn't be done until much later by specialized modules.
-- # Vasileios Lourdas, # Informatics Engineer, Thessaloniki (Greece)
# http://www.lourdas.name
[ Drupal support list | http://lists.drupal.org/ ]