When specifying my custom stylesheet, it says "File ... is not readable by the web server." Yet my stylesheet is still picked up and it works well.

I see this was an issue with the 6.x version #883086: Cannot Un-Select Printer-friendly URLs list Option or Change Any Other Attribute Options Under Settings, but in the 7 version it still throws the error.

Comments

pixelsweatshop’s picture

pixelsweatshop commented

It appears it only happens on the first time i set it. When I return to change the css file it does not throw up the initial error.

jcnventura’s picture

jcnventura
Primary language English
commented
Status: Active » Fixed

Actually, from testing what I saw happening is that it is still complaining from a previous entry..

I've fixed that case now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

silurius’s picture

silurius commented
Version: 7.x-1.0-alpha2 » 7.x-2.0
Issue summary: View changes
Status: Closed (fixed) » Needs work

I am also experiencing this problem, but it persists even after saving the settings more than once. And the custom stylesheet is not being loaded. The permissions on the CSS in question are 0644 (rw-r--r--).

silurius’s picture

silurius commented
Status: Needs work » Active
Tokoh’s picture

Tokoh commented

Version 7.x-2.0. I do not have wkhtmltopdf enabled.

I an experiencing this problem. At one stage it did work and the css from this invocation still works.
I then tried moving the file and since then, each time I move the file and try to save the configuration I get the error message, "File /home/united2/public_html/sites is not readable by the web server.
I've tried enabling, disabling and reenabling it. After each step clearing cache, just in case.
I moved print.css to the root (public_html) and enabled and it does not find it. But I would expect this because the path is now empty and this you would expect would turn the private css function off.
For example I moved print.css into the sites folder and got the message: File /home/united2/public_html/sites is not readable by the web server.
However the key could be the message: "File /home/.........." The critical word being File not folder!
If I change the configuration path to include the filename, for example sites/print.css it works and the css is active.
However when I try to move the folder to sites/default I get an error from cpanel filemanager: "ERROR: Could not create file "print.css" in /home/united2/public_html/sites/default: Permission denied" Now I cannot create a file of folder in default. Its permission is 555.
Normally filemanager can create files and folders anywhere, so my guess is that the print module is changing permissions in some way.
For now I have left the print.css file in sites and changed the print module configuration to sites/print.css and it works but the functionality of file manager is degraded. I cannot create files or folders in default. I'm not sure of the extent of effect of this problem.

silurius’s picture

silurius commented

That's an interesting workaround, Tokoh. Unfortunately I do not have the option of directly placing content into the /sites directory for one of my important sites, so I'll still be looking for other workarounds or a solution.

dshields’s picture

dshields commented

Check to see if there is white space before or after the path you entered. That was my issue

kentjames1980’s picture

kentjames1980 commented

the correct path to the custom style sheet is to the file not the folder so :

sites/all/themes/yourtheme/print.css

not

sites/all/themes/yourtheme/

just in case anyone has this issue in the future

bygeoffthompson’s picture

bygeoffthompson commented

I encountered this error and began troubleshooting before I realized how stupid I was. I set the path for my custom stylesheet within the module before I added the `print.css` asset to the server.

Once I uploaded the file to the defined directory the error stopped appearing for me.

Hope this helps another idiot out there :).