Details
-
Bug
-
Resolution: Fixed
-
Neutral
-
1.2.0
-
None
-
None
-
Empty show more show less
-
Cloud Service 7, Cloud Service 8
-
8
Description
Steps to reproduce
- In a content app, with an asset field
- Create a content using an asset in S3 that is in a folder
- Rename in assets app the folder that contains the asset
- Open the content with the asset
.. Logs, screenshots, gifs...
Expected results
When I open the content, I can see the asset without errors
Actual results
Like the asset has another key, there is an error (software.amazon.awssdk.services.s3.model.NoSuchKeyException) and the asset is not available in the content
Workaround
Development notes
Maybe the problem can also happen when you rename the asset the same way that renaming the folder.
Checklists
Acceptance criteria
Attachments
Issue Links
- is related to
-
EXTDAM-267 Clone - [S3] Renaming a S3 asset break links to that asset
-
- Closed
-
-
EXTDAM-266 Store asset information in Magnolia
-
- Closed
-