[MAGNOLIA-3729] Dialogs not found after update Created: 07/Jun/11 Updated: 16/Aug/11 Resolved: 02/Aug/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, gui, templating |
| Affects Version/s: | 4.4.1, 4.4.4 |
| Fix Version/s: | 4.4.5 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Zdenek Skodik | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| 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 |
|
In case of using an extends feature for custom dialog definitions, one needs to reregister (i.e. server restart, or rename such dialog and name it back to its original name again) such dialog after update task of that module otherwise she will face http500 during its rendering (find the attachment). |
| Comments |
| Comment by Magnolia International [ 21/Jun/11 ] |
|
Actually in my case, there is no module version handler involved, and the issue reappears after each restart. Manually renaming a dialog "fixes" it. |
| Comment by Magnolia International [ 21/Jun/11 ] |
|
To be confirmed, but I suspect this has not much to do with the the update mechanism (or not only). |