Project

General

Profile

Actions
Copy link

Bug #105903

open

FE Login Template Paths from settings ignored

Added by Lina Wolf 3 months ago. Updated 2 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
felogin
Target version:
-
Start date:
2025-01-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When the TypoScript constants for templates are not set but the site settings are set, the empty constants overrule the settings from the site set.

While the site set itself does not load the TypoScript constants, in EXT:fe_login/ext_localconf.php they are forcefully loaded so they are always an empty string.


Files

Download all files
clipboard-202501090949-rqvlm.png (27.5 KB) clipboard-202501090949-rqvlm.png Lina Wolf, 2025-01-09 08:49
clipboard-202501090951-liph3.png (14.7 KB) clipboard-202501090951-liph3.png Lina Wolf, 2025-01-09 08:51
Actions
Copy link
 #1

Updated by Lina Wolf 2 months ago

Ok, this bug is actually quite interesting. I still had a root TypoScript record, however that record was hidden. As long as I still have the hidden TypoScript Record,

$GLOBALS['TYPO3_CONF_VARS']['FE']['defaultTypoScript_constants'], which containts the felogin constants is loaded! As soon as I delete the hidden record it is not loaded anymore.

Actions
Copy link
 #2

Updated by Benjamin Franzke 2 months ago

Note for myself:

styles.content.loginform.email.layoutRootPath is defined to be an empty string by typo3/sysext/felogin/Configuration/TypoScript/constants.typoscript and therefore null coalesce does not work if felogin is loaded via TypoScript sys_template record and via site sets.

Possible "solutioin" 

layoutRootPaths {
  20 = {$styles.content.loginform.email.layoutRootPath ?? ''}
  21 = {$felogin.email.layoutRootPath ?? ''}
}

Actions
Copy link

Also available in: Atom PDF