[MAGNOLIA-1616] Versionned content is not rendered Created: 03/Jul/07  Updated: 05/Aug/08  Resolved: 05/Aug/08

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 3.0.2
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Capitaine Harold Assignee: Magnolia International
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tomcat 5.0, jdk 1.4.2.12


Attachments: PNG File CurrentVersion.png     PNG File PreviousVersion.png    
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   

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")



 Comments   
Comment by Magnolia International [ 03/Jul/07 ]

From what I can see through the versions dialog, version 1.2 does not exist (I was confused by your screenshots which both render the same content) - actual versions are 1.0, 1.1 and 1.2
The actual problem seems to be that the template is not (fully?) rendered.

My guesses are:

  • when you tried with CE, you forgot to remember that only 2 versions were kept ?
  • the problem that you screenshot'd with EE might be related to sitedesigner which has its own special way of inheriting templates / layout.
    Would be great if you could confirm that
Comment by Jan Haderka [ 05/Aug/08 ]

Works fine for 3.6.1 EE, both sample and SiteDesigner templates.

Generated at Mon Feb 12 03:28:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.