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 4.8.1 Not able to detect skins copied to Portal\0\DNN 4.8.1 Not able to detect skins copied to Portal\0\
Previous
 
Next
New Post
3/18/2008 6:25 PM
 
Why is it that in DNN 4.8.1, I can no longer copy a previously extracted skin folder from Portals\_default\skinname to 
Portals\0\skinname ?
 
Although perhaps not the best practice occasionally we have to clone extracted skins from 
Portals\_default\skinname to Portals\0\skinname. We then will alter those skins as needed.
And as always like in DNN 4.7, DNN is able to pick these extracted skins up on the Site level under Appearance.
 
Then we just go under Admin or Host site settings > expand Appearance and select Site radio button and the dropdown is able to pick up our new modified skin ascx files and folder we just cloned from Portals\_default\skinname into Portals\0\skinname.
 
Here's the problem… This Worked in DNN 4.7 BUT IN DNN 4.8.1 no skin directory shows up when Site radio button is selected for appearance! We’re only able to clone containers from Portals\_default\containername to Portals\0\containername.
 

What happened? And how do I get DNN 4.8.1 to recognize skins on the APPERANCE>SITE level if I need to clone them from Portals\_default\ to Portals\0\ ?

 
New Post
3/18/2008 7:47 PM
 

browse to the filemanager and click the "synchronize files" image in the top right, it will parse the folders and add references to any files that have been moved into the site structure.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/19/2008 10:30 AM
 

Thanks Cathal for the reply..that was a good suggestion but...
Unfortunately re-synchronizing files Did Not Work.... Is there something else i can try? Does anyone else see this happening in 4.8.1 ?

Is this another bug or a "Feature" of 4.8.1?
Was there a change in 4.8.1 ?
Is anyone else noticing this problem?

If there is something else i can try please let me know.
This is the 1st time I’ve noticed that I’m not able to activate skins cloned to Portal 0 and then proceed to  activate them Site level from the Host or Admin Appearance settings. The drop down for the site level is still not picking them up...

I'm thinking about switching back to 4.8.0 which still allows you to activate skins on the site level.
This is very strange... the installation seemed normal and went with out a hitch. I did a 4.8.0 install 2 weeks or so ago and no problems when i had to activate skins on the site level under the appearance settings.

Any thoughts?

 
New Post
3/19/2008 12:39 PM
 

It appears that there were some security changes made to the skin parser for security in 4.8.2 that may have Inadvertently created a non-wanted feature where designers such as my self who often clone or copy skins to the Portal 0 folder.

I went ahead and upgraded to 4.8.2 and the problem still exists even when you're logged in as a super user. Files copied or cloned to Portal 0 are not viewable when the Site radio button is selected under the Appearance settings.

What is interesting, is that under Filemanager and if you select Portal Root, you CAN easily see any new files or skin folders copied to Portal 0.
They are just not accessable under Apperance>Site settings drop down list.
I'm very courious as to whats happened and what can be done to fix this.

I'm begining to think this is a Bug myself.... and may just have to design my new site as a 4.8.0 like my other ones until DNN fixes this or provides a work-a-round or point out a setting that i'm over looking.

I would appreciate further feedback on this from other fellow DNN Designers.

 
New Post
3/21/2008 4:09 AM
 

The changes are only in 4.8.2 and prevent the parsing of a skin if the admin doesn't have skin upload rights.

Did you try this on a fresh DNN 480 install, or is it an upgrade?

If you want you can send me an email with the skin so I can try to reproduce...

timo .... breumelhof AT dotnetnuke ....com

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNN 4.8.1 Not able to detect skins copied to Portal\0\DNN 4.8.1 Not able to detect skins copied to Portal\0\


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