Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...Administration ...Administration ...Problem Parsing Default skinsProblem Parsing Default skins
Previous
 
Next
New Post
1/19/2006 3:09 PM
 
J D

Joined: 4/26/2003
Posts: 5

I wanted to make a small tweak to the default skins in 3.2, and when I "Parsed Skin Package" the containers get all messed up. The action buttons at the bottom of the containers go away and I'm left with either "~" as links, or "action button 1" etc...

When I diffed the unparsed original skins with the parsed changed skins, in the container, I saw this:

The parsed Skin:

<TD valign="middle" nowrap><dnn:VISIBILITY runat="server" id="dnnVISIBILITY" /><dnn:ACTIONBUTTON5 runat="server" id="dnnACTIONBUTTON5" /></TD>

 

The original container:

<TD valign="middle" nowrap><dnn:VISIBILITY runat="server" id="dnnVISIBILITY" /><dnn:ACTIONBUTTON5 runat="server" id="dnnACTIONBUTTON5" CommandName="ModuleHelp.Action" DisplayIcon="True" DisplayLink="False" /></TD>

Manually editing the container .ascx file to add back in the missing attributes (CommandName, DisplayIcon, DisplayLink) fixes the problem. So my question is why does parsing the original skins on a default install kill the container.ascx file?
 
New Post
1/21/2006 2:52 AM
 
Scott Willhite


alkihomes.com
Joined: 4/11/2003
Posts: 3047
It shouldn't.  Can you verify that the .html files are unchanged... and let me know which version of DNN you are running?  It is the .html files that are parsed, and the .ascx files generated.  Also look at the log generated on import for any obvious problems?

Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry
 
New Post
1/21/2006 8:14 PM
 
J D

Joined: 4/26/2003
Posts: 5

It's version 3.2, the html files are the original ones from the install zip file. This is the second portal this has happened to me on... the first time I didn't know why, but this time it happened when I did nothing but change "cellpadding" in one of the html skin files.. I didn't change the container html files at all and the container files exploaded after I clicked "Parse Skin Package"

I copied them right from the original zip file into the new website folder: "DotNetNuke_3.2.0_Install" and didn't change any of the container or skin files, and have edited the core or anything like that.

I can also easily reproduce the problem (this is a complete default installation of 3.2, there aren't even any custom modules) just by selecting say.. dnn-blue skin and clicking "parse skin package"... as soon as I do that all the dnn-blue containers break because of those missing attributes and my containers look like this:

Also, during the "Parse Skin Package" routine, I don't see any errors, but I'm pasting the output here for this container just to be sure.

Begin processing file: Image Header - White Background.htm

  • Processing token: [ACTIONS]
  • Token is skin object: Admin/Containers/SolPartActions.ascx
  • Formatting control statement: <dnn:ACTIONS runat="server" id="dnnACTIONS" />
  • Processing token: [ICON]
  • Token is skin object: Admin/Containers/Icon.ascx
  • Formatting control statement: <dnn:ICON runat="server" id="dnnICON" />
  • Processing token: [TITLE]
  • Token is skin object: Admin/Containers/Title.ascx
  • Formatting control statement: <dnn:TITLE runat="server" id="dnnTITLE" />
  • Processing token: [VISIBILITY]
  • Token is skin object: Admin/Containers/Visibility.ascx
  • Formatting control statement: <dnn:VISIBILITY runat="server" id="dnnVISIBILITY" />
  • Processing token: [ACTIONBUTTON:5]
  • Token is skin object: Admin/Containers/ActionButton.ascx
  • Formatting control statement: <dnn:ACTIONBUTTON5 runat="server" id="dnnACTIONBUTTON5" />
  • Processing token: [ACTIONBUTTON:1]
  • Token is skin object: Admin/Containers/ActionButton.ascx
  • Formatting control statement: <dnn:ACTIONBUTTON1 runat="server" id="dnnACTIONBUTTON1" />
  • Processing token: [ACTIONBUTTON:2]
  • Token is skin object: Admin/Containers/ActionButton.ascx
  • Formatting control statement: <dnn:ACTIONBUTTON2 runat="server" id="dnnACTIONBUTTON2" />
  • Processing token: [ACTIONBUTTON:3]
  • Token is skin object: Admin/Containers/ActionButton.ascx
  • Formatting control statement: <dnn:ACTIONBUTTON3 runat="server" id="dnnACTIONBUTTON3" />
  • Processing token: [ACTIONBUTTON:4]
  • Token is skin object: Admin/Containers/ActionButton.ascx
  • Formatting control statement: <dnn:ACTIONBUTTON4 runat="server" id="dnnACTIONBUTTON4" />
  • Formatting control directive: <%@ Control language="vb" CodeBehind="~/admin/Containers/container.vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Containers.Container" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="ACTIONS" Src="~/Admin/Containers/SolPartActions.ascx" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="ICON" Src="~/Admin/Containers/Icon.ascx" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="TITLE" Src="~/Admin/Containers/Title.ascx" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="VISIBILITY" Src="~/Admin/Containers/Visibility.ascx" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="ACTIONBUTTON5" Src="~/Admin/Containers/ActionButton.ascx" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="ACTIONBUTTON1" Src="~/Admin/Containers/ActionButton.ascx" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="ACTIONBUTTON2" Src="~/Admin/Containers/ActionButton.ascx" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="ACTIONBUTTON3" Src="~/Admin/Containers/ActionButton.ascx" %>
  • Formatting registration directive: <%@ Register TagPrefix="dnn" TagName="ACTIONBUTTON4" Src="~/Admin/Containers/ActionButton.ascx" %>
  • Writing file: Image Header - White Background.ascx
    End processing file: Image Header - White Background.htm

    • Any ideas?
     
    New Post
    1/31/2006 8:43 PM
    		 
    Jason Henkle

    www.NerdPowerd.com
    Joined: 1/29/2006
    Posts: 5

    I am currently having the same exact problem with my DNN.  The bottom of all my modules look EXACTLY as his does above. 

    The bottom of all my modules look like:

    Import ContentExport Content~~Move Import ContentExport Content~~Move Import ContentExport Content~~Move Import ContentExport Content~~Move

    Are there any fixes to this yet?
     
    New Post
    2/1/2006 8:49 PM
    		 
    Jason Henkle

    www.NerdPowerd.com
    Joined: 1/29/2006
    Posts: 5
    I was able to log into my Host account and restore the defaults.  This fixed all of my problems!  I then was able to apply my skins properly.  Hope the same works for you.  Good Luck!
     
     Page 1 of 2
    12Next 
    Previous
    		 
    Next
    HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Problem Parsing Default skinsProblem Parsing Default skins


    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