-
Bug
-
Resolution: Obsolete
-
Neutral
-
None
-
1.0.6
-
None
Steps to reproduce
- In a page in pages app, use a S3 asset
- Rename that asset in S3 subapp
- Open the page with the previous S3 asset
.. Logs, screenshots, gifs...
Expected results
When I open the page, I can see the asset
Actual results
Image not shown and there is an error in console:
Caused by: software.amazon.awssdk.services.s3.model.NoSuchKeyException: The specified key does not exist. (Service: S3, Status Code: 404, Request ID: 7P0VC0Z43N5MN5WT, Extended Request ID: 40yw44lR0b1gbK+b4+CjPW5RRk2g8Cjvj10a9+UiNtiNtfm2lZYnprLx32LXNtr0ePWAUIouCkk=)
Workaround
Development notes
It happens renaming the asset, or editing it and change the name
- Find the new way to map the S3 asset, which allow to rename on S3 asset app, meanwhile doesnt break the link to the asset
- Ask Jesus for his idea
Acceptance criteria
- depends upon
-
EXTDAM-266 Store asset information in Magnolia
- Closed