Jump to:
| Project: | Taxonomy Access Control |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I am having a problem that seems to have occurred before for others ... none of the posts I read seem to describe a solution except upgrading to TAC 5.x-2.x dev
I have installed and successfully used TAC for some months. Suddenly getting errors.
Error occurs when attempting to edit any of the role permissions for categories.
On clicking any edit link on the admin/user/taxonomy_access page
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 77 bytes) in /home/groupsal/public_html/includes/form.inc on line 853
Questions:
1) What information about the configuration or database would be useful to help diagnose?
2) Is the 5.x-2.x dev version actually ready for use on a production site? I notice that a bit over 200 sites seem to use it... but don't know if they are production sites...
3) other ideas??
Thanks for this great module and (in advance) for any help.
Comments
#1
Please, upgrade to TAC 5.x-2.x dev. (It needs less memory).
OR increase 'memory_limit' with php ini_set() e.g in the settings file of drupal.
#2
Thanks for responding so quickly
I am already using quite a bit of memory and the module was working successfully for quite a while.
My settings file has the following line setting memory.
ini_set('memory_limit', '64M');
I still have a question above ... the TAC 5.x-1.1 version is the one recommended for D5.
Is the TAC 5.x-2.x dev version ready for use on a production site?
Has it been used successfully on other production sites? Many?
I hope that my questions don't come off as critical. Our drupal site has a standing policy of not using dev versions of modules. Dev versions are usually supposed to be snapshots of partially tested works in progress.
What is TAC's policy/approach to development and the status of the dev version?
Thanks
#3
The development snapshots are generally pretty stable. Particularly with the 5.x branch, I don't intend to make any more changes unless there is a major bug.
#4
Thankyou.
Given that its pretty stable and you don't expect more changes, is there a reason that the current dev snapshot is not released as a new 5.x-2.0 version and recommended for use with D5?
#5
I think there were still some outstanding issues with the 5.x-2.x branch. With Drupal 7 around the corner, there probably won't be another 5.x release. FWIW, I am using 5.x-2.x-dev on a production site.