On a different page, let's say MyTest, add a diagram macro that displays Diagram1 with the cached option checked (it will use the diagram svg when displaying)
Install Diagram Application (Pro), using a version >= 1.11 (let's say 1.12)
Go to MyTest and observe the diagram included using the diagram macro
At this point the problem continues to reproduce, meaning that the migration is not applied.
The migration is working well if the paid application was installed from the start
Workarounds:
Use the diagram macro without the cached option checked
Resave Diagram1 (since this will generate the needed attachments)
Note that this will impact the XWiki PDF export export as well (or any other feature that relies on the diagram svg)
Starting with version 1.11, the diagram svg is not anymore stored inside a page object, but as an attachment, see https://github.com/xwikisas/application-diagram/issues/84#issuecomment-555078670 When upgrading from a version that used the old storage, a migration should be triggered to move the svg to the attachments.
Steps to reproduce the issue:
Expected result: The diagram it is displayed.
Actual result: The diagram it's not displayed anymore while the cached option checked.
Note: This behavior is caused by the fact that the applied migration only listens to the upgrade event (see https://github.com/xwikisas/application-diagram/blob/master/application-diagram-api/src/main/java/com/xwiki/diagram/internal/DiagramApplicationListener.java#L68), while above an install event was actually fired (the free and the paid version are 2 separate application). So I continued with:
At this point the problem continues to reproduce, meaning that the migration is not applied. The migration is working well if the paid application was installed from the start
Workarounds:
Note that this will impact the XWiki PDF export export as well (or any other feature that relies on the diagram svg)