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, ...<%=skinpath%> causes HTTP 404 Error on certain pages<%=skinpath%> causes HTTP 404 Error on certain pages
Previous
 
Next
New Post
4/28/2006 6:25 AM
 
The result of a this thread is this:

If you get this error
Server Error in '/DNN/test/' Application
The resource cannot be found
if you apply a skin to a page and you have <%= SkinPath %> somewhere in your skin, the real problem is that you don't have a pane with "id=ContentPane" in your skin.

The added SkinPath variable is just hiding the DNN message, that it cannot find the ContentPane.

(I guess only people that are skinning in ascx instead of HTML can make this mistake)

---------------------------------------------------------------------------------
My original post:
I created my own skin which works okay, but now I'm trying to use
<img src="<%=skinpath%>img/01.jpg">
This causes an error:
Server Error in etc....: "The resource cannot be found" (HTTP:404)
The strange thing is that this only happens when applied to a certain page. If I apply the skin to a different page it does work, and if I remove only
<%=skinpath%> from the skin  the page loads normally.
Ofcourse I can remove the page and create a new one but I think a skin should never cause an error like this.
Normally it doesn't, if there's a bug in a skin you get a nice DNN error on top of the page.
Anybody any ideas?

DNN 3.2, page language VB.NET


 
New Post
4/28/2006 7:24 AM
 
Yes, you shortened it up a little too much.  It's supposed to be <%= SkinPath %> with spaces around the SkinPath word...
 
New Post
4/28/2006 8:03 AM
 
Thanks for the reply.
I used <%= skinpath %> in my page, but not in my post....
I tested <%=skinpath%> and <%= skinpath %> but either of them doesn't change the behaviour of the page.
If I try something useless like <%= sdfsdfasdf %> I still don't get a HTTP 404 error. I tried making a new page and apply the skin; no problem, the problem is in the page somehow I guess. But where did the problem come from......
I've had this problem before, then solved it by making a new page, but since it happens again, I want find the reason......  I've seen some other posts about the subject but none of them has been "solved"
Timo
 
New Post
4/28/2006 9:54 AM
 

One word of caution.

You can not use <%= SkinPath %> inside an element that has an attribute runat=server.

I don't know if this is the problem you are experiencing, but thought I would mention it.

You can read more about it here:

http://blogs.snapsis.com/PermaLink,guid,381f9036-432e-468c-bc2e-b52ab86f12ea.aspx

 


DotNetNuke Modules from Snapsis.com
 
New Post
4/30/2006 2:15 PM
 
I'm aware of that. The strange thing is that one pages doesn't and all the others do accept the skin......
Thanks for your time, Timo
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...<%=skinpath%> causes HTTP 404 Error on certain pages<%=skinpath%> causes HTTP 404 Error on certain pages


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