i'd like to put two diffrent menues at the same page. diffenet content and design.
every solpart menu automaticaly reciviece the ALL the current pages in system. but i want one menu to lead some pages, and the other to different pages. is it possible?

another question:
is it possible to enable the portal admin to change only the content of the moduls (i.e text in text editor) and disable all the other editing option such as upload different skins and changing the page structure (i.e. add/remove panes, locations of studd, etc)?

please let me knoiw how..
thanks,
Hadar

Hello,

You can add a second Solpart menu to the page using the token:

[SOLPARTMENU:2] within the setup for the menu - ie. in the skin.xml file for this token you can then specify the CSS class to use for styling this menu and further options such as which elements to display. - All of these configuration options are in the skinning documentation that you can download from the main dotnetnuke website.

For the admin - yes this is possible and it is covered in these tutorials from issue 1:

Administrators:
Security Roles, Users and Pages (Videos totalling 34 mins) 

DNN Users & Setting the Registration Options

Specifying Required Fields Upon Registration

User Accounts: Adding / Editing / Deleting / Viewing

Working with Security Roles

Assigning a security role to a user account

Basic Introduction to working with pages

Assigning Security Roles to Pages & Modules

Basically you setup a security role such as 'adminedit' and you then assign this security role to the modules that you wish a user to be able to edit. - Once you have done this, assign the 'adminedit' role to the user accounts you wish to have access to edit your module. - These users will not have access to the admin menu but will have access to edit the module(s) that you specify.

This is explained in detail step by step in the tutorials above.

Thanks,

Thanks Lee. the videos so far (Mainly skinning) were very helpful.

Hello,

No problem, glad you have found them useful. - Just noticed the post looking for good DNN skin designs in the main DNN forum. -  Yes the DNN Creative skin needs a big overhaul I agree! - I'm looking to create a new pure CSS skin which implements all of the practices that I have demonstrated in the video tutorials so hopefully in a couple of months or so there will be a decent CSS skin on the site. - Happy Skinning! - Thanks, Lee

Thanks Lee.
Another question:

Is there a way to directly upload skin.htm, instead of installing it thorugh the 'install' folder, and then the install link ? not to mention its a a full zip file to upload every time i make a small change.

I'm working with FTP access and i'd like to know if its possible. Also, what are the risks if i upload "wrong" skin (unclosed tags, etc.).

Yes there is, have a look at this tutorial which explains how to install a skin via FTP.
http://www.dnncreative.com/tabid/21...fault.aspx

Check video 3

It demos it in a localhost installation, but this is identical to FTPing to a live website.

You also have the option of editing the .ascx file direct rather than the html and skin.xml files combined. There is an explanation of this in: Introduction to Skinning

If you make a mistake with the skin and it causes errors in your installation, all you have to do is delete the skin from your install (you will probably have to do it via FTP) and DNN will automatically resort to the DNN Blue skin.

Hope this helps, thanks,

In video 3 it is still required to zip the folder and go to the install link. Suppose i install a skin once, and then wants to update the files inside it. is it possible to directly upload the relevant files, without zipping and using the installing url again?

About security Roles:
when i try to set a user i defined to be able to edit a text editor module, this user (actually me..) login the page and cannot see or edit any of the text i enterd as admin. its only for the text module; i also permitted this user to edit the iframe module, which works well.

BTW lee, do you prefer i'll post a new topic for every question, or to keep discussing for now in this one?

Hello,

Skins: If you don't want to upload the zip the other option is to edit the .ascx file direct. - I use this method for making quick edits and it allows you to edit the live files without re-uploading the entire skin.

Just make sure that you transfer back to your local computer the changes that you have made, - I've occassionally made that mistake and then lost some of the work I have done.

Security Roles: Have you just set up the module to be viewed by administrator? - You need to set the module to 'View' and 'Edit' permissions for your new security role. This should allow the person to view the module and edit its content

- For different questions I would prefer you to post a new topic as it will be clearer for the other users searching around the forum.

Thanks,

ok then. so i'll keep this discussion here and post new questions in new threads.

i did set to the new user i created to view and edit the text module. still i can only see the module (thorugh the new user account) without text inside, of course without ability ti change anything (i tried the moudle corenerd menu button, it just offers help and help online).

I still couldn't find a way to STYLE two menus at the same page. so i call [solpartmenu:1] and [solpartmenu:2], and i can design a little of it in the XML, but i want totaly different CSS styles to both. what's the trick ?

You need to specify a new CSS class for each of the elements within the Solpart 2 XML section:

<Token>[SOLPARTMENU:2]</Token>
        <Settings>
            <Setting>
                <Name>seperatecss</Name>
                <Value>True</Value>
            </Setting>
            <Setting>
                <Name>menucontainercssclass</Name>
                <Value>menucontainercssclass2</Value>
            </Setting>
            <Setting>
                <Name>menubarcssclass</Name>
                <Value>menubarcssclass2</Value>
            </Setting>
etc.

So here instead of styling the menucontainerclass, for the Solpartmenu2 we will style the menucontainercssclass2 class in the skin.css file.

Of course, you can name these classes to any name you wish.

You will see each of the settings for the classes starting from page 48 in the skinning docs that come with DNN.