Forced entry of user data made obligatory afterwards

1 Description

Normally, user are forced to complete empty but obligatory user data fields after logging in.
Unfortunately, this does not work when a user data field is made obligatory only after the account has been created:
When the account is created, a flag is set that decides whether the user is forced into the Profile after login or not. Thus, chenages to the obligation of a user data field at a later time is not taken into account.
The reason why the user handling was designed this way up to now was because an algorithm that checks the obligatory user data fields at every login was a heavy burden on performance.

The question is: Could there be a different way to determine the need for user data field completion?
The main scenario is:

1. User accounts are imported (with data lacking the administrators actually wants to know).
2. Those data fields are made obligatory.
3. Users login and are foreced into the Profile.

2 Status

• Scheduled for Release: Not scheduled yet
• Funding: Required
• Development: Feature is to be developed by tbd

3 Additional Information

• If you want to know more about this feature, its implementation or funding, please contact: bromberger (at) qualitus.de

4 Discussion

JF 24 Jan 2011: The improvement is highly appreciated.

Zenzen, Enrico [ezenzen], 18 AUG 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

5 Follow-up