Problem/Motivation

When configuring fields for a content type duplication, the 'id' attribute from the configuration is missing a schema definition.

Steps to reproduce

1. Install the module.
2. Configure a few content types, add at least one field with a value different thant 'skip'.
3. Install Configuration Inspector module ( https://www.drupal.org/project/config_inspector ).
4. Go to admin/reports/config-inspector and find the content_entity_clone.bundle.settings.* rellevant configurations.
5. Enter the List link in any of them.

For each field configured, it shows "missing schema 'id' is not a supported key."

Proposed resolution

The existing configuration schema in config/schema/content_entity_clone.settings.yml does not seem to match the existing configuration created by the module. It should have a "processor" key, and then an "id" and "settings" attributes inside.

Issue fork content_entity_clone-3514273

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

guiu.rocafort.ferrer created an issue. See original summary.

guiu.rocafort.ferrer opened merge request !13

guiu.rocafort.ferrer’s picture

guiu.rocafort.ferrer
Primary language Spanish
Location Barcelona
commented

We might want to add additional validation for the ContentEntityCloneFieldProcessor plugins ( see https://www.drupal.org/node/3330852 ), but this would require to bump up the minimal Drupal version to 10.1 in the next release.

guiu.rocafort.ferrer’s picture

guiu.rocafort.ferrer
Primary language Spanish
Location Barcelona
commented
Status: Active » Needs review

orakili made their first commit to this issue’s fork.

orakili’s picture

orakili commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.