Debug message clarification: Appliance check for event eca.form.build defined by ECA ID process_ID resulted to not apply, successors will not be executed

Created on 22 February 2025, 8 days ago

Problem/Motivation

I have the ECA log switched on during development, and I noticed that if any of the models I created use a Build form event, the log gets filled up with long lists of this message: "Appliance check for event eca.form.build defined by ECA ID process_ID resulted to not apply, successors will not be executed."

I wonder whether I am doing something wrongly, or what other reasons evoke this debug message. Also, because the same message is generated several dozens of times, i wonder if the Build form ECA event results in any performance penalty.

💬 Support request
Status

Active

Version

2.1

Component

Documentation

Created by

🇮🇪Ireland marksmith

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

Comments & Activities

  • Issue created by @marksmith
  • 🇩🇪Germany jurgenhaas Gottmadingen

    First of all, a performance penalty is not an issue. ECA stores the list of subscribed events from your active models in Drupal's state. This list is stored together with arguments to determine if an event applies or not. For that reason, it's very lightweight to determine if an event applies or not. That doesn't require any significant compute power.

    To determine, how often that assertion needs to be tested is the product of that event being dispatched by Drupal and the number of events being used in your active models. Let's say, that event is dispatched twice on a page, e.g. from the search form and a newsletter subscription, and you have 5 different events in your models for the form build, you would then see this assertion 2*5 = 10 times in the debug log.

  • 🇮🇪Ireland marksmith

    Understood, thank you.

  • 🇩🇪Germany jurgenhaas Gottmadingen
Production build 0.71.5 2024