custom stylesheet doesn't work after update to 6.x-1.11 [#886766]

%t/css/print.css is the path i input. I get the following error when trying to save:

File /home/fishh1/public_html/themes/garland/css/print.css is not readable by the web server.

Strange thing is, I'm not even using garland as the default theme. Garland is just set as my admin theme. Everything worked fine before the update. Can someone else try to duplicate and see if they are having the same problem? I know the path variables allowed in the field changed because the old version was %b%t/css/print.css

Comments

Comment #1

jcnventura CreditAttribution: jcnventura commented 18 August 2010 at 15:00

I hadn't foreseen that possibility :) I'll try to figure out a way to check the path of the site's default theme instead of the current one.. Or else remove the error.

João

Comment #2

apmsooner CreditAttribution: apmsooner commented 18 August 2010 at 15:06

Not just the error is the problem by the way... it never actually saves the settings and applies the correct css. Just wanted to clarify.... thanks by the way!

Comment #3

fmesco CreditAttribution: fmesco commented 18 August 2010 at 15:27

Me too - I am using custom content type-specific templates for my nodes and after the update my print templates no longer work as expected.

Comment #4

jcnventura CreditAttribution: jcnventura commented 18 August 2010 at 17:30

Status:

Active

» Fixed

I've committed to CVS some code that makes unreadable custom CSS file a warning and not an error when submitting the settings form.

João

Comment #5

fmesco CreditAttribution: fmesco commented 26 August 2010 at 14:23

The update to 1.12 did not resolve my issue. When using custom print templates per content-type (print.node-content-type.tpl.php) to define print styles, the field values are no longer visible, making the printed version useless. I had to once again revert back to version 1.10 to correct the problem.

Comment #6

apmsooner CreditAttribution: apmsooner commented 26 August 2010 at 15:53

The print urls issue also exists in 6.x-1.12. Unchecking the boxes doesn't stop the output of those links.

Comment #7

jcnventura CreditAttribution: jcnventura commented 26 August 2010 at 19:32

Status:

Fixed

» Active

Versions of the module from 6.x-1.11 will now use whatever node template your theme is using. In the normal case, this would enable a better match to the normal version.

In some cases, it may be that you actually want different fields to be printed, and that can be achieved by using different build modes, but you now have to test the current build mode in the template in order to decide whether to show those fields.

João