Cpuple of things in one here...

On Jan 30, 11:10 am, "Hoolahawk" <[EMAIL PROTECTED]> wrote:
> We want to create a print friendly page so that users can click on
> "print this page link" to print the page.
>
> I noticed that there is a printfriendly.cfm page that I have linked to
> but when it opens it only displays our home page. Do I use this page,
> if so should I be passing the objectid?

Where are you getting this from?  The standard Mollio webskin?

Essentially you can set up a separate controller (ie. 
printfriendly.cfm) to handle requests that you want to have rendered 
with a different display handler.  If I was following this approach I 
might have a specific displayPrintFriendly.cfm template for each of my 
relevant content types.  The purpose of printfriendly.cfm is to invoke 
the relevant content item with this template.  The template is 
designed to have a specific rendering just for print.

> With CSS Administration I gather that this is so that you can create
> more that one css style and FC imports into a each page, rather than
> handcoding it into each page?
>
> I added a print css via CSS Administration but noticed that it was not
> be included on the page when I checked the source.

In order to use the dmCSS content type you need to include the 
*importCSS* webskin tag in the header of your template inorder to 
import relevant CSS content items from your content tree.

Unless you are going to have different CSS print style sheets for 
different regions of your site tree I'd be inclined to hardcode the 
reference to the print style sheet in the HEAD section of your header 
template.

Hope that helps,

-- geoff
http://www.daemon.com.au/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to