17488 Posts in 4473 Topics by 1978 members
|Go to End||Next >|
5 July 2007 at 9:48pm
OK, so I'll do that and just make sure that no one can login with an empty password (which should be already prevented by default - but I'll check that again).
I'm still waiting for the role decorator code to finish the integration in the backend. I hope to get it soon to be able to finish everything for Monday.
6 July 2007 at 1:56pm
Markus: I guess the situations I was thinking of were more along the lines of the SilverStripe forum, where anyone can register but you do need to give access.
So, for some OpenID log-in forms, it needs to have the abillity to accept unrecognised OpenID accounts, and get their profile information (Name, Email) from the OpenID provider.
The "activation link" type system does happen from time to time - mostly when you have a site containing private content that the owners want to control access to, but still let strangers request content. This is what my initial suggestion was aimed at, but is of secondary importance.
6 July 2007 at 8:18pm
Yes, for the forum module it would make sense... I you want (and you give me SVN access ) I could work on that for the second milestone..
8 July 2007 at 9:32pm
Could be a good idea. One of the things I would like to have is a more general registration system, that was used for the forum, and could be used for other sites with more custom functionality.
Perhaps having a class such as RegistrationForm, that could be placed on a page and would let people fill out their details and become a member of the site - site implementors would choose:
* the data fields that were collected
* the permissions that people have once they were given access
* the restrictions that needed to be met to get that access (nothing, email validation, administrator approval).
On a particular, site, we could specify that such a registration form was available, and this could then suggest that failed log-ins (both standard and openid) go to the register page to sign up for an account.
Markus - does this sound like a good way to approach this problem?
9 July 2007 at 9:11pm Last edited: 9 July 2007 9:12pm
That sounds good
The only thing I would change (or maybe just clarify):
> * the permissions that people have once they were given access
I would say the easiest thing would be to specify the group to which all the new members should be assigned automatically.
In that way it is easy to get an overview of that kind of members or to modify their permissions.
Core Development Team
9 July 2007 at 11:32pm
Markus, svn readonly to forum shall be ready fairly soon (trac/svn are not easy to set up all sorts of varied rights to) so you won't have to wait too long...
11 July 2007 at 8:32pm
No.. unfortunately I still don't have access...
Core Development Team
11 July 2007 at 11:17pm
I know hayden is working on this now as he's deliberating over svnserve vs apache access, so shouldn't need to hold your breath too much longer ;)
|Go to Top||Next >|