I'm getting this error when trying to use the Andreas-09 skin:

Could Not Load Skin: /Portals/_default/Skins/andreas-09-logo/2col-left.ascx Error: The file '/Test/Portals/_default/Skins/andreas-09-logo/2col-left.ascx' does not exist.

The files are there, and I did try re-parsing both ways, first using local then portable on the options for the parsing. I've taken care of the House of Nukes Skin Objects, and also the Default.aspx file so I have followed directions as published in the article....

Any suggestions?

Thanks,

CT

Hello,

I'm not sure what has caused that, do any of the other skins display in the andreas package? - have you successfully installed any other DotNetNuke skins to your website?

Here's summary:

1) Fresh install of DNN 4.8.2 - works fine.

2) Install of all DNN Creative skins - works fine.

3) Test of each DNN Creative skin on default (initial) portal by applying skin to portal -works fine including the Andreas-09.

4) Now create new portal in current DNN install by using the site templates provided by DNN Creative for each of the skins. No longer works fine and now get the errors whether for Andreas-01 or Andreas-09 etc.

5) Try to run the Site Wizard and again apply one of the site templates. Still get the errors.

So it's not in the skins themselves, and it's not in my DNN installation or the Default.aspx or the House of Nuke SkinObject. It's got something to do with the site templates. Here again are the kinds of errors reported:

Could Not Load Container: /Portals/_default/Containers/andreas01/h1 title.ascx
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled error loading module. ---> System.Web.HttpException: The file '/andreas9/Portals/_default/Containers/andreas01/h1 title.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.LoadContainer(String ContainerPath, Control objPane) --- End of inner exception stack trace ---

So I'm now wondering whether it has something to do with whether the portal is child or parent, etc.  Could you please reclarify any considerations related to child/parent portals?

I thought they could be converted back and forth in order to go from localhost/test to www.test.com and use appropriate aliases and always declare them to be parent portals which is what I've been doing. Should the DNN Creative site templates for the DNN Creative Skins be able to handle this?

Thanks

CT

Hello,

I did a quick test in 4.8.2 with the templates, installed them to the default portal, and then created a new portal with the templates and both times worked.

The only thing I can think of is the location of the skin files. On this occasion the skin was installed using the Host menu and not the Admin menu, perhaps this is why the template can not find the skin files when you are applying them when first creating a portal.

However, you could try creating a portal using the DNN template and then using the admin menu / site wizard to apply the Andreas template - using the site wizard you can specify which skin to apply to the template.

It is due to long path,use www.deletelongfile.com to resolve it