Uploaded image for project: 'Magnolia DAM Module'
  1. Magnolia DAM Module
  2. MGNLDAM-1005

Exception when trying to open editor for content with a JCR asset

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 3.1.0
    • None
    • None
    • None

    Description

      To reproduce:

      • Create a contenttype and content app which have an asset..
      • Run on local magnolia instance and create a content item which links to a JCR asset.
      • Export content item to YAML
      • Import content item to SaaS instance with same contenttype and content app.
      • Open content item.

      Expected:

      View and edit content item.

      Actual:

      Get exception, cannot edit item.

       

      Use this contenttype...

      // contentTypes/activity.yaml
      datasource:
        workspace: activities
        autoCreate: true
      model:
        nodeType: activity
        properties:
          name:
            label: Name
            i18n: true
            required: true
          description:
            type: richText
            label: Description
            i18n: true
            required: false
          image:
            type: asset 

      Exception

      Message: No AssetProvider with id &lt;jcr&gt;. Stack trace: info.magnolia.dam.api.AssetProviderRegistry$NoSuchAssetProviderException: No AssetProvider with id <jcr>	at info.magnolia.dam.core.AssetProviderRegistryImpl.getProviderById(AssetProviderRegistryImpl.java:83)	at info.magnolia.dam.core.AssetProviderRegistryImpl.getProviderFor(AssetProviderRegistryImpl.java:88)	at info.magnolia.dam.app.data.AssetConverter.convertToPresentation(AssetConverter.java:81)	at info.magnolia.dam.app.data.AssetConverter.convertToPresentation(AssetConverter.java:51)	at com.vaadin.data.Converter$2.convertToPresentation(Converter.java:173)	at com.vaadin.data.Converter$2.convertToPresentation(Converter.java:174)	at com.vaadin.data.Binder$BindingImpl.convertToFieldType(Binder.java:1274) 

       

       

      Context

      This is very problematic for people trying to use or migrate to SaaS. They cannot bring over any of the their content which has links to images. This makes it hhard for them to test it..

      Of course bigger picture we'd like to provide a way that they can migrate asset content, but in the short term, without that, this can be a blocker in and of itself.

      WOrkarounds would be by hand or a tool to edit the YAML files to remove or rename all of the asset references.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                jalonso Jesus Alonso
                czimmermann Christopher Zimmermann
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD