![]() |
|
|
|
|
Change By:
|
Christopher Zimmermann
(07/Mar/13 9:00 AM)
|
|
Description:
|
While it may be possible to get this feature quickly working for just a demo - ie by storing another "original" binary on the same asset node that does not get edited - this will not satisfy the actual requirements of the specced feature. It could be that there is some overlap in the "quickfix/hack" and the actual implementation.
Please see this page for analysis of where the binary for the original should be stored: http://wiki.magnolia-cms.com/display/DEV/Concept+-+Workspace+structure+for+assets+with+originals
Please see this doc for full specification of original/variant functionality: http://wiki.magnolia-cms.com/display/UX/Digital+asset+management
FYI: actual resource is stored on asset node on "/jcr:content"
property
node
.
Quickfix Concept:
* /jcr:content-original node can save the original resource on the same asset node.
* On saving an edit, check if /jcr:content-original exists, if not: copy /jcr-content to it before saving edit.
* On uploading a new file, delete /jcr:content-original node
* On duplicating an asset - be sure /jcr:content-original is also duplicated (I guess everything is)(Of course this wastes space (duplication of original).)
* On "Revert to original" click, copy /jcr:content-original to /jcr:content and delete /jcr:content-original
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
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]>
----------------------------------------------------------------
