TYPO3 Core

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 @Torben Hansen 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).