[CONTDIFF-7] Remove Bynder dependency on the module Created: 02/Jan/24  Updated: 09/Jan/24  Resolved: 09/Jan/24

Status: Closed
Project: Content Diff module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.2

Type: Task Priority: Neutral
Reporter: Cass Weber Assignee: Yen Lac Tue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 55m
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Work Started:

 Description   

Issue raised by customer, slightly modified for simplicity and clarity:

  • We have found a problem when generating and deploying the bundle with the module.
  • Origin has turned out to be a dependency on the external-dam module that we believe is not strictly necessary and, in fact, is not included by default in the DX version of Magnolia
  • From the source code of the module, and trying to eliminate dependencies that we believed were unnecessary, we have found out that both the external-dam module and others, such as Frontify, Bynder and S3 connectors, are not necessary
  • Only magnolia-ui -framework-jcr which we already included in the bundle besides Frontify-connector.
  • It would be convenient to verify our findings with your team and, if they match ours, modify the module dependencies


 Comments   
Comment by Cass Weber [ 02/Jan/24 ]

Hi yen.lactue, Kindly confirm:

Remove:

  • External DAM
  • Bynder
  • S3 

Keep:

  • magnolia-ui -framework-jcr
  • Frontify{}
Comment by Yen Lac Tue [ 03/Jan/24 ]

Hi cweber ,

I've just double check again base on this information:

  • Only magnolia-ui -framework-jcr which we already included in the bundle besides Frontify-connector.

We can modify module dependencies as below:

  Remove:

  • External DAM
  • Bynder
  • S3 
  • Frontify

  Keep:

  • magnolia-ui -framework-jcr

Thanks!

Comment by Cass Weber [ 03/Jan/24 ]

Thank you, yen.lactue!

Comment by Yen Lac Tue [ 09/Jan/24 ]

Hi cweber ,

This ticket has been fixed. Could you please let me know about the release time for this?

Thanks!

Comment by Yen Lac Tue [ 09/Jan/24 ]

This fix is going to be released within version 1.0.2

Generated at Mon Feb 12 00:13:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.