Hi Bence, First what you see in the 'Asset name' column in the tree is indeed the 'name' JCR property, not the name of the asset's JCR node.
I could dig (not too far) in the history, it looks like when a field was added for the asset's "name" property, it was explicitly "untied" from the JCR node name itself (http://jira.magnolia-cms.com/browse/MGNLDAM-458). I can think of a use case where someone renames an asset's JCR node, then edits the asset (NOT changing the [i]asset name[/i]), saves changes, and then his node is renamed back to the [i]asset name[/i]. This could well have been considered a destructive operation. While I understand this, I also know that it would still be the case in Contacts, and that in some other apps we don't even have an action to rename JCR nodes... — we could as well have left it consistently destructive, it wouldn't have been that bad imo. Anyway we'd like to streamline usages of name-like characteristics of content across apps: which fields are present in edit forms VS. rename actions or inline editing. In particular we want to emphasize usage of human-readable names over JCR names. Once we do, I hope it makes more sense again. Meanwhile, if this behavior doesn't fit your needs, perhaps you can reconfigure the rename action in the assets-app to open the generic rename dialog instead? - go to [code]/modules/dam-app/apps/assets/subApps/browser/actions/renameAsset[/code] - set the [code]dialogName[/code] property back to "ui-framework:rename". This would update the name property again and make renames directly visible in the tree. Cheers, Mika -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=ebfb5310-3bc8-4bc9-8d64-703a505d381c ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
