Can't set Parameters outside the "ECA Parameters" collection

Created on 20 March 2023, almost 2 years ago
Updated 5 August 2023, over 1 year ago

Problem/Motivation

The "Get Parameter" action is able to read any parameter, no matter if it is global, or on a specific content type.
The "Set Parameter" action can however only influence the "ECA parameters" collection.
In my use case, I would need to be able to set a parameter value on a content type through ECA.

I highly appreciate the flexibility that ECA combined with parameters offers, however this feature would still be much appreciated :)

Best regards,
Daniel

💬 Support request
Status

Fixed

Version

1.0

Component

Code

Created by

🇦🇹Austria SherlockHomeless

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

Comments & Activities

  • Issue created by @SherlockHomeless
  • 🇩🇪Germany mxh Offenburg

    Could you maybe provide some details about your case, so that I'm able to understand why this would make sense?

    One key concept of Parameters is that it guarantees availability in a specific format / parameter type. Changing a parameter value on runtime could lead to unexpected consequences. When it's about something dynamic on runtime, actions like "Token: set value" provided by eca_base would be preferable. Are you using a certain type of parameter that cannot be replaced by "Token: set value"?

  • 🇩🇪Germany mxh Offenburg

    In case you need to persist a parameter value on runtime, and it's a simple parameter type (like a string or formatted text), you could also try to use "Config: write" that is provided by the eca_config module.

  • 🇩🇪Germany mxh Offenburg
  • Status changed to Fixed over 1 year ago
  • 🇩🇪Germany mxh Offenburg
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024