DNN 4.8.1 Not able to detect skins

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 \ ?

Just how do i get skins to show up when cloned Portals\ 0 \skinname ?

Yes very curious indeed on the banners.... i panicked when i saw it...

Anyway in regards to skins folder not showing up if cloned to the Portal 0 folder,
I tried to browse to the filemanager and click the "synchronize files" image in the top right, which should have parsed the folders and added references to any files that have been moved into the site structure.

This approach Did Not Work... so i'm back to squar One.
Anything else i can try, I will Strongly consider.

Do you think this is a bug or a "Feature"  thats been added to DNN 4.8.1.
Is there something i'm perhaps over looking?

This is the 1st time i've noticed that i'm not able to activate skins on the Site level from the Host or Admin appearance settings. I'm thinking about doing switching back to 4.8.0 which still alows you to activate skins on the site level.
Thanks for all your help and feedback.

I haven't been able to confirm anything yet, but I do see that they changed the skin parser for security in 4.8.2

http://www.dotnetnuke.com/News/SecurityBulletins/SecurityBulletinno13/tabid/1149/Default.aspx

Thanks John... very much appreciated... The link does shed some light on this issue and although DNN fixed a previous security issue, it appears that they may have Inadvertently created a non-wanted feature where designers such as my self will 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. Do you think it may be a folder security permissions issue?

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...

As always... keep me informed if you find anything new or there is something i'm over looking.
Hope i don't sound too defeated... but hey thats the industry that we're in....

Thanks i did try the restart application and unfortunataly DNN did not recognize any files copied to Portal 0
However.....
Through Trial and Error i think i found a work-a-round.

Here are the steps....
1) Login as a Super User
2) Select Admin>Skins
3)Select Upload Skin (Just use some old skin zip file as you can delete it later)
4)This creates a Skin folder under portals 0 which includes the basic temporary skin you just uploaded.
5)NOW copy or clone any previouly extracted files from Portals _default to Portals 0
6)NOW you can go to Host or Admin and select Site settings then Appearance and select Site radio button You will see the New Copies of skins moved to Portals 0
7) At this stage you can delete the basic skin folder. From here on out you'll have the freedom of moving folders back and forth to portals 0 as you test and modify them for portal 0 on the fly

Again this may not be the best way, but as a designer sometimes you may want to refine your skins under different portals on the fly instead of re-uploading an entire skin packages and start over with hit and miss refinements for different portals all over again.

It appears that in recent versions of DNN, it needs something establishted in the database that there is a new skin under Portals 0

pretty interesting.