Products

Solutions

Learn More

Partners

Community

Blog

About

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, ...Exported Template File Throws ErrorExported Template File Throws Error
Previous
 
Next
New Post
8/4/2014 9:42 PM
 

The upgrade did not fix it.

The first invalid element error is for <enablepopups>, then a whole lot of <uniqueid> tags are invalid elements.

I know if I do a site via the Host menu it will work.  Also, if I use the old template file, it will work.

This must just be an XML validation issue, I'm sure.  Tomorrow night I'll look at the portal creation code and make sure the new DNN routine doesn't have a method call I'm not implementing or something.

It will be a simple fix, just a question of finding where it lives.  I'll throw a debugger on it real quick and grab some info, then do another reply to you.

 Thanks!

 
New Post
8/4/2014 10:08 PM
 

Here is my code, it's failing validation below, where I've bolded, italicized, etc.

Since it is working , if only showing a failure, that's a good sign.  Don't know just yet why I can't attach a debugger but even without, nothing jumps out at me here.

Keeping it simple ... I'm missing the right schema definition and that's the problem.  Also, the template file does *not* have an associated .resources file, that jumps out at me.  I'm going to look up portal.template.xsd now and see if the most recent schema just ain't thar. :) (not present)

               try
                {
                    bool blnChild = true; //Set this to true.  Parent Portals will never be created by ABFR
                    string strPortalAlias = string.Empty;
                    string strChildPath = string.Empty;
                    var closePopUpStr = string.Empty;

                    var objPortalController = new PortalController();

                    //check template validity
                    var messages = new ArrayList();
                    string schemaFilename = Server.MapPath(string.Concat(AppRelativeTemplateSourceDirectory, "portal.template.xsd"));
                    string xmlFilename = template.TemplateFilePath;
                    var xval = new PortalTemplateValidator();
                    if (!xval.Validate(xmlFilename, schemaFilename))
                    {
                        DotNetNuke.UI.Skins.Skin.AddModuleMessage(this, "", String.Format(Localization.GetString("InvalidTemplate", LocalResourceFile),
                            Path.GetFileName(template.TemplateFilePath)), ModuleMessage.ModuleMessageType.RedError);
                        messages.AddRange(xval.Errors);
                        lstResults.Visible = true;
                        lstResults.DataSource = messages;
                        lstResults.DataBind();
                        validationPanel.Visible = true;
                        return;
                    }

 
New Post
8/4/2014 10:27 PM
Accepted Answer 

Of course ... all things not rocket science have SIMPLE answers. (Maybe even rocket scientists won't admit it though :) )

And the issue was ... the .xsd file changed.  It needed to be copied down to my module.

Upgrading to 7.3 could not hurt so that was done in the process.  At least it's published now what the cause of this is.

 
New Post
8/5/2014 2:55 AM
 
I am glad you were able to solve your issue.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/5/2014 8:04 PM
 

Sebastian,

Thanks so much for being right there to help.

I've seen more than one post on this including someone who reported it to DNN as a bug.  He probably figured out his schema file was out of date and of course ... didn't want to answer his post with that solution. :)

More important when it is seen that this issue has cropped up that people can find quick answers on Google.

Best,

Mike Durthaler

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Exported Template File Throws ErrorExported Template File Throws Error


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out