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, ...Registering a Custom Skin Object from SkinRegistering a Custom Skin Object from Skin's Root
Previous
 
Next
New Post
8/24/2009 5:07 PM
 

Hi

I've managed - sucessfully - before to register Brian Duke and Chris Hammond's Engage CSS Selector skin object into a custom skin, like so:

<%@ Register TagPrefix="engage" TagName="CssSelector" src="~/Portals/_default/Skins/MySkin/CssSelector.ascx" %>

BUT I was wondering if there was perhaps a way of registering the object to the skin's root using a relative path...  ...essentially skipping the "~/Portals/_default/Skins/MySkin/" bit and just having it like so:

<%@ Register TagPrefix="engage" TagName="CssSelector" src="~CssSelector.ascx" %> or
<%@ Register TagPrefix="engage" TagName="CssSelector" src="~/../CssSelector.ascx" %> or whatever...

Is this do-able..?  I ask because if I'm not managing the site and the client / admin decides to install the skin on another portal, the object won't be registered...

Any help would be appreciated.

Jon


Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

 
New Post
8/24/2009 5:21 PM
 

OK, so I might have answered this for myself....

I tried:

<%@ Register TagPrefix="engage" TagName="CssSelector" src="CssSelector.ascx" %>

(with the .ascx file sitting directly in the skin's root) and it seems to have worked...  Weird, somehow didn't expect it to...  Any thoughts?


Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

 
New Post
8/24/2009 5:37 PM
 

OK, it's (simplified) like this:

A skin is a ASP.NET usercontrol (ascx) and DNN adds it to the page (default.aspx)
A skin object is also a use control and it's placed inside the Skin usercontrol.

To include a usercontrol in another usercontrol you need the location relative to the parent user contro (to register it).

Normally if you install a skin object this is in the DesktopModules/.... folder, so you need a path from the root or the control will not be found.

If you place a skin object (or any other ASCX file) in the skin folder, you don't need the slash, you just use the path relative to the skins usercontrl (ascx)

So, you don't have to install a skin object in DNN, it's just more convenient (especially now they register a version number in DNN5)

HTH

 
New Post
8/24/2009 5:52 PM
 

Hi Timo

Thank you for your explanation - makes sense.  And that's way DNN in essentially in a form (ID = #Body).

Cool.  I'm packing the Skin Object as part of this skin, so no need to install it.  Just register.

Jon


Shebang Websites - A product of Mogridge Design
Hey, we're partnered with UntangleMyWeb.com

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Registering a Custom Skin Object from SkinRegistering a Custom Skin Object from Skin's Root


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