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, ...New skinning framework vs legacy skinningNew skinning framework vs legacy skinning
Previous
 
Next
New Post
10/6/2009 5:54 PM
 

Hi guys,

I do apologize up front if this post is a duplication of a previous question.

After some heavy, deep searching on Yahoo!, Bing, Google and Ask! I stumbled upon a blog entry that neatly explained the new manifest file (a similar post on this forum was of absolutely no help to me) which I tried to implement on my testing skin. Now from what I've read is that having a manifest, and HTML file with the required <object> tags embedded where necessary, should be perfectly valid for a skin type based on the new framework? Unfortunately I cannot get this statement to bid true for me, I get the following:

A critical error has occurred.
Data at the root level is invalid. Line 1, position 1

I wish I had a degree in rocket science, because that does not tell me anything about where my packages is at fault. So I thought I'd do an assessment on my package. Currently it contains 6 files:

skin.css
index.html
testing_skin.dnn (manifest)
license.txt
releasenotes.txt
index.doctype.xml

index.doctype.xml, which is the first document to get parsed by the extension's wizard from what I can see (first file in the packaged) contains only the required definition for the DOCTYPE declaration, as per previous versions of DNN. I cannot see anything wrong with this:

<SkinDocType>

<![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">]]>

</SkinDocType

Second to that is my HTML file. It contains only my <body> that needs to be displayed on the page. Now I've only found ASCX based examples online, but noted from Wrox Professional Dotnetnuke 5, following the traditional HTML route should still be seen as a valid DNN 5 skin allowing as long as the required manifest file has been included. The html file does not contain any TOKEN pointers, it has been replaced by the new skin object framework (<object>) so in all theory this should not case the above mentioned error.

I have to TEXT files that just contain license agreements to the skin that I'm testing.

The manifest file (testing_skin.dnn) also the name of my sking (testing_skin) contains the required fields for my skin:

<dotnetnuke type="Package" version="5.0">

  <packages>

    <package name="Testing Skin" type="Skin" version="1.0.1">

      <friendlyName>Testing Skin</friendlyName>

      <description>skin created by Joblogs</description>

      <owner>

        <name>Eric Truter</name>

        <organization>Sixt4</organization>

        <url>http://www.sixt4.co.za</url>

        <email>eric.truter@sixt4.co.za</email>

      </owner>

      <license>No warrenties, support for Sixt4 clients only</license>

      <releaseNotes>First release version of this skin for Testing Skin</releaseNotes>

      <components>

        <component type="Skin">

          <skinFiles>

            <skinName>Testing Skin</skinName>

            <basePath>Portals\_default\Skins\Testing Skin</basePath>

            <skinFile>

              <name>index.html</name>

            </skinFile>

            <skinFile>

              <name>skin.css</name>

            </skinFile>

          </skinFiles>

        </component>

      </components>

    </package>

  </packages>

</dotnetnuke>

I can't see anything wrong with this file either. The last file is the skin.css which is required as the base skin for the site, assuming that framework automatically knows that the skin.css file should be the base stylesheet for the site.

With this assessment not helping, I assumed that the system would trap more detailed errors something else (EventLog, SQL Database, log file) but no such luck.

I'm really at a loss here, and would like to start utilising the new framework, but with this obstacle in my way, I don't see me progressing anywhere. I also tried to search for similar cases, but no luck.

I would really appreciate any help with this.

Regards,

Eric

 
New Post
10/6/2009 7:52 PM
 

Hi Eric,

My apologies as I am about to run out the door, so I havent had the chance to read your post properly.

You can compare you skin manifest with my skin manifest builder here: http://dotnetnuke.mywebsitedesigner.com.au/

Let me know if this helps ;)

 
New Post
10/7/2009 3:13 AM
 

I agree the error message is not very helpful.

I have a few questions;

1. What (exact) version of DNN are you installing this skin on?

2. Is the post that did not help you this one? And if so, could you tell me what's unclear about it?

(I might be able to make it clearer, I have not had a lot of feedback on it)

3. Would you mind sending me the skin package, so I can test it myself (messmail at  yahoo d0t c0m)?

Thanks, Timo

 

Thanks, Timo

 

 

 
New Post
6/24/2010 3:38 PM
 
Hello,
I was also getting the following error while trying to update a skin:
A critical error has occurred.
Data at the root level is invalid. Line 1, position 1

What seems to have fixed it is that I excluded a "_vti*" folder, that was created by "Microsoft© Expression Web™", from the ".zip" file. These folders (which might be hidden) are created automatically when you edit files. When I zipped the skin folder without the "_vti*" folder and uploaded it, I was able to update the skin without errors.

Bienvenido Cancel
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...New skinning framework vs legacy skinningNew skinning framework vs legacy skinning


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