I've been working with Drupal for only about 3 weeks now and I really like it. However, seem to be having some strange permission or access errors and I can't figure out why. I first saw this when trying to use the Service_Links module, no matter what I did I could not get the icon images to show up. I've seen the problem again, and more dramatically, today while trying to get the Pixture_Reloaded theme installed and working.
In the case of the Service_Links module, as I mentioned, the icon images for digg.com, facebook, etc. would not show up. If I viewed the source and clicked on the link for the image I get a 403 Forbidden error. I verified that the path was correct, and the permissions appeared to be right but I cannot get this module to show these images. I have quite a few other modules installed, many that I've installed myself, and they work fine.
Today, while trying to get the Pixture_Reloaded theme installed, I seem to be having the same problem. I first noticed it when the I first went to the Administration->Site Building->Themes->List page to select the theme and saw that the screenshot.png image doesn't show up in the list. Again if I view source and click on the link to screenshot.png I get a 403 forbidden error even though the path is correct. I went ahead and enabled the theme anyway and set it as default but when I do drupal loads a plain page with no CSS or images so apparently Drupal can't access the CSS files or anything else for this theme. If I view source and look at the links in the source to the CSS or image files everything looks ok, and the folder and file permissions seem to be exactly the same as the other several themes I have installed so again, I have no idea why it's not working.
Any assistance with this problem would be greatly appreciated!
TIA,
Noel
Comments
Does sound like a permissions problem
What I recommend is that you check that all these files are owned by the www-data user and group.
On Unix this can be fixed using the command:
chown www-data:www-data [filename]with superuser privileges.
You can even do this to all your drupal files by going to the drupal root and using:
chown -R www-data:www-data *again with superuser privileges. This will give ownership, of all files in that directory and recursive directories, to the www-data user and group. All files already with this ownership will stay the same.
Although I am not sure how this is done on Windows.
The site is hosted on
The site is hosted on siteground.com, so I'm not sure I have access to that. I'll have to check. I did just look at the files via FTP and they are all owned by the same user and group as the rest of the themes and modules. At least as far as I'm able to see in gFTP, all of the ownership and permissions in the non-functional theme and module are exactly the same as all the functional themes and modules.
Thanks!
Recent Log Entries
You almost definitely won't have access to do that.
Open up your recent log entries and look for things related to the issue. That could possibly give you some greater insight into what is happening.
Tom Heard
Which log files should I be
Which log files should I be looking in? The logs under Administer->Reports->Recent log entries doesn't appear to have any entries at all related to this problem. The only thing I see in there over the last day or so is notification of cron.php runs. The only error log I can find inside cpanel under my siteground admin page doesn't have any errors listed at all. Do I maybe not have logging turned on somewhere I should? I've looked around and didn't see anywhere I could bump up the level of error logging but I might have missed it.
Thanks!
I found the problem. I was
I found the problem. I was looking at the files under the module and theme directories, but not the module and theme directories themselves. In other words, all the files under sites/all/themes/pixture_reloaded had the correct permissions but the sites/all/themes/pixture_reloaded directory *itself* did not. It had the same permissions as the other modules but it needed a few more apparently. It was set by default to 700. I changed it to 755 and everything is working fine now. I also modified permissions on some other things, like my tagadelic module and the service_links module and everything is working as it should now, including the different font sizes in my tagadelic tag cloud that haven't been working up to this point.