Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.OK, I have several Drupal sites running on one server which is running FreeBSD 4.10 stable, PHP 4.3.11 and MySQL 4.1.9.
On an existing 4.6.3 site (site 1), there are no problems of the kind I'm about to describe. This can be witnessed by visiting:
http://www.vcommunity.org.uk/system/files?file=pictures/picture-1.jpg
(apologies for the ugly mugshot - WHO is that guy!?!?!)
However, on a 4.7-beta-3 site (site 2) that I'm setting up, I have been receiving the following error:
Type - access denied
Location - /system/files?file=pictures/picture-1.jpg
Referrer - http://rutland.vcommunity.org.uk/user/1/edit
Message - system/files denied access.
Severity - warningVisiting a similar URL for that site produces this:
http://www.v-community.co.uk/system/files?file=pictures/picture-1.jpg
I have tried to troubleshoot the error to no effect and finally decided to try a clean install to see if there were any problems. This I did on a subdomain, http://rutland.vcommunity.org.uk (site 3). Visiting the respective same URL produces this:
http://rutland.vcommunity.org.uk/system/files?file=pictures/picture-1.jpg
Which looks fine. Except that in the log files, I have the same error as on site 2:
Type - access denied
Location - /system/files?file=pictures/picture-1.jpg
Referrer - http://rutland.vcommunity.org.uk/user/1/edit
Message - system/files denied access.
Severity - warningThe error always appears twice for every instance:
warning access denied 16 Jan 2006 - 1:57am system/files denied access.
warning access denied 16 Jan 2006 - 1:57am system/files denied access.And given that this is a clean install now and is running on a server which is known to work (site 1), I have to assume that there is a problem with beta-3.
Am I wrong? Can someone point me in the right direction if I am because I am completely flummoxed now.
Sorry if this isn't considered a bug report. I'll happily move it if so, but to me it seems the most logical place for it.
Regards
Patrick
Also, apologies for the many links shown here but a single screenshot will not make the problem clear.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | Image1.jpg | 159.46 KB | icenogle |
Comments
Comment #1
icenogle commentedI am having similar problems, under similar circumstances.
I am getting error messages in the log trying to display those images.
Here is the kind of thing I'm getting:
The second error message (which actually occurs first) is another piece of wierdness that may or may not relate to the other. I suspect it doesn't.
I have gotten some of the other error messages mentioned by the original submitter, but I have been messing with editing the text and the links and prevented some of the problems by modifying the url's on the images. (I suspect I shouldn't have to.)
I have been re-visiting this bug report to see what the response might be, and decided to confirm the bug, in case someone thought it was unique to the submitter.
Comment #2
icenogle commentedAs I now look at it, it does appear that the two error messages are related. drupal_access_denied() has been modified for 4.7 to unconditionally print(theme(page,...)), and it looks as though recursion is happening here. (If I click on the "view" link in the access denied error message, I get a recursive print of the page, apparently til the stack blows.)
So there's a problem with image access, and there's a problem with drupal_access_denied(), if I'm not mistaken.
I have attached a screenshot of the way this display looks.
I'll check to see if another bug needs to be filed on this.
Comment #3
icenogle commentedI have gotten rid of my problems (note: I'm not the original submitter) by carefully re-installing and re-patching image, img_assist, and tinyMCE.
I haven't tried to make uploads private again. I note in the settings help text that it isn't advised to switch back and forth, so I suppose they shall forever remain public, at this point.
I believe that if you do get a "denied access" message, you will get a cascading theme page, and that that probably is because of a bug in the re-implementation of the drupal access denied function.
Comment #4
Patrick Nelson commentedI too have gotten rid of the problems by doing a completely new install and not enabling upload module at all but allowing the upload of user pictures.
This therefore is definitely not fixed, but at least it means the problem is narrowed to uploading files, i.e., the upload module (IMO).
Comment #5
moshe weitzman commentedi think a patch went in to fix this. can someone please try to reproduce this using HEAD drupal? thanks.
Comment #6
tangent commentedPer comment #3 this issue seems to be caused by contributed modules exclusively. I'm setting this to support status.
If the OP still thinks this is a core bug then please submit steps to reproduce the bug.
Comment #7
Patrick Nelson commentedNo, I have a fresh install of 4.7-CVS and no problems. I reckon this WAS caused by contrib. modules but I am not able to say which ones at present. Will still be using all modules that I had installed at that time although not all are currently enabled, so I will keep an eye out for this problem as I carry on building the site and will report the error and reproduce path if it reoccurs.
Comment #8
killes@www.drop.org commentedapparently fixed.
Comment #9
mjolley@buy-hot.com commentedI fixed this by setting global read access to the "files" directory. Probably not the ultimate solution, but I don't currently have any files that need read protection.
Comment #10
(not verified) commented