I have built my first DNN site for a client and I need to create an account for the client that gives them some level of admin access (not a whole lot, but some ability to make changes).  What is the process for doing this?  Is there any good documentation on this or tutorials?

Thanks, Gary

rather than give your client full administrator access, you can  gives them access to edit a page and all of the modules on the page or just a module within a page.

To learn more about this check out these tutorials:

• How to Assign a Security Role to a User Account
• Assigning Security Roles to Pages and Modules

Depending on your level of expertise you may also want to look at:

• DotNetNuke Users & Setting the Registration Options
• Working with DotNetNuke Security Roles
• User Accounts: Adding, Editing, Viewing, Deleting

 

Thank you, Lee.  I will review those tutorials.

Gary

Lee,

I went through the tutorials and they were very helpful. I created a role for the client, added the client account to the role & then set certain content modules so that this role could edit them.

However, this brought up another question. I have the module containers turned off on this site as I think it looks better for the visitor without the module containers displayed. You can view the site at www.landairsurveying.com. Of course when I login and admin, I see the containers. However, when I log into the client account the containers don't show and it is not obvious how to edit the content. These are all text/html modules and I am not even sure how to bring up the wysiwyg editor. Is there any way to turn the containers on for this client account/role?

Thanks, Gary

It may be easier to use a transparent container which will display a menu at the top of it.

I have included transparent containers in all of the skins that are available on DNN creative:

• Simple Red Leaf

• Andreas 01
• Andreas 09
• Summer Breeze
• FreeStyle
• Curiously Green
• Internet Sharing

Thanks Lee,

This site has a custom skin that I had someone else create. I can have them modify it (maybe) or learn how to modify it myself.

Are there other options?

Have a Merry Christmas.

Gary

Gary,

Upload the Andreas 01 skin to your site. Then you will have access to all of the skins and containers that it contains.

Then, specify the Transparent container for the module in question. Just that module. Then, your admin user will see the dropdown list of actions when they visit the page that contains the module.

Well, I added the Andreas 01 skin to the site (while logged in as Host). I installed without any errors. Then I logged in as Admin, went to "Site Settings" and applied the "Transparent" container just to the Admin Container (as a test). Then the trouble started. I couldn't get into any of the Admin functions without receiving a red yield symbol with an exclamation point and one of the following error messages:

An error has occurred.
An error has occurred.

A critical error has occurred.
Object reference not set to an instance of an object.

Since I coudn't get into Admin or Host functions to change it back, I had to FTP to the site and change the folder name for the Andreas 01 containers. Then I got into Admin and changed the container back to what it was. We are using DNN 4.04.01

Does anyone have any helpful ideas.

Thanks, Gary

This is a bug in 4.4.1 - they forgot to include some dlls in the installation. - One of them was for the DropDownActions token which is what those containers use.

You have 2 options, edit the containers to use the Solpartmenu, as the DNN-Blue containers, this is discussed here:
http://www.dnncreative.com/Forum/ta...fault.aspx

or you could fix the bug outlined in this tutorial:
How to fix the [DROPDOWNACTIONS] token bug in DotNetNuke 4.4.1

Hope this helps, thanks,

A thrid alternative would be to upgrade to a more recent version of DotNetNuke. I've got 4.6.2 on one site and 4.7.0 on another. Both are running fine.

If your current installation is running fine and it is a major production site I would just add the dlls to the site. - If you look at the Gemini checklist a lot of bugs were fixed for 4.7 when they released 4.8 so you may find that after upgrading that something stops working - if you do look into upgrading make sure you test in a localhost installation first extensively.

I have 4.7 running on www.dotnetnukepodcast.com and there are elements which have introduced bugs into previously working areas. - I think most of these have been fixed in the 4.8 version, but I would wait for a point release or 2 before upgrading to 4.8.

Thanks to both of you for the quick and helpful responses. I did upload the missing dll and the problem is resolved. You guys are great.

Thanks again, Gary