Condition plugins should not rely on the existance of the token named "entity"

Issue information

From user: jurgenhaas

Related to !105 (merged)

Contribution record

Fork management

Problem/Motivation

All conditions in the sub-module eca_content use $entity = $this->getContextValue('entity'); at the beginning of their evaluate method. If that context isn't available, this throws an exception and produces a WSOD.

That happens e.g. if the triggering event is not entity related, then the token "entity" is not defined and the context won't be available, unless the model puts another entity onto the token stack, but then the conditions need to refer to the name of that token.

Proposed resolution

The exception needs to be caught and the evaluate methods then must respond FALSE.

Edited by drupalbot
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information