Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Image relative location did not get updated.Image relative location did not get updated.
Previous
 
Next
New Post
1/15/2007 8:05 AM
 
I just tried in DNN 4.4
<div style="background-image:url(<%=skinpath%>image.gif)">
Does get processed in that version, so the text in the skinning document is correct.
 
New Post
1/15/2007 8:22 AM
 

Timo,

the <%= skinpath %> bit is just short for <% response.write(skinpath) %>. This will be interpreted by asp.net each time the control is loaded. As the browser will never know the original code, and just sees the output (the complete path of the skinfolder in this case), it will work in any location that needs a reference to the skinpath (and makes your skins portable in the same time)

 


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
1/15/2007 11:24 AM
 
Erik,
I know, I use it all the time, the original poster was only complaining about inline styles not being processed,
It seemed unlogical, but if so then... ( I never use inline styles, but you are right there is no real reason why they wouldn't work)

You write:
"it will work in any location that needs a reference to the skinpath"
Isn't there one (small) exception?  You cannot pass it to a skinobject like this, can you?
 
New Post
1/15/2007 11:36 AM
 

correct, because the call to a skinobject is already serverside code, notation like <%= %> only works in plain html that is part of the server page, and a remnant of the old ASP vbscript language

Anyway, you should be careful using too much interpreted code in your skin, i'm not sure what it does for performance. I'd think using inline css like this makes the skin load just a little bit slower. For a busy site that might translate in a considerable performance loss


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
1/15/2007 6:26 PM
 
ErikVB wrote
Anyway, you should be careful using too much interpreted code in your skin, i'm not sure what it does for performance. I'd think using inline css like this makes the skin load just a little bit slower. For a busy site that might translate in a considerable performance loss


I sometimes have quite a lot of VB code in my ascx file (yes I know I should start creating modules ;-).
Maybe I'm missing something, but why would this be slower compared to the situation where this code would be in a module?
My idea is that it might slow the page a bit down the first time it's used or after an app restart, since it has to be compiled, but if it is it shouldn't make a difference, should it?
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Image relative location did not get updated.Image relative location did not get updated.


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out