By default, only Admins can drag and drop their web-parts. However if you look at sites like MyMSN or Google's portal, this is a capability available to all logged in users.

How can I modify DotNetNuke 4.0 to allow this capability without being forced to grant full Admin privlidges?

Kind Regards,

Damon

Jon,

Thanks for the response. Acrually I cannot grant everyone Admin access to the pages in question, and you are absolutely correct. I want the user's view to be persisted as 'their view' of any page.

This is quite unfortunately, given this is a user experience more and more people are expecting with the sites I mentioned (my.msn.com being perhaps the best example).

Are there any plans to add this functionality? I have a case where up to 500,000 users will be viewing a portal and this is a required feature.

Is there a way for me to allow 'Admin' type access to a user's assigned 'owned page'? All other sections would not have admin rights.

I cannot see this in the 4.x release we are running now and I don't want to diverge from the source base. Ugh... I could use the ASP.NET Portal environment I suppose but I would have to code much of what DNN gives me.

Perhaps I will have one page for each user as an IFRAME which hosts our technology.

What would you recommend? I cannot imagine I am unique in these requirements as even Google's portal supports this. Or is DotNetNuke more targeted to intranet deployment? This doesn't appear to be the case with your reference clients like Alienware..

There is always the 'SNAP' widget as well from ComponentArt a building block (for cross-browser) or the new ASP.NET 2.0 WebPart capability for this:

http://www.componentart.com/demos/snap/features/core_features/webform1.aspx

http://www.componentart.com/demos/snap/features/snap_insideSnap/WebForm1.aspx

Any help would be much appreciated.

Kind Regards,

Damon Wilder Carr, CEO and Chief Technologist
agilefactor
www.agilefactor.com

damon@agilefactor.com

Understood. Here is the requirement:

1) Each user would have the ability to create their own Pages as well as lay-out some existing pages to their liking

2) Upon each login-in this user would see their configured 'view' into the Portal

3) We would also support multiple 'views' per user and allow the user to select the desired view (and we may programmatically have algorithms for when a view is the default one automatically so it might differ upon login with no user interevention)

4) Their work should have no impact on the pages for other users, as this customization is truly 'theirs'. This is really close to what the main Consumer portal sites are now allowing.

5) Building this is obviosuly non-trivial I can see. However I have to think that with DNN we are much closer then starting from scratch.

6) Is there a way this could be added to DNN 4.0 without eliminating our ability to participate in new releases?

7) Any experts in the code-base think they can do this? By leveraging the ASP.NET 2.0 Personalization Engine, they do this with their ASP.NET base bones portal environment, which is admittadly just a sliver of DNN, but their 'Web Parts' are supporting this.

8) Perhaps this is a compromise: Is there a way to give every user a 'home' area where they at least have a single page, where worst case scenario we have an IFRAME? So every time a user registers, upon login they would see a menu link to their seperate area. I suppose if this area was hidden from all other users, they could have admin access to this page and accomplish much of this. We would like to let them create additional sub-pages off this area as well.

The only way I can envision this is to (at registration) create a security group for each user and assign view and edit provlidges only to this user 'security group'.

One way to solve this I believe is to allow security at the USER and Security Group level.

Ideas?

Thanks,

Damon