Sorry, I responded before I got your response. I'm still trying to figure out why our clink.external got corrupted. I've searched for any sort of documentation on clink and come up empty handed.
Bob -----Original Message----- From: David Sean Taylor [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 4:57 PM To: Jetspeed Users List Subject: Re: clink.external problem On Monday, June 16, 2003, at 01:05 PM, Bob Fleischman wrote: > The content.vm, default.vm and preview.vm files (in > templates\layouts\vm\html) contain > > <base href="$clink.External" /> > <link > href="$clink.setURI($config.getString("site.stylesheet")).Absolute" > type="text/css" rel="stylesheet" /> > > What should we be using to replace clink.external? > $jslink.HomePage also works After some review, I've found that $clink is not deprecated but required to make links to static content in the portal deployment. So it is ok to use $clink when linking to static content. -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] +01 707 773-4646 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
