Issue Bug New Orphaned

#69818ExtensionService - getPluginNamespace should have signalSlot to build (not only set via TypoScript) own pluginnamespace

Andreas Allacher 09/15/15, 12:33 updated 01/25/26, 12:58

Description

Sometimes it would be good to be able to override the pluginnamespace more dynamically then just using the TypoScript setting allows.
For instance appending a Input-Fieldnmae of the content element or the UID.

The reason is if you intend to create a plugin that can/should be used multiple times on the same site the pluginNamespace defines which plugin is actually involved.
As the ExtensionService itself is injected in quite a lot of classes it is a bit complicated to get the change to work everywhere.

The easist solution would add a signalSlot that allows to modify the default pluginnamespace.

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
[BUGFIX] ExtensionService - getPluginNamespace should have signalSlot to build (not only set via TypoScript) own pluginnamespace Resolves: #69818 Releases: main