#307
- Created on2011-08-10 05:15
- Reported by
- StatusAssigned
- PriorityNormal (3)
- Assigned to-
- Milestone-
- Plan Level-
- Due Date-
user suspend - no error message
If the admin setup a suspend for a user and the user would login in, than he could see the following message only:
Taking you back to where you were....
But he don't know about the suspension. We need a messages for this.
Taking you back to where you were....
But he don't know about the suspension. We need a messages for this.
Leave a comment
The login process is handled by the core whereas the suspension is handled in profile. Therefore, core doesn't know the reason why the login failed.
The only possibility would be to change the suspension method so that the level is changed to 0 (not activated yet).
The activision key needs to be secure then so that a user cannot reactivate the account with the previous activision key.
Might be implemented in a later version
The only possibility would be to change the suspension method so that the level is changed to 0 (not activated yet).
The activision key needs to be secure then so that a user cannot reactivate the account with the previous activision key.
Might be implemented in a later version
The login process is handled by the core whereas the suspension is handled in profile. Therefore, core doesn't know the reason why the login failed.
The only possibility would be to change the suspension method so that the level is changed to 0 (not activated yet).
The activision key needs to be secure then so that a user cannot reactivate the account with the previous activision key.
Might be implemented in a later version
The only possibility would be to change the suspension method so that the level is changed to 0 (not activated yet).
The activision key needs to be secure then so that a user cannot reactivate the account with the previous activision key.
Might be implemented in a later version
The login process is handled by the core whereas the suspension is handled in profile. Therefore, core doesn't know the reason why the login failed.
The only possibility would be to change the suspension method so that the level is changed to 0 (not activated yet).
The activision key needs to be secure then so that a user cannot reactivate the account with the previous activision key.
Might be implemented in a later version
The only possibility would be to change the suspension method so that the level is changed to 0 (not activated yet).
The activision key needs to be secure then so that a user cannot reactivate the account with the previous activision key.
Might be implemented in a later version
The login process is handled by the core whereas the suspension is handled in profile. Therefore, core doesn't know the reason why the login failed.
The only possibility would be to change the suspension method so that the level is changed to 0 (not activated yet).
The activision key needs to be secure then so that a user cannot reactivate the account with the previous activision key.
Might be implemented in a later version
The only possibility would be to change the suspension method so that the level is changed to 0 (not activated yet).
The activision key needs to be secure then so that a user cannot reactivate the account with the previous activision key.
Might be implemented in a later version
Updating tickets (#253, #60, #165, #61, #62, #63, #64, #118, #120, #121, #122, #123, #124, #125, #169, #172, #177, #182, #185, #225, #234, #251, #277, #305, #307, #310, #318, #1, #2, #3, #5, #119, #126, #127, #128, #163, #164, #171, #174, #175, #183, #245, #322, #65, #153, #170, #173, #176, #180, #184, #306)
