Allow different default status configurable per-plugin

Created on 1 August 2025, 2 months ago

Problem/Motivation

Some projects might need to set the status as published, others as unpublished, when a source string is discovered. It would be nice to be configured per-plugin.

Proposed resolution

  • Make TranslationTypePluginInterface extend also PluginFormInterface
  • MenuLinkContent plugin doesn't need to extend PluginFormInterface anymore
  • The translation_type_default schema definition should add a new mapping entry: default_status of type boolean.
  • Implement methods from PluginFormInterface into TranslationTypePluginBase
  • In TranslationTypePluginBase::submitConfigurationForm() add a new checkbox element "default_status"
  • In submit handler store the submitted value in configuration (see the "menu_link_content" plugin for an example)
  • Update MenuLinkContent::submitConfigurationForm() to call also the parent
  • In Joinup config, make plugin "config" default status to TRUE and "locale" plugin default status to FALSE.

Remaining tasks

None.

User interface changes

None.

API changes

None.

Data model changes

New default_status configuration for all plugins.

Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇷🇴Romania claudiu.cristea Arad 🇷🇴

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024