[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: |
|
| 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:
So if you change the version number in the URL to the first version, for example 1.0, the content is not rendered. |
| 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 My guesses are:
|
| Comment by Jan Haderka [ 05/Aug/08 ] |
|
Works fine for 3.6.1 EE, both sample and SiteDesigner templates. |