Hi,
I installed this modules this morning, for Drupal 5.1, using TAC module version 5.x-1.1. After enabling the module, I saw a memory size error message, but the module was enabled. I get error messages when I try to change permissions, so I tried disabling the module and get the following error message:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 20594 bytes) in /home/speclaw2/public_html/MYSITE/includes/database.mysql.inc on line 188

I haven't seen this elsewhere. At the moment, I just want to uninstall the module. How can I do this without messing up my site?

khorby

Comments

edrex’s picture

edrex commented
Status: Active » Closed (fixed)

you could
- delete the module from the filesystem
- delete the row for the module from the 'system' table using phpmyadmin or similar

khorby’s picture

khorby commented

Thanks, I deleted the module and restored my database from a backup.

judib99’s picture

judib99 commented

When we bring up the Taxonomy Access Permissions grid and make changes we get the exact same error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 21514 bytes) in /home/cmtrav/public_HTML/includes/database.mysql.Inc on line 183

At this point there are two things to note:

1) When looking back at the grid the changes ARE saved
2) ALL of the permissions for the entire site are reset at this point (very very bad, no one can see anything until we go back to every image, every forum post, every page and resave them)

We sent the error to our host and they maxed out our memory limit at 48M which, according to the error above SHOULD be enough, however we are still getting the error and the entire site is still getting reset everytime we make a change to the grid.

Please please help asap, we were sent to launch nationally next week and are frozen until we fix this error.

Thanks!
Judi

edrex’s picture

edrex commented

use 2.x dev, http://drupal.org/node/153216
you might get mem errors still until you blast the old rules for each role.

hope this helps
- eric

jsethi’s picture

jsethi commented
Status: Closed (fixed) » Postponed (maintainer needs more info)

Hi,

I am getting a fatal error: allowed memory size problem too.

It occurs when I try to go to the TAC admin area.

Please advise how to resolve this issue.

edrex’s picture

edrex commented

Please read #4.

2.x-dev needs testing! Put it through the paces and report your experiences. In particular, the admin UI needs some work, please try it out and make suggestions.

klance’s picture

klance commented

I posted a patch here that I'd like someone to try on a test site (not production):

http://drupal.org/node/167977#comment-637110

klance’s picture

klance commented

A couple of related references:

Node_access_rebuild needs tons of memory
http://drupal.org/node/108752

memory exhausted (50M) when trying to set access control
http://drupal.org/node/143919

edrex’s picture

edrex commented
Status: Postponed (maintainer needs more info) » Fixed

Thanks for the research klance. I don't think this issue is the same as http://drupal.org/node/167977 (this issue is resolved by 2.x branch).

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

vtsaran’s picture

vtsaran commented
Project: Taxonomy Access Control » Project
Version: 5.x-1.1 » 5.x-1.x-dev
Category: support » bug
Status: Closed (fixed) » Active

I see exact same error with both Project and Project_issue modules in Drupal 5.3.
There is more than enough memory.
Any ideas?

dww’s picture

dww
we/he/they
commented
Project: Project » Taxonomy Access Control
Version: 5.x-1.x-dev » 5.x-1.1
Category: bug » support
Status: Active » Closed (fixed)

a) Please don't re-open old, closed issues about other modules if you think you have a problem with project*. This is a completely unrelated support request, so there's no sense bothering all the people who participated in this thread so far about your new issue. Unless there's already an issue about this in the project* issue queues, you should just submit a new support request there.

b) Drupal 5.3 is known to be insecure. What are you doing still running that version? Don't answer here, it's meant for you to ponder, not for me to know. ;)