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, ...Troubleshooting Container/Skin uploadTroubleshooting Container/Skin upload
Previous
 
Next
New Post
1/26/2007 2:33 PM
 

I'm at my wits end with this.

After creating a container or a skin I go through the process to upload to DNN 4.0.3.7 as a zip file (Using XP's own zip utility) and a good portion of the time the zip file does not get processed. It will just send me back from wence I came (Usually back to either the Skins or Container selection) without even a whimper of an error.

How can I beat DNN in to submission, or retrain myself to get it to do what it is suppose to do?

 
New Post
1/27/2007 4:41 PM
 
What is the file size of your skinpack - in older versions of DNN, the uploader did have problem with uploading large files.

This is fixed in new versions, but if you have upgraded from 4.0.3 then chances are that the upgrade was not done correctly

Salar
 
New Post
1/28/2007 1:32 PM
 

The container is 4k.

The skinpack is 151k.

I really couldn't say if there was wrong with the upgrade, as I inherited the installation from a previous administrator. At one point I think I even tried copying a DNN skin and uploading it and it didn't parse it. I'm wondering though if it is a stupid browser cache issue where IE sees that a URL is the same and just provides the cached page (thus sending me off to unexpected results). But then I cleared cache, deleted files, restarted browser and the same thing happened. It seems to be hit and miss.

Would it be possible to just manually upload the files and pray that some built in mechanism says oooh, look there's a new directory under containers/skins let's show it to the user and then allow the user to parse out so I can make a new ascx (or what ever the extions is) file.

 
New Post
1/29/2007 7:19 AM
 

You can FTP the skin package to the \Install\Skin directory, then browse the 'install resources' URL to invoke the web-based installer.  It will be http://www.yoursite.com/Install/Install.aspx?mode=InstallResources 

BUT ~ The problem sounds like an improperly formatted skin package to me.  When packaging files for the skin, files should be zipped using relative file paths to the skin definition files.  You should make sure that relative file path information in the zip file matches the relative path information in the skin definition files.

 

 

 
New Post
1/29/2007 12:30 PM
 

I'll give the FTP and other options a shot.

Don't see how the files can be improperly formatted. I've even gone as far as to have it work then apply it again without change and still do nothing. I have noticed though, sometimes I can turn off the web services and restart them and have it work.

Not sure what the InstallResources is suppose to do but I went to it and just three lines popped out. But I'll be sure to keep this in mind for the future.

Installing Resources

Install Resources Status Report

Installation Complete

By chance does IIS itself have some sort of built-in caching mechanism?

Thanks for  your assistance by the way.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Troubleshooting Container/Skin uploadTroubleshooting Container/Skin upload


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