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, ...Disable site containerDisable site container
Previous
 
Next
New Post
12/21/2010 3:43 PM
 
Is there any way to disable a container site-wide to allow for its being uninstalled? Or alternatively, to look up the pages where a container is being used?
 
New Post
12/22/2010 12:33 PM
 
To expand on the situation a bit: I'm doing a couple of adjustments on a skin for a client. When uploading my adjusted version of the containers file, I used the Admin Extensions uploader rather than the Host Extensions uploader, not realizing that the previous version was installed through Hosts. As a result, in Extensions it shows the updated skin (v. 1.0.1), but it appears to have retained the old version as well somehow. As it stands, if you select the container with the "Site" radio button selected, you get the correct container, but if you select it with the "Host" button selected, you still get the old version. When I try to install the updated version over the old version in Host Extensions, all I get is a note that it's already installed (no option to repair). This is going to be confusing for people using the site.

My initial thought was to simply delete the container pack and reinstall it correctly, but I've run into another strange hiccup: Despite the fact that I've gone over the site with a fine toothed comb and changed every place I could find where the container was being used, Skins still claims it's in use and Extensions won't allow me to delete it. I'm trying to figure out how to proceed from here.
 
New Post
12/22/2010 4:26 PM
 
Do you have file system access?

If so, I would just move the container folder from the portals/#/ folder to the portals/_default folder

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
12/22/2010 7:22 PM
 
Thanks for the advice. I'll give that a shot.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Disable site containerDisable site container


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