Problem/Motivation

Packages/versions

Any site that already had BPMN 2.0 was going to run into issues installing this module if it's set to BPMN 3.0, per ECA's documentation.

By downgrading the requirement of BPMN from 3.0 it 2.0 in composer.json, the ECA module has to also be 3.0, we maintain compatibility with 10 while also being compatible with 11.x.

Plugin code

Out of the box, the module also throws WSOD errors whenever an ECA model to generate ai revision logs on entity presave has been created.

We need to change the module to make sure it can run correctly when installed.

Steps to reproduce

- Set up an anECA model to generate AI revision logs on entity presave
- Set up a content type
- Create a node of the new content type
- Note the WSOD

Proposed resolution

Change composer.json from `"drupal/bpmn_io": "^3.0",` to `"drupal/bpmn_io:^2.0"`

Remaining tasks

User interface changes

API changes

Data model changes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

skyriter created an issue. See original summary.

skyriter’s picture

Title: Downgrade BPMN dependency to ^2 » Updating dependent packages and plugin to run on install
Issue summary: View changes

skyriter’s picture

Issue summary: View changes
edmund.dunn’s picture

Status: Active » Reviewed & tested by the community

This works for us.

skyriter’s picture

Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

skyriter’s picture

Version: 1.0.x-dev » 1.1.3
Status: Fixed » Closed (fixed)