This is actually driving me crazy because we tested the migration on a backup of the website first, and that site does not have the problem.

Basically, when you're logged in things work fine, but if you're not logged in something like 99% of the site is access-denied, with no clear explanation of why.

  1. I've rebuilt permissions several times.
  2. Uninstalling TAC restores anonymous access but, obviously, also gives anonymous users access to areas of the site we don't want to give them access to.
  3. Reinstalling TAC reintroduces the problem.
  4. Looking at the issues for TAC I noticed similar complaints related to the PHP version. Both the test site (which works) and the production site (which is broken) are using PHP 5.2.17.

Question: When I re-installed TAC, it restored the old schemes. Is it possible to completely remove these schemes? Would it help?

Question: When I reinstalled TAC it "remembered" the previous schemes it had installed. Is it possible to uninstall the schemes completely? Would it help?

Comments

mwheinz’s picture

devel_node_access reports:

node	prio	status	realm	gid	view	update	delete	explained
532	– 	empty	tac_lite	4				
(Some of the table elements provide additional information if you hover your mouse over them.)
Webmaster has the administer nodes permission and thus full access to all nodes.
username	create	view	update	delete
Anonymous	NO: by the module	NO: node access	NO: node access	NO: node access
Webmaster	YES: administer nodes	YES: administer nodes	YES: administer nodes	YES: administer nodes
mwheinz’s picture

I was able to partially fix the problem, by manually clearing out the TAC scheme, uninstalling, rebuilding permissions, reinstalling, recreating the scheme and rebuilding permissions.

But now I have the reverse issue - users are getting "create" access to forums they don't have access to:

username create view update delete
Anonymous NO: no reason NO: node access NO: node access NO: node access
System Administrator YES: administer nodes YES: administer nodes YES: administer nodes YES: administer nodes
porkchop YES: by the module NO: node access NO: node access NO: node access

Dave Cohen’s picture

Looks like you have multiple modules affecting node_access, which can be hard to troubleshoot.

Try comparing devel_node_access data from both your broken server and your working backup. Are they identical?