access denied for users for any taxomy

I had a similar problem, though with different symptoms. In my case, all new content (new pages, blogs, stories, etc.) would generate an "access denied" error for all users, even though they had the "access content" permission. The problem seems to be that Drupal looks at the node_access table to know whether it should even be using it at all to restrict access. By default, Drupal does not use the node_access table for anything, and it has a single blank row to indicate this. Tac_lite puts a bunch of entries in this table, at which point Drupal then explicitly expects to find entries for ALL nodes in that table. If the entry is not found, it will deny access to that content by default.

This works fine when tac_lite is installed because it manages the entries in this table, but once tac_lite is removed, entries no longer get created. Old content still works because the node_access entries were already created by tac_lite, but new content fails because nothing is adding node_access entries for those new nodes. The solution is to just delete everything from your node_access table and add in the default marker row that Drupal expects. This is trivial if you have access to your database in any form; just run this:

delete from node_access;
insert into node_access (nid, gid, realm, grant_view, grant_update, grant_delete) VALUES(0, 0, 'all', 1, 0, 0);

This will reset Drupal's permission handling to its original default state. DON'T do this if you have other modules besides tac_lite that are actively using node_access to control access permissions to anything.

Tac_lite should potentially have an uninstall handler that does this for you, though I can see how this would be problematic since tac_lite has no way of knowing if other modules are still actively using the node_access table, in which case zeroing it out would be bad. Some documentation about this at least would be nice (or maybe it already is documented and I missed it, in which case some additional keywords of common symptoms added to those docs would be nice :).

These seem like totally different issues.

To nezroy: if you have a problem like this, go to ?q=admin/content/node-settings and hit the "rebuild permissions" button. tac_lite is working within the framework provided by core drupal. If you want to change the way that works, submit an issue to drupal core.

To dr. abody: You're saying that tac_lite is not even installed, so I fail to see how your issue is related to tac_lite. You'll have to provide more details.