[MAGNOLIA-3421] LogViewer never installed when updating Created: 29/Nov/10 Updated: 04/Dec/13 Resolved: 04/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 4.3.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
The LogViewer introduced in Magnolia 4.0 has never been installed on updated instances. (i.e when updated from a version prior to 4.0) There are at least two bootstrap files (menu item, page definition) that would need to be bootstrapped, but of course users might have bootstrapped those manually (just did so on docu), so update tasks need to be written carefully. |
| Comments |
| Comment by Jan Haderka [ 04/Dec/13 ] |
|
As there are no longer any instances running on pre-4.0 version that are being upgraded and all the others have been already fixed by manually bootstrapping all necessary configuration this issue doesn't seem to be relevant anymore. |