Issue Task New Orphaned

#105269Consider to change TypoScript configuration in ext:felogin

Torben Hansen 10/11/24, 06:39 updated 10/14/24, 05:27

Description

ext:felogin uses a plugin specific TypoScript configuration by default plugin.tx_felogin_login. This makes it impossible to override plugin settings, when the felogin plugin is includes via TypoScript (USER or EXTBASEPLUGIN), since extbase configurationManager always prefers plugin specific configuration and thereby overrides possible configuration defined in USER or EXTBASEPLUGIN.

It should therefore be considered to rename the TypoScript configuration to plugin.tx_felogin in TYPO3 v14 as a breaking change

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[TASK] Consider to change TypoScript configuration in ext:felogin Resolves: #105269 Releases: main

History 4

  1. Torben Hansen changed Related to #105256 10/11/24, 06:39

  2. Torben Hansen changed category 10/11/24, 06:56

  3. Garvin Hicking changed Tags breaking 10/11/24, 07:15

  4. Tobias Jungmann commented 10/14/24, 05:27

    I thought about it a while and in my opinion this is not the best solution.

    Imagine having 2 plugins instead of only one in the felogin extension. You then wouldn’t want to define the settings in tx_felogin because the two extensions have different settings configuration and you maybe want to define settings.pages differently for each plugin.

    In that case you would have to define the settings for tx_felogin_login and tx_felogin_newplugin. But that again would lead to the problem, that USER or EXTBASEPLUGIN or FlexForms configuration would be overriden by those settings. To achieve the flexebility (that was given until v12), you would have to add an extension per plugin.

    Which leads as back to #105256, where @derhansen mentioned:
    > Changing extbase configuration manager is no option here

    But I really think, It should be an option. As a developer i’ts not logical, that a less specific configuration (e.g. tx_felogin_login) overrides a more specific configuration (e.g. EXTBASEPLUGIN, the concrete plugin configuration; FlexForms).