Skip to content
This repository has been archived by the owner on Jul 3, 2020. It is now read-only.

Configuration of required attributes for registration #67

Open
tkrille opened this issue Oct 15, 2014 · 2 comments
Open

Configuration of required attributes for registration #67

tkrille opened this issue Oct 15, 2014 · 2 comments
Assignees
Labels
Milestone

Comments

@tkrille
Copy link
Member

tkrille commented Oct 15, 2014

At this time one can only configure what fields show up on the registration page. Which fields are required or not is statically implemented and so cannot be changed by a deployer/operator. I think we should make it possible for a deployer/operator to define which fields are required or not. @dacrome already made up an example how to specify that in the properties file: https://gist.github.com/dacrome/31edbb3b9e894258e937

@dacrome
Copy link
Member

dacrome commented May 18, 2015

I think we need a custom validator to handle all fields of the user

@dacrome
Copy link
Member

dacrome commented Sep 26, 2015

@tkrille which fields are required is changeable by deployer/operator via the templates, by just setting the last parameter to true/false. But for sure it is way easier to do this by configuration. I think this is a low hanging fruit, because everything is prepared to fulfill this feature.

@dacrome dacrome assigned ghost , khapke and dacrome and unassigned ghost and khapke Oct 4, 2015
@dacrome dacrome mentioned this issue Oct 12, 2015
48 tasks
@tkrille tkrille added this to the v2.0 milestone Oct 17, 2015
@tkrille tkrille modified the milestones: v1.8, v1.9 Dec 27, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants