Hello,

The issue I am having is that any page that is a child of any main pages does not pull any of the styling from CSS for the printer-friendly pages. All of the main pages pull the styling just fine, but any children of those pages do not.

No other issues are present. The elements are positioned where I have specified with the php file but nothing from the CSS is coming through.

I'm just assuming at this that the issue lies within conflict between modules but I'm not sure.

Anyone have any problems similar to this?

Thanks!

Comments

doomsdaymine@gmail.com’s picture

doomsdaymine@gmail.com commented

Did you try the link visibility? Also, this might be trivial but try the source code and see if the class for the CSS is being called.

Anonymous’s picture

Anonymous (not verified) commented

Thanks for your response! I work with the person who posted the question. When you refer to "link visibility" do you mean the module's web settings? I believe so.

The "Printer Friendly Version" link is present on child nodes but when you click on the link the printer friendly page displays the module's default CSS file instead of the custom stylesheet.

When we look at the page source of the printer friendly page the custom stylesheet is listed but it isn't affecting the page.

We have created a custom page template for the printer friendly page but I tested it and the same problem exists with our without our custom page template.

I turned off Node Hierarchy in the modules list and cleared the cache and am still seeing the same problem. It sure seems like a Node Hierarchy and Print, email, PDF conflict but maybe there is something else going on.

I've tried both 1.10 and 1x.dev versions. I see the same thing in both versions.

Has anyone experienced this problem?

jcnventura’s picture

jcnventura
Primary language English
commented
Status: Active » Postponed (maintainer needs more info)

I find it REALLY strange that the custom style sheet is listed but it doesn't affect the page.

Can you provide a URL to a page with that problem?

Anonymous’s picture

Anonymous (not verified) commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

We added this module to our staging site to make sure the problem wasn't specific to our development site. We still had trouble. Then I discovered the problem. It was my error, I'm embarrassed to say. I didn't have a slash preceding the macro for the path to the stylesheet.

Instead of

/%t/print-friend.css (this worked for both children and parent nodes)

I had

%t/print-friend.css (this worked with parent nodes only)

I needed to have that initial slash for the style to carry down to the child nodes.

Thanks for everyone's help though. I appreciate it!