Support Forum

How do I get the absolute path of a stylesheet?

Code

<!--[$stylepath]-->

...doesn't give the URL of the site, and it cant be combined with:

Code

<!--[pngetbaseurl]-->

...because it results in something like:
http://www.mysite.co.uk/P...yTheme/style/style.css

Thanks all




edited by: ntward, Mar 08, 2007 - 10:01 AM

For what do you need that? $stylepath is usually sufficient.

-----
best regards from Kiel, sailing city

Steffen Voß

Member of the PostNuke Steering Committee
Visit: Kaffeeringe.de - Internet & Kreativität

The Stylepath, and other theme paths, use the base URI rather than base URL. Within the theme module I can't really see the need for using the URL rather than the URI.

-Mark

The modulestylesheet plugin creates complete urls for stylesheets.




-----
"He is not dangerous, he just wants to play...."

Frank,
Looking at my current SVN install that doesn't seem to be the case. In the admin panel page I have

Code

<link rel="stylesheet" href="/PostNuke_SVN/trunk/PostNuke/themes/andreas08/style/style.css" type="text/css" media="screen,projection" />
<link rel="stylesheet" href="/PostNuke_SVN/trunk/PostNuke/system/Admin/pnstyle/navtabs.css" type="text/css" />
<link rel="stylesheet" href="/PostNuke_SVN/trunk/PostNuke/system/Admin/pnstyle/admin.css" type="text/css" />

All use the URI rather than the URL.
-Mark

Right, I mixed URI with URL. Mea culpa.

I need a day off....





-----
"He is not dangerous, he just wants to play...."

Hi all,
I need it for my site-wide RSS feed module. The XSL stylesheet loads a CSS style sheet, and for some reason I need to have the complete path included for it to work. The relative path fails.

Ideally I don't want to hard code it, so I can easily use it on several sites. Also, I need use a stylesheet from the theme rather than the module for consistency.

What am I missing?

Nick,

I take the point of the use of these variables in 'pages' to be served remotely. Should, at some point, we introduce stylesheets into our rss and atom themes we would run into the same problem. I've updated these paths to be URLs rather than URIs. This makes no difference to the browser and solve your problem.

This will be in the next daily.

-Mark

Mark,
Cheers!