Skip to content

ElementNode is unset in fusion context #66

Description

@jakob-LIS

Some flow queries on the elementNode do not work. It appears that the elementNode is unset on reload of the node. To give an example the following throws an error when changes on the element are saved in the Neos backend:

prototype(Neos.Form.Builder:NodeBasedFormElement) {
    element {
        condition = ${q(elementNode).parents('[instanceof Neos.Form.Builder:NodeBasedForm]').find("[instanceof Neos.Form.Builder:FormElement][label='" + elementNode.properties.label + "']").is()}
    }
}

(The example above is simplified for clarity. I originally used this in a Neos.Fusion:Case)

The following error is thrown:

No operation which satisfies the runtime constraints found for "parents".

Apparently the elementNode is missing from the fusion context for the OutOfBandRendering.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions