[MGNLDAM-973] DOC: Document alternative ways of renaming asset files Created: 07/Jun/21  Updated: 18/Jun/21  Resolved: 18/Jun/21

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Federico Grilli Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2021-06-18-09-58-02-359.png     PNG File image-2021-06-18-10-01-52-114.png     PNG File image-2021-06-18-10-02-49-415.png     PNG File image-2021-06-18-10-05-43-851.png     PNG File image-2021-06-18-10-06-05-277.png     PNG File image-2021-06-18-10-08-30-575.png     PNG File image-2021-06-18-10-09-00-005.png     PNG File image-2021-06-18-11-19-57-515.png     PNG File image-2021-06-18-11-22-22-090.png     PNG File image-2021-06-18-11-28-19-296.png    
Issue Links:
documentation
documents MGNLDAM-951 Asset Filename cannot be renamed Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Sprint: Content Mngmt 6
Story Points: 1

 Description   

See the workaround paragraph at MGNLDAM-951 description



 Comments   
Comment by Martin Drápela [ 18/Jun/21 ]

Observations from the hotfix solution.

1) hotfixing: /dam-app-jcr/dialogs/uploadAndEdit.yaml

    jcr:content:
      $type: compositeField
      itemProvider:
        $type: jcrChildNodeProvider
      properties:
        fileName:
          $type: textField
          label: ""
      label: Filename
here

and touching a file in the dam-app-core (for example /dam-app-core/apps/dam.yaml)

adds the field to the dialog:

Initially, the

Name shown after upload will be "jcr:content.".

The user should use the new field to rename the filename. But be sure to also use the extension with the new filename, e.g. "winterLandscape.png"

 

 

Generated at Mon Feb 12 05:05:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.