BPMN Modeler FAQ¶
This page collects answers to common questions raised in the BPMN.iO support issue queue. Each entry links back to the original discussion for full context.
How do I upgrade from BPMN.iO 2.x to 3.x?¶
BPMN.iO 3.x depends on ECA 3.x. Upgrading the modeler without upgrading ECA will cause a fatal error:
1 | |
Always upgrade ECA and BPMN.iO together and follow Upgrading from ECA 2 to ECA 3.
The ECA update scripts install the Modeler API and migrate your models, but two
steps are yours. On the direct route to ECA 3.1 you have to uninstall
eca_modeller_bpmn while the site still runs ECA 2, because that release no
longer contains its code and no update hook gets the chance to run. BPMN.iO
depends on that sub-module in version 2.x, so it goes down with it, and you have
to enable bpmn_io again before you run the database updates so the migration
can read your diagrams.
Original discussion (d.o #3571323)
The status message overlaps the modeler UI in Claro¶
When using the Claro admin theme, the "Model saved" status message may appear in the centre of the screen, cannot be dismissed, and never disappears. This is caused by a CSS selector mismatch: the bpmn_io JavaScript that makes messages dismissible uses a selector that does not match Claro's message markup.
Solution: Switch to the Gin admin theme, where message handling is already optimized. Claro is being deprecated in Drupal core in favor of Gin.