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, ...Skin tokens and skin objectsSkin tokens and skin objects
Previous
 
Next
New Post
2/6/2011 4:21 AM
 
I have a skin object that works when you enter it in the ascx file. But when you add it to the html file, it fails to parse the object into the ascx file.it fails to register and to translate the token. There is a skin.xml file, and the parser reads it, because when I make an error in the xml file, the parser will give an error warning.

It used to work under DNN 4.

Two questions:

(1) I have been searching for instructions on the creation of skin tokens, but found nothing that explained the process. Can anyone direct me to apropriate documentation? Installing the extension no longer adds the skin token to the table SkinTokens (which I guess it should do)

(2) I would like to check and eventually step through the functions involved in parsing the skins. The DNN source code is pretty new to me and I'm still trying to find my way in it. I've done a search for "SkinTokens" through the source files but the only reference I find is in the SqlDataProviders for 05.01.00 adding a column to the table. Can anyone tell me where in the source the parsing happens?

____________________________________
The one-eyed in the land of the blind.
 
New Post
2/6/2011 6:54 PM
 
The best way to do thing is for a skin object to be installed using the module / extensions installer if you want it registered and parsed correctly from HTML.

There are a lot of details on manifests and installing elements in the wiki.
http://www.dotnetnuke.com/Community/W...

Westa
 
New Post
2/7/2011 3:05 AM
 
Wes Tatters wrote:

The best way to do thing is for a skin object to be installed using the module / extensions installer if you want it registered and parsed correctly from HTML.

 That much I know.But sometimes this is not enough. I am cleaning up the source code of an extension that worked under DNN 4 but has some problems under DNN 5. This is one of those.



However, while cleaning the code (I currently reduced the obsolete warnings from 102 to 70), I may have unknowingly corrected a part of that problem: Now my skin produces an error when applied to a page, which it formerly did not do, the skin token went unchanged through the parsing process. Now it has processed it but with an error. But that means that now I have some firmer ground to find the issue. I have to research this more closely, but I think by the end of the week, I will have solved at least one of the (3) outstanding issues.


____________________________________
The one-eyed in the land of the blind.
 
New Post
2/7/2011 3:34 AM
 
one more hint: when parsing an HTML skin for cnvertion to ASCX, the token name is taken from Skinobjects table in DNN, i.e. the name must match the token (though I am not sure about capitalization atm).

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/8/2011 3:52 AM
 
This is mostly an issue if the skin object was not correctly installed
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Skin tokens and skin objectsSkin tokens and skin objects


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