Contrib.social

Schema errors for eca.eca.eca_lib_0028

Open on Drupal.org →
Created on 1 August 2025, 1 day ago

Problem/Motivation

When installing/applying an ECA recipe e.g. drush recipe ../recipes/eca_lib_0028, schema warning are displaid in the terminal output:

0/2 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░]
Applying recipe
 [warning] Schema errors for eca.eca.eca_lib_0028 with the following errors: eca.eca.eca_lib_0028:events.Event_0zx0bxh.configuration.form_id missing schema. These errors mean there is configuration that does not comply with its schema. This is not a fatal error, but it is recommended to fix these issues. For more information on configuration schemas, check out <a href="https://www.drupal.org/docs/drupal-apis/configuration-api/configuration-schemametadata">the documentation</a>.
 [warning] No schema for eca.model.eca_lib_0028. These errors mean there is configuration that does not comply with its schema. This is not a fatal error, but it is re2/2 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓]
Applied Access to form fields with tokens recipe.

When going to admin/config/workflow/eca, the imported model has no name in the list. In the model edit form, the model name is displayed as ECA Model: undefined.

This looks to be an consequence of the major rewrite in 3.x. Not sure if there's an easy way to update recipes to be compatible with 3.x ?

Steps to reproduce

  • composer require drupal-eca-recipe/eca_lib_0028
  • drush recipe ../recipes/eca_lib_0028
  • drush cr
  • Go to admin/config/workflow/eca
  • Click Edit
🐛 Bug report
Status

Active

Version

3.0

Component

Code

Created by

🇨🇦Canada bisonbleu

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

Comments & Activities

  • Issue created by @bisonbleu
  • Comment about 20 hours ago →
    🇩🇪Germany jurgenhaas Gottmadingen

    Well, this is a challenge now:

    The format of the config entities has changed, and also some config keys have changed. Looks like for a while we have to provide all the samples in two flavours, one for ECA 2 and a new one for ECA 3.

    With recipes, we can achieve that with versioning, so that their composer requirements rely on different ECA versions, and therefore composer will then always load the correct one.

    As for the archives in the ECA Guide, this won't be possible the same way. For that, I wonder if we should just remove them and let people only use recipes? That would it make much easier for to maintain, and the usage should also be far less error-prone.

    What do you think?

  • Comment about 19 hours ago →
    🇨🇦Canada bisonbleu

    I agree, removing the archives (the Download links) makes sense.
    A «composable» paradigm, we now live in… ;^)

  • Comment about 18 hours ago →
    🇩🇪Germany jurgenhaas Gottmadingen
  • Comment about 16 hours ago →
    System Message
    • jurgenhaas → committed 2e8ff2b0 on 3.0.x 
      Issue #3539206 by bisonbleu, jurgenhaas: Update sample models in the ECA...
  • Comment about 15 hours ago →
    System Message
    • jurgenhaas → committed cc58d46a on 3.0.x 
      Issue #3539206 by bisonbleu, jurgenhaas: Update sample models in the ECA...
  • Comment about 11 hours ago →
    🇨🇦Canada bisonbleu

    I tested the recipe for «Access to form fields with tokens» (eca_lib_0029). The good news is that the schema warnings are gone. But I see 2 remaining issues:

    FIRST ISSUE
    In the ECA Library, the first command is incorrect:

    ## Import recipe
composer require drupal/eca_lib_0029

    This is the correct command:

    ## Import recipe
composer require drupal-eca-recipe/eca_lib_0029

    SECOND ISSUE
    There is an issue with the property panel.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024