Download & Extend
Taxonomy Access Control » Issues

I am now unable to see certain other stories that I have posted since I turned this module on.

Posted by Andrew44 on September 12, 2009 at 12:29am
Project:Taxonomy Access Control
Version:6.x-1.0
Component:User interface
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

Hi,

Someone put me on to use taxonomy access module to control which roles could access certain nodes.

This works great. However I am now unable to see certain other stories that I have posted since I turned this module on.

The content type I am having trouble with is storys. Taxonomy is set not to use this type so I don't see why taxonomy access should be stopping my viewing of those if I am running as an anonymous user.

Anyone have experience with this kind of issue?

Thanks in advance,

Login or register to post comments

Comments

#1

Posted by mbuhmann on November 17, 2009 at 7:30pm

I am having a similar issue. I set up TAC and created permissions for an anomymous issue to access story content. No matter what permissions I gave the anonymous user new content could not be viewed. When I turned off the TAC module then the content could be viewed.

#2

Posted by xjm on February 21, 2010 at 2:47am
Status:active» postponed (maintainer needs more info)

Try these steps:

  1. Disable TAC at admin/build/modules
  2. Uninstall TAC at admin/build/modules/uninstall
  3. Re-enable TAC
  4. Rebuild your content access permissions at admin/content/node-settings
  5. On the anonymous user TAC config page at admin/user/taxonomy_access/edit/1, make sure the global default view is set to A. You should probably also check the list box.

Does this resolve the issue? If it doesn't, I'd suggest disabling and uninstalling any other access control modules and seeing what effect that has. If you don't have any other access control modules, try using the devel module and looking at its node access features to troubleshoot the problem further using the devel node access debug mode setting. Also check what it says on the devel node_access summary page.

As a last resort, you could run the query truncate node_access; and then rebuild your content access permissions again. (Not on a production site!)

#3

Posted by xjm on April 1, 2010 at 12:01pm
Status:postponed (maintainer needs more info)» closed (fixed)

Closing issue since there's been no followup. I realize the reply was several months after the original post, of course; if the troubleshooting in #2 does not resolve the issue, please provide more information and set the status back to active.

nobody click here