[MGNLDAM-386] JcrAssetProvider#getAssetIdentifierForPath is not able resolve asset's identifier for path which contains also the file name Created: 29/Jan/14  Updated: 27/Aug/14  Resolved: 11/Aug/14

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

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Milan Divilek
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Date of First Response:

 Description   

damfn.getAssetLinkForId(item.image) returns the following url with the following DAM structure:

  • URL: /magnoliaAuthor/corporate/dam/moved_from_data_references/References/EEClients/Virgin-America/virgin-america-screenshot/virgin%20america%20screenshot.png
  • DAM Path: /moved_from_data_references/References/EEClients/Virgin-America/virgin-america-screenshot
  • Image name: virgin america screenshot
  • Image type: png

Unfortunately, the DAM servlet does not recognize this link. The following wraning is thrown:

2014-01-29 16:15:19,776 WARN  info.magnolia.dam.DefaultDamManager               : No asset Found for the following path '/moved_from_data_references/References/EEClients/Virgin-America/virgin-america-screenshot/virgin america screenshot'. Nothing will be returned

And the servlet use a fallback strategy to finally find the asset.

Unfortunately, since this call is successful, the cache associate this asset to a wrong url.



 Comments   
Comment by Daniele Biagi [ 27/Jun/14 ]

Hi, I am having this problem, despite all the assets that I use in my components are present and published, for some of them I see this message in the logs: WARN info.magnolia.dam.DefaultDamManager : No asset Found for the following path '/marketplace/123_image/image-hd-retina' .
The image is rendered in the page without any problems, but I see the error above in the logs. I also tried to re-publish the asset and to rename it, but I still see this error in the logs.
Do you know any workaround to avoid that the message above appears in the logs, while this bug is not fixed?

Comment by Milan Divilek [ 11/Aug/14 ]

URL /magnoliaAuthor/corporate/dam/moved_from_data_references/References/EEClients/Virgin-America/virgin-america-screenshot/virgin%20america%20screenshot.png is correct.

If the filename is not same as the node name then info.magnolia.dam.providers.jcr.JcrAssetProvider#getLink adds filename into link. This is same behaviour as in Magnolia 4.5, 4.4 ...

Problem here is that the info.magnolia.dam.providers.jcr.JcrAssetProvider#getAssetIdentifierForPath is not able resolve asset's identifier for path which contains also the file name. Edited issue title to describe real issue here.

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