the installation failed with a php memory error, but the module was nevertheless enabled. right off the bat it caused a handful of seemingly random access problems. content of various types is invisible to various roles. this was before i tried fixing it through the module's ui. at this point i am unable to restore drupal to its previous state.

Comments

johnalbin’s picture

Category: bug » support
fago’s picture

Status: Active » Fixed

hm, I think you got hit by the issue mentioned in the README of the latest dev snapshot:

Enabling this module on big sites
----------------------------------
Drupal 5.1 uses a lot of memory, as soon as you enable this, or any other node access module on a
site with a lot of existing nodes, which means thousands of nodes. This is problem of drupal itself,
and is fixed in the latest development snapshot of 5.x (http://drupal.org/node/108752).
So if you are experiencing memory issues or you are planning to enable this on such a big site update
to the latest development snapshot of drupal 5.x before.
You can find it here: http://drupal.org/project/drupal

If drupal 5.2 is already released at the time you read that, it will also contain the fix.

To clean your install again, try updating to latest drupal snapshot, and reinstall the module.
I've just created a new release of content access (1.1), so that the README of the latest release is also updated.

Anonymous’s picture

Status: Fixed » Closed (fixed)
FableForge’s picture

I got hit by this too.

I cant uninstall it, (trying to gives me a "Zero Sized Reply" error).

So I tried to upgrade from 5.1 to 5.9. I followed the recipe as best I could, but now all pages give me a "Zero Sized Reply" error. So I tried installing 5.1 (had the backup) and I still got the same error. I'm not sure what to try next. Any help is appreciated.

FableForge’s picture

After a lot of pain, I was able to get my site to 5.9. Still, this mod plainly doesn't work, the checkboxes to control access, edit and delete under Content Types have no effect whatsoever.

johnalbin’s picture

Hi Marco,

The module definitely works because I’m using it fine on my site.

Since this issue was about a core bug in Drupal 5.1 and its already fixed and closed, I suggest opening up a new support request to ask for help on your issue.