Bug #25700: Task center - sys_action: Password should not be required when editing BE-User - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #25700

closed

Task center - sys_action: Password should not be required when editing BE-User

Added by Stephan Großberndt about 13 years ago. Updated over 5 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Miscellaneous

Target version:

Start date:

2011-04-01

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

4.5

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

When editing an BE-User via sys_action by selecting it in the create be-user action of the task center, no changes can be made without providing a password.

So if you want to change any other field and do not enter a password, you get an error: "Action error! The password is empty."

It should be possible to save the be-user without providing a password - you do not know the password of the user and do not want to reset it each time when you edit access rights, disable it etc...

When the password is empty, it should not be saved and an information message should be shown: "The password field was empty. Password has not been changed!"

This problem exists at least in 4.4.7 and 4.5.2.

Related issue: http://forge.typo3.org/issues/25329

When editing a BE-User, the usergroups the user currently belongs to are not selected. When you save without selecting the current groups (you might not know!) the user loses all groups!

Files

allow_empty_password_when_editing_beuser.patch (1.12 KB) allow_empty_password_when_editing_beuser.patch

Tobias Schmidt, 2013-09-20 12:08

Related issues 2 (0 open — 2 closed)

Actions

Copy link

Updated by Stefan Neufeind almost 13 years ago

Tested this against latest 4.5 from git.

First of all: Normal editing of users works as it should.
This ticket refers to using the sysext "sys_action". And there the "Edit record"-functionality, which can be used to edit also users, also uses the normal edit-functionality which works.
The function "create user" also works. You give it a template-user, can select a username/password and the new user is created just fine. After that however that dialog (almost the same) stays. If you you might want to change something there, you'll have to enter something into the password-field (as you also need when you use the same mask for "create user").

One solution would be to add the above mentioned check, and if action is not "NEW" an empty-pasword-field is ignored.
But how about not "doubling" functionality? Why not after creating a user just display it was created, display an edit-link and that uses "edit record"-functionality? This way you would even be able to then edit all records of the user/record and not just the limited few fields from "create user" (which is mainly targeted at creating a copy from the target-user).

Actions

Copy link