Issue Bug Closed

#107038Custom settings types are not loaded in settings editor

Benjamin Franzke 07/04/25, 11:53 updated 08/12/25, 14:35

Description

When a settings type provides a custom module name that implements the backend UI, it’s JavaScript module configuration from JavaScriptModules is not loaded in the settings editor.

    public function getJavaScriptModule(): string
    {
        return '@my/extension/settings/type/my-type.js';
    }

Either a settings.type tag should be added to be used in JavaScriptModules.php or all possible settings types shall be pre-loaded for the UI.

Reviews 3