[
http://jira.magnolia.info/browse/MAGNOLIA-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379#action_17379
]
Jan Haderka commented on MAGNOLIA-1616:
---------------------------------------
Works fine for 3.6.1 EE, both sample and SiteDesigner templates.
> Versionned content is not rendered
> ----------------------------------
>
> Key: MAGNOLIA-1616
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1616
> Project: Magnolia
> Issue Type: Bug
> Components: activation
> Affects Versions: 3.0.2
> Environment: Tomcat 5.0, jdk 1.4.2.12
> Reporter: Capitaine Harold
> Assignee: Sameer Charles
> Priority: Critical
> Attachments: CurrentVersion.png, PreviousVersion.png
>
>
> It's not possible to render a versionned content. This bug can apply on the
> 3.0.2 and on the enterprise edition (tested on your website)
> Way to reproduce it:
> - create a page, add this text "version1" for example in the center of the
> page
> - activate it and get through the whole process.
> - Modify the same page with this text "version 2"
> - activate it and get through the whole process.
> - Modify the text with "version 3".
> - activate it but go at the first step of the workflow to your inbox, and do
> "show content"
> -The bug appears, the content is not rendered. (screenshot
> "PreviousVersion.png")
> So if you change the version number in the URL to the first version, for
> example 1.0, the content is not rendered.
> Magnolia is only able to render the current version of the page. (screenshot
> "CurrentVersion.png")
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
