sharindenver
Posts:54
| | 01/19/2007 2:59 PM |
| Me again! :) I am planning on (at the moment) creating several child portals... one for each school. I want them to each use thier own skin. Is there a way I can prevent other skins showing up in the drop down list? Right now, as I add different skins, they all show up in the ddl for every portal. I am more concerned about containers... that is what users are likely to play around with. They don't all have the best style sense. | | | |
|
|
|
John Mitchell
Posts:3249
| | 01/19/2007 3:19 PM |
| Hi Sharlyn,
No, you can't hide the skins or containers from anyone with edit rights to the pages modules or the administrators.
It would be a fairly easy modification to hide those selections from everyone but superusers though. | | | |
|
sharindenver
Posts:54
| | 01/19/2007 3:23 PM |
| | well, the problem with hiding it completely is I have found that if we set a default container, it gets kicked off a LOT, so the editor needs to go in and "hard" set it. They wouldn't be able to do this then. It's just that now when they need to go in and do this, they have to know which one to pick and as easy as that sounds, they tend to not pay good attention! | | | |
|
John Mitchell
Posts:3249
| | 01/19/2007 3:28 PM |
|
Maybe a naming convention that put them at the top would help.
Or, you could put only the ones needed for each portal in each portal's site folder.
| | | |
|
sharindenver
Posts:54
| | 01/24/2007 2:51 PM |
| | How do I do your second suggestion? If I did that, when a user is logged in to the child portal would only the skins/containers for that portal show up? | | | |
|
John Mitchell
Posts:3249
| | 01/24/2007 3:25 PM |
|
For the naming convention suggestion, you would just name the skins or containers in a way that you could tell your admins to "only use these that start ABC_".
For the per portal one, you just need to put a "skins" and/or "containers" folder in each portal's root folder e.g. portals/1
| | | |
|
sharindenver
Posts:54
| | 01/25/2007 11:28 AM |
| ok... i am going to do this on the production box, so I want to make sure I have this right.
Do I add the folder on the server or through the file manager or does it matter? Then do I need to upload the skin again and how does it know to add it to the right place? How do I take it out of the main portal folder? Can I do all of this just on the server? the child portal is not live so it doesn't matter... and the parent portal is not accessing this skin so it shouldn't effect what is live. As long as this won't bring down the whole server or something!
SO... can I do the following:
create a skin folder in the child portal directory
cut and paste the skin files from the parent portal (_default folder) to the child portal (2)
go to the child portal and will I need to repoint the pages to the skin since it is in a new location? | | | |
|
John Mitchell
Posts:3249
| | 01/25/2007 2:11 PM |
| Posted By sharindenver on 01/25/2007 11:28 AM
SO... can I do the following:
create a skin folder in the child portal directory
cut and paste the skin files from the parent portal (_default folder) to the child portal (2)
go to the child portal and will I need to repoint the pages to the skin since it is in a new location?
That is correct.
When you are assigning skins there are two radio buttons, one for host which looks in the /portals/_default/skins folder, and one for site which looks in the /portals/nn/skins folder. And the same thing for containers. You can do it all directly on the server as those drop-down lists are populated each time you go to the settings page. | | | |
|
sharindenver
Posts:54
| | 01/25/2007 2:32 PM |
| | ohhhhhh... that's what those radio buttons mean and why when I select site it is empty! :) Cool! I will post back once I do this. | | | |
|
sharindenver
Posts:54
| | 01/25/2007 2:39 PM |
| | worked great! Thank you!!!!!!!! | | | |
|
sharindenver
Posts:54
| | 01/25/2007 2:49 PM |
| | when adding a new page, is there a way on child portals I can have the site radio button be the default selection instead of host? | | | |
|
John Mitchell
Posts:3249
| | 01/25/2007 2:55 PM |
|
No, not without changing the core code.
| | | |
|
sharindenver
Posts:54
| | 01/25/2007 3:51 PM |
| | i don't mind changing the core code... I just have to have a log of code I change so I know to make the changes when I upgrade. I'm assuming the change would be minimal? | | | |
|
John Mitchell
Posts:3249
| | 01/25/2007 5:05 PM |
| It should not be hard, let me find out where to change it at so you don't need to recompile and I'll post it back here.
| | | |
|
sharindenver
Posts:54
| | 02/02/2007 9:39 AM |
| | Hi John, Did you happen to find where I can change the default for child portals to be site instead of host for skins and containers? Thanks! (looks like the board is picking up a little!) | | | |
|
SplatMan_DK
Posts:81
| | 02/02/2007 9:51 AM |
| Why dont you just copy the skin for each school directly to their portals "Skins" folder, so that it is the only skin they can select by default? If they want other skins they would then have to upload them - and they would always only have access to their own skins?
- Jesper | |
brgds
- Jesper | |
|
sharindenver
Posts:54
| | 02/02/2007 9:58 AM |
| I think that is what I did. I have a child portal and have that portal's skin uploaded. It is the default and so when new pages are created, it is already there. Technically, no one should ever even want to go change this.
Here is my problem... on the parent portal as well as the child portals, the default skin sometimes gets "kicked off" when saving. So when you go into page settings and look at what the skin is, it has Not Selected. If I "hard select" the skin I want, it never gets kicked off. So I have told users they can do one of two things... wait for the default skin to get kicked off, then go in and hard select (this is where they seem to have trouble selecting the correct one when host is the default list instead of site), or hard set it when you initially create the page (again, would like site as the default instead of host so they only get their skins and containers to choose from).
So... any thoughts as to why the default gets kicked off? :) or how to make site the default selection on the child portals only? | | | |
|
SplatMan_DK
Posts:81
| | 02/02/2007 10:17 AM |
| Aaaah, now I understand you better.
I have not experienced that the skins get "kicked off" on child portals - but I admit that I only have 3 of them, and they have vurtually no traffic.
Beeing a DNN newbee, but somewhat more experienced with databases, I would probably consider writing a trigger somewhere in the SQL DB that would force the correct foreignkey value for your portals - but please note that its probably VERY far from a "best practice" solution 
- Jesper | |
brgds
- Jesper | |
|
John Mitchell
Posts:3249
| | 02/02/2007 5:46 PM |
|
This actually turns out to be easier than I thought.
Look for the file \controls\skincontrols.ascx and open it with an editor.
Inside that file search for "Checked".
You will first find it on the Host radio button where it is set to "True", set that one to "False" and find the next one on the Site radio button, change that one to "True".
Save the file, and you are done. | | | |
|
sharindenver
Posts:54
| | 02/05/2007 11:10 AM |
| | i'm thinking this will make the change on the parent portal as well right? is there a way i can code in there to only do this for child portals? or is there a way for the parent portal skins to show up in the site ddl? | | | |
|