Problem

We are building upon a not yet officially stable API of Drupal Canvas. This is not affecting the component configurations, solely the PHP-API compatibility. The issue is mitigated by following changes in canvas-extjs and tagging new compatible releases quickly.

We do note version compatibility in composer.json, what makes sure that a compatible canvas-extjs+canvas module is installed together. However, if a new canvas module version is released and we have not yet tagged a new canvas-extjs module, sites may upgrade to canvas already and end-up in a broken state.

The broken site needs to revert the update or wait for the compatible canvas-extjs relesae to get out.

Comments

fago created an issue. See original summary.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Fixed

Actually, I think we can call this fixed. Canvas-Extjs releases declare the canvas minor versions it is compatible with, so there is no chance to accidentally upgrade canvas too early. Canvas patch releases can be applied just fine, for new minors having compatibility declarations is fine imo.

The previous upgrades went all smooth that way, so calling this 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.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.