Hi,

I uploaded new Acidfree module and applied patch the filemanager-private.patch to the latest filemanager.module.
I set all settings in admin (both Acidfree and Filemanager).

Then the front_page module access is denied for evereybody (admin user too)
And sometimes the admin pages after the setting also write this: Access denied. But the settings were saved.
I don't understand and can do anything...

I have to disable the acidfree module and everything is work.
But I'd like to use acidfree module.

Pls help me

Comments

vhmauery’s picture

vhmauery commented

I tried to get front_page working and I couldn't get it to do anything, let alone give me an access denied message. I am not sure if I can help you out here. Do you have any node_access modules enabled, like organic groups or node privacy by role? I can't see why acidfree would cause problems with access denied unless it is the interaction with the node_access modules.

dublin drupaller’s picture

dublin drupaller commented

Hi arnoldg,

I maintain the front_page.module and just tried the Drupal 4.6 version. Works perfectly out of the box.

Would like to help you sort your problem though and see if there is some sort of conflict...quick questions:

(a) was the front_page.module working before you installad acidfree and patched the filemanager-private.patch ?

(b) did it stop working after you installed acidfree...? or was it after you patched the filemanager-private patch?

Dub

Anonymous’s picture

Anonymous (not verified) commented

Hello,

- No, I don't use some kind of node_access modules.

- Answer of (a): Yes, before I installed acidfree the front_page m was working
well. You have to know that my front_page module contains this: 

  include("myfolder/myfile.php");

So this module uses a PHP file from
a folder. Does cause the problem? Permission of file/folder? But I tried this,
I set the folder and file to 777. Sorry without success. And I tried that I
copied all codes from this PHP file to front_page m (settings/front_page), without
result. And I have got some blocks that get content from external PHP file.
Is this in connection with my error?

- Answer of (b): It stop after I installed acidfree. The order: 1: front_page
works, 2: I installed filemanager (front_page works) 3: I installed and patched
the filemanager-private patch. (front_page don't works) 4: I disabled acidfree
m and there isn't error. Now filemanager m is active (with filemanager-private
patch) and everything is ok.

- And it is stranger: When I set something in admin/settings or admin/settings/acidfree
the result is same.

dublin drupaller’s picture

dublin drupaller commented

Using a php instruction to include a file with the front_page.module should work without any difficulty as long as:

(a) the path is correct
(b) the file & folder permissions are correct..755 is the common setting.
(c) the PHP filter is selected

It's not unlike including an IMAGE...fairly simple stuff.

I was guessing that the filemanager private thing was overriding the folder & file permissions of sub-folders, and thus, front_page.module was not able to "include" it. From what you say, it's not that and something to do with acidfree.module.

So, based on your comment..it seems that the Acidfree.module is causing problems. I'm not familiar with that module, hopefully the module maintainer can shed some light on it.

Sorry I can't be of more help.

by the way, I didn't understand your final point, i.e.

And it is stranger: When I set something in admin/settings or admin/settings/acidfree
the result is same.

What do you mean?

Dub

vhmauery’s picture

vhmauery commented

I cannot reproduce this bug. I tried on my main devel setup site and another sandbox site. I tested some complex code that makes calls into the acidfree API. I tested some plain HTML. I tested code that included other files. It all worked like a charm.

Can you make it show just some sinple HTML for your front page?

dublin drupaller’s picture

dublin drupaller commented
Status: Active » Closed (won't fix)

just to add to this....I have looked at both the acidfree.module and front_page.module and cannot see anything that would cause a conflict.

My only guess is that it might have something to do with the PATHS to the included file you are trying to pull into the front page. i haven't looked at the filemaneger patch thing you mentioned..but, I think you can almost certainly scratch acidfree.module off your list as the cause of the problems you're having.

Marked this thread to won't fix to free it up as an issue. It's nothing to do with acidfree.module as far as I can see.
Dub

nigma3d’s picture

nigma3d commented
Status: Closed (won't fix) » Active

This issue appeared on the message boards and I enabled the acidfree module on my installation and got the same access denied issue. Check out http://drupal.org/node/41311. I have no idea what is causing the issue but I am pretty sure it has nothing to do with the front_page module but some other culprit.

gosherm’s picture

gosherm commented

Well, after disabling all other modules and then reenabling them one-by-one, it looks like it may be some sort of conflict with the trip_search module. Does anyone else having the problem have that enabled? Anyway, in the interm, I'm just going to disable the trip_search module and call it good.

nigma3d’s picture

nigma3d commented

Sure enough, it is the trip_search module that is causing the interaction issue. I too want acidfree more than tripsearch, so I disabled tripsearch -- no more access denied problems for me. Anyone know what the problem could be with that interaction?

vhmauery’s picture

vhmauery commented
Status: Active » Closed (fixed)