[MGNLDAM-1005] Exception when trying to open editor for content with a JCR asset Created: 17/Nov/21 Updated: 16/Feb/22 Resolved: 16/Dec/21 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Jesus Alonso |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[X] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Epic Link: | External DAM MVP |
| Sprint: | SaaS 23, AuthorX 1 |
| Story Points: | 3 |
| Description |
|
To reproduce:
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 <jcr>. 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. |
| Comments |
| Comment by Jesus Alonso [ 16/Dec/21 ] |
|
Now, assets belonging to a not existing provider should be just ignored. |