As soon as I enable acidfree I get access denied problems on a lot of the admin pages. And I am the "superuser". I have all checkboxes under rights checked. As soon as I disable acidfree I get my rights back again.
I installed filemanager an put my private map under Drupal.
I installed acidfree.
I enabled filemanager and acidfree. Problem occurred.
Comments
Comment #1
vhmauery commentedI have never seen this before. It is almost certain that some other module is interacting with acidfree. Can you try turning off ALL of your modules (besides the drupal required ones) and trying again?
Take this divide and conquor approach. after each step, check for the access denied problem.
1. turn off all the modules
2. turn on acidfree
3. turn on half the remaining modules
4. mark on a piece of paper which modules were turned on in which iteration
5. repeat step 3 until it breaks
6. go to step 1 and start again, but this time, the 'remaining modules' means the modules that don't play well with Acidfree.
You should be able to narrow down the problem very quickly. When you have a list of one or two modules that doesn't play well with Acidfree, let me know and I will try to recreate it myself to investigate the problem.
Comment #2
AstaC commentedWell I didn't do exactly as you asked but I did turn off everything, turned on acidfree and then enabled one module after another. And found out that if I have acidfree enabled at the same time as I have trip_search module enabled I get the access denied problem.
Comment #3
AstaC commentedI however cannot use it since I get another problem.
Fatal error: Call to undefined function: valid_input_data() in /home/www/mysite.org/Drupal/modules/css/css.module on line 85
Comment #4
AstaC commentedForget the last problem. That was another module
Comment #5
vhmauery commentedWell, as far as I can tell, there are several weird things going on here. The menu system doesn't like to be queried in the process of being built, but trip_search is the first one to ever cause a complaint. I committed a workaround for this problem, though I don't think it is the real solution. Either way, your bug is fixed in CVS and waiting to be repackaged.
Comment #6
vhmauery commented