Closed (fixed)
Project:
Taxonomy Access Control
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Aug 2008 at 04:15 UTC
Updated:
14 Jul 2012 at 19:20 UTC
I tried using Secure site to limit access to one directory of my site. After deciding to turn off the module and remove it, the pages originally blocked, plus newly created pages, are unavailable to anonymous visitors. They get an access denied message.
I am willing to make changes to the db to remove any remnants of the module. Can you describe an approach to ensuring that it is completely uninstalled?
The site is in development and has very few users at this time.
I used Secure Site 5.x-1.2 and Drupal 5.10
Comments
Comment #1
junyor commentedHave you tried clearing your site's cache? If you have the devel module installed, I believe you can use it to clear your cache. If not, empty the cache* tables in your database. Also, make sure the anonymous role has the "access content" permission (assuming you want anonymous users to access your site, which seems to be the case).
Comment #2
urbanrob commentedClearing the cache with devel did not change the issue. Anonymous role can access content and can still access most content on the site. It cannot access newly added content.
Comment #3
junyor commentedSecure Site couldn't be causing that. Did you also test any node access control modules like taxonomy access, tac lite, etc.? One of those is the most likely culprit.
Comment #4
urbanrob commentedYes, I tried Taxonomy Access. It was previously uninstalled and deleted. (Using the devel variable editor I do see that a list of securesite_ variables are still available, even after emptying the cache.)
I just deleted the taxonomy that had been associated with Taxonomy Access (the terms were not applied to any nodes) and cleared the cache again. No change.
Comment #5
junyor commentedThere's your problem. Taxonomy Access Control must have messed up the default access control for anonymous users. Try going to /admin/content/node-settings and rebuilding permissions.
In 5.x-1.2, Secure Site does not delete variables on uninstall. This functionality has been added to the next release.
Comment #6
urbanrob commentedThank you. "/admin/content/node-settings and rebuilding permissions" worked.
Comment #7
junyor commentedComment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.