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, ...DNN 5.1.2 skin install package installation abortedDNN 5.1.2 skin install package installation aborted
Previous
 
Next
New Post
9/21/2009 11:03 AM
 

Timmo thanks for the help.

It is entirely possible that in error I installed this skin package through the ADMIN extensions function at one point because I have do have the same skin name in portals/0/ and portals/_default/ and I am now all jammed up.  I will consider the SQL options you provided in later posts.

My contianers package is ending up in portals/0/ everytime even though - I swear I am using the host extension - and the path name in manifest states _default.  I have repeated this time and time again.  Please advise. So far I do not have an issue with loading containers because they always end up in portals/0/

Judy

 

 

 

 
New Post
9/21/2009 1:35 PM
 

Timo:

I don't know if there is more to this issue.  I logged into my host provider (PLESK) and deleted the skin package that was in the portals/0/.  When I go back into the website now I can no longer see this skin package in admin->skins when the radio button is set to site (I could before I did the delete in Plesk).

When I go to extensions (selected from the top right) I still see two versions of the skin package listed 1.8 and 1.9 with the SAME name.  Why do I still have two - did loading the skin package in portals/0/ cause an error that caused two versions to show in host -> extensions or is there another error and my carelessness of loading in admin -> extension (poetals/0) just added confusion and clouded this bug?  I do not understand why having a skin of the same name in portals/0/ and portals/_default would cause this duplicate and the inability for the load process to use/delete temporary files.

Judy

 

 
New Post
9/21/2009 2:43 PM
 

In dnn 5 a skin is an extension, if you delete the folder through Pleak, it is still installed.

You should deinstall the skin from the Extensions page and then the fodler should be removed also.

If I install your skin from Host > Extensions it ends up in the Portals/_Default/Skins folder.

You should make sure you uninstall the skin (not delete the folder) and then try again.

 
New Post
7/20/2012 7:06 AM
 
How To create New Skin In dnn 5.1
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNN 5.1.2 skin install package installation abortedDNN 5.1.2 skin install package installation aborted


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