[MGNLDAM-951] Asset Filename cannot be renamed Created: 17/Mar/21  Updated: 22/Sep/21  Resolved: 07/Jun/21

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

Type: Bug Priority: Neutral
Reporter: Gabriele Piras Assignee: Roman Kovařík
Resolution: Workaround exists Votes: 0
Labels: VN-Testing, cs-bk, maintenance
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2021-03-22 at 15.21.25.png     JPEG File filename_cannot_be_modified.jpg     PNG File rename_asset_5_7.png    
Issue Links:
documentation
to be documented by MGNLDAM-973 DOC: Document alternative ways of ren... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Documentation update required:
Yes
Date of First Response:
Sprint: Maintenance 56, Maintenance 57, Maintenance 58, Maintenance 60, Maintenance 61
Story Points: 3

 Description   

We have removed in Magnolia 6.2 the possibility to rename the file during the Upload process. (See attached screenshot)

Rename action could be used on Magnolia 5.7 for SEO Reasons. This missing rename option for files generates now for the customer additional workload.

Steps to reproduce

  1. go to Dam app
  2. upload a new asset or edit an existing one

Expected result

The editor can edit the asset name as it was possible in 5.7

Current behaviour

The editor cannot edit the asset name and if the editor use Asset Name for this, it is not working as expected.

Workaround

A] Edit the asset name before uploading it to Magnolia
B] Using legacy assets app where this option is still available.
C] Hotfix/decorate magnolia-dam-app-jcr/src/main/resources/dam-app-jcr/dialogs/uploadAndEdit.yaml with:

form:
  properties:
    upload:
      ...
    jcr:content:
      $type: compositeField
      itemProvider:
        $type: jcrChildNodeProvider
      properties:
        fileName:
          $type: textField

Development notes

It used to work in Magnolia 5.7. 
When opening using damlink field, the chooser is not displaying the asset name correctly, when it is displayed correctly in dam app.

 

 



 Comments   
Comment by Federico Grilli [ 07/Jun/21 ]

Unfortunately there are some tech constraints which prevent us from doing what we did in 5.7.x. unless we hack it somehow which we'd rather avoid.

In Roman's words:
"The thing is that the name in the upload view is not really a field, it's just a label not connected to backend.
There might be a way to hack it but I'd stay away from that.
If there is only one or few customers requesting this, can they just use this config on their own and we would only document this (we can even provide a ready-to-use decoration file)?"

I would therefore close this ticket and mention in the documentation the possible alternatives, decoration of dam-app-jcr in particular.

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