Re: Is the naming of a container skin work differently when logged in as admin of a portal vs. host?

SDodds — Tue, 04 Oct 2005 04:24:22 GMT

Hi Tim,
Your doing nothing wrong as far as I can see this is just the way it (DNN) works.

Skin management reads the folder names from .../portals/_default/skins/ [for host-global skins] and .../portals/x/skins/... (where x = portal id). As admin you have both the host and the local to portal skins to choose from, so if you install the skin to host and portal it will appear twice.

So, either

(a) just install as host or

(b) just install as admin or

(c) name your portal skins differently eg ThisPortalsSmittySkin.zip which is redundant if they are the same skin .. see (a or b)

Regards,
Steven

Is the naming of a container skin work differently when logged in as admin of a portal vs. host?

jeewun — Tue, 04 Oct 2005 00:35:49 GMT

Hi everyone,

I have a portal. I logged in as host and gave the admin user of the portal "Skin Upload Permissions" via...
Host Settings > Advanced Settings > Other Settings > Skin Upload Permissions (I set radio button to "Portal")

As far as I understand the following steps are how a container skin can be added to an existing skin package...say the existing Skin Package name = Smitty. So while in Admin > Skins the left Skin dropdown displays the skin name Smitty, and in the right dropdown I also see the container names, Smitty.

1.) Name your .html, .xml, and .css files as follows...MyContainerName.html, MyContainerName.xml, MyContainerName.css.
2.) Zip up these three files and name the .zip file Smitty.zip
3.) Go to Admin > Skins > Upload Container
4.) Browse to and select Smitty.zip to upload....then upload it.

Now I should still see "Smitty" in both the left (skin) and right (container) drop down menus on the Admin > Skins page. When I select the Smitty container from the right dropdown I should see a new container titled MyContainerName with a preview thumbnail (if I made one). I can then select the skin and apply it.

This works fine while logged in a HOST.

However, when logged in as Admin and I try uploading the new container skin the same way, this is what happens...

A.) The right (container) dropdown menu now lists "Smitty" *twice*. The top-most Smitty will list out all the containers in the original Smitty skin package. The second Smitty will list out only the new uploaded container skin, MyContainerName.
B.) Selecting Smitty from the left (Skin) dropdown menu will only list out the orginal skins and container skins. The new MyContainerName container skin is not listed.

Why is this important? It's confusing if I have multiple Smitty's in a dropdown menu. I can work around this fine if I'm logged in as HOST, but that kinda defeats the purpose of giving admins permission to upload skins.

Any ideas? Am I doing something wrong? Thanks!
-Tim

DotNetNuke

Re: Is the naming of a container skin work differently when logged in as admin of a portal vs. host?

Is the naming of a container skin work differently when logged in as admin of a portal vs. host?