Posted by kpaul on November 5, 2007 at 8:04pm
7 followers
Jump to:
| Project: | Content Access |
| Version: | 5.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I tried to uninstall the content_access module last night by turning it off on the modules screen. I realized this morning that all anonymous users couldn't get to content.
Looking at the database, the node_access table had stopped inputting nids into the table about a month ago?
In any case, I turned the module back on, but still couldn't access content anonymously. So I went to content types and hit the submit button. It seemed to update that table with new nids.
My question is, though, how to get rid of content_access module without messing anything up. An easy way I'm overlooking?
Thanks!
kpaul
Comments
#1
just deactivating should do it.
#2
Automatically closed -- issue fixed for two weeks with no activity.
#3
Had the same problem for newly created pages, looked through the module's source and found the node_access_rebuild() function. Ran it once as admin in an existing page and it fixed the problem for good. It should be added to the uninstall routine. Hope it helps.
#4
Closing it as 5.x is not supported anymore. And in newer Drupal versions, you'll get a warning to rebuild the permissions.
#5
what? no.
whats the process to remove this module? had it working on a 5.x site, upgraded to 6.x now can't access anything nor can I disabled this.
#6
Is it still valid on D6? if so reopen this issue and change the version to 6.x, since 5.x is not supported anymore.
#7
Is it still valid on D6? if so reopen this issue and change the version to 6.x, since 5.x is not supported anymore.
#8
yes this is still vaild on 6.x. You want people to upgrade a site busted due to this module and hope that that corrects problems?
#9
As far as I understand, 5.x is no longer supported. Updating title to make it easier for people to find, just in case.
@captaingeek - if you have ideas how to fix it then that's great. Otherwise it seems apparent that this issue doesn't affect very many people so the best status is closed.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.