Last post May 08, 2006 09:40 AM by kennsterdude
Feb 01, 2006 04:46 PM|HSLDAWebmaster|LINK
Where do I start. Any good docs or pointers.
What's coming down the pipe that I should be aware of so I don't spend time on something that will be obsolete soon.
The provider is to work in concunction with a SQL based membership database called Raiser's Edge if anyone cares.
Feb 02, 2006 11:12 PM|thecrispy1|LINK
I don't know anything about Raiser's Edge but...
The next DNN Version has a rewrite or the core implementation of the 3 providers. This includes Membership, Profile, Roles. We are look at making this more flexible and more to a standard provider model. Currently, any provider would fall short because
the core currently is restrictive in its implementation of the MemberRole.dll.
I am not sure of your time constraints but I would hold off on this if possible.
Feb 02, 2006 11:57 PM|christoc|LINK
Feb 07, 2006 12:56 PM|HSLDAWebmaster|LINK
Feb 07, 2006 07:11 PM|thecrispy1|LINK
We never announce a date. I can say it will be in the next version.
Feb 08, 2006 01:20 AM|IndianGuru|LINK
... and when is the next version [;)]
Also, I guess, the next version(s) would be on both, DNN 3 (ASP.NET 1.1) as well 4 (ASP.NET 2) [:P]
Feb 17, 2006 03:24 PM|jbeall|LINK
Feb 17, 2006 09:34 PM|netguy|LINK
I understand why no dates being disclosed.
What would be nice, however, is to have some document outlining what is coming in the next version of the 3 providers in question.
(Maybe there is one and I do not know about ???)
Mar 02, 2006 12:52 PM|jbeall|LINK
Mar 02, 2006 07:06 PM|JMyung|LINK
The new provider thing in the next version of DNN - are you going to use storage in DB like the current one blob thing or something more usefull for reporting like the
ASP.NET 2.0 SQL Table Profile Provider Released Today
I agree that we shouldn't push any times from Core Team but it will be usefull to know if we are talk in a granularity of weeks, months or years. I can't wait for this since the membership limitations are the worst part on DNN for me
Mar 02, 2006 10:03 PM|cnurse|LINK
Mar 03, 2006 08:50 AM|jbeall|LINK
Mar 03, 2006 11:46 AM|jbeall|LINK
Mar 03, 2006 11:54 AM|cnurse|LINK
Mar 03, 2006 12:09 PM|jbeall|LINK
May 08, 2006 09:40 AM|kennsterdude|LINK
I think I asked this elsewhere, but best I can tell, this is the best thread to place this question/comment:
Since 3.x has been out, I have been frustrated by the fact that it no longer supported the ability to have a single user base across all portals. For sites such as Churches, Educational Institutions, Businesses, which need to have a single user base and
multiple sub-portals, 3.x simply isn't viable as it requires a user account to exist separately in each portal it exists within.
This has been argued time and time again in the forums, but this solution is not practical for schools or churches which may wish to have many subportals for different classes, teachers, students, committees, etc, all of which worked very nicely on DNN 2.1.2
(which I still implement for this purpose today). It would be so great to have the ability to sell to a client again the ability to set up a master public or private facing site, and add it's users to departmental or committee roles, and then give each committee,
department, class admin access over their own section of the public facing site and subportal. I even wrote a handy little 'my portals' module which looked up the user's portal membership, and other portals who's keywords included 'open-enroll,' which enabled
the users to automatically be added to that sub-portal's registered users role prior to being redirected to that sub-portal. All of this continues to work wonderfully in DNN 2.1.2, and it would be great to be able to do this in 3.3, without having to manage
thousands of identical accounts.
Regardless, than you for your hard work and continuing efforts, and from what I have read between your posts and S.B.'s blog, I think the 3.3 version may support these use cases.