TYPO3 Core

With the normal login FORM an CSS styled content, you must set the page id in the constants field:

styles.content.loginform { # cat=content/cLogin; type=int+; label= PID of user archive: Enter the page-uid number (PID) of the sysFolder where you keep your fe_users that are supposed to login on this site. This setting is necessary, if login is going to work!
pid =

However it would be nice if also the Frontend Users from the page's record storage folder would be accepted like with the new login box extension. This only in the case when the pid is empty in the constants and setup. This should be changed for all FORMs in class.tslib_content.php.

function FORM {
....
if (is_array($conf['hiddenFields.'])) {
reset($conf['hiddenFields.']);

$hiddenfields:    <div style="display:none;"><input type="hidden" name="logintype" value="login" /><input type="hidden" name="pid" value="" /></div>

while (list($hF_key,$hF_conf) = each($conf['hiddenFields.'])) { :

$hF_conf
String (0) value
Array (2) override.
String (5) field pages
String (1) listNum 1

If the $hF_conf['value'] is unset then the pids from the page's rootline record storage folders should be inserted and also page 0 should be allowed.

This change would help a lot to users who wonder, why inserting a normal login box does not allow someone to log in. It is really very hard to find the reason for this and documentation (if there is any somewhere). A normal user thinks that a login box must allow the login of all FE users by default if nothing has been entered in the constants.

[FE][checkFeUserPid] = 0 could be set. But this is hard to find and not sufficient.

(issue imported from #M5571)