[MGNLUI-2231] Publishing the deletion of a page leads to a page in a weird state Created: 03/Oct/13 Updated: 10/Dec/13 Resolved: 09/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | pages app |
| Affects Version/s: | 5.1, 5.2 |
| Fix Version/s: | 5.2.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Andreas Weder | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
5.1 Enterprise Edition |
||
| 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: | |||||||||
| Sprint: | 5.2.1 | ||||||||
| Description |
|
When I attempt to publish the deletion of a page, I get a weird top-level page with no icon until I close and re-open the Pages app. Steps to reproduce:
Also reproducible when having configuration app open on public and deleting a visible node on author. It even crashes the the whole admincentral. by Internal Error. |
| Comments |
| Comment by Christoph Meier [ 09/Oct/13 ] |
|
in a 1st attempt i'm not able to reproduce the above described issue. Instead everything worked as expected. |
| Comment by Andreas Weder [ 09/Oct/13 ] |
|
I've been able to reproduce this error with 5.1 final, but with a slightly different result:
|
| Comment by Andreas Weder [ 09/Oct/13 ] |
|
I've updated this issue to reflect the current state with 5.1 EE final. I've also lowered the priority, since I get no exception any more and there's a workaround (close and re-open Pages). |
| Comment by Christoph Meier [ 09/Oct/13 ] |
|
so. for me this looks more like a bug in the tree-view ... maybe. |
| Comment by Christoph Meier [ 15/Oct/13 ] |
|
i have the impression, that the described behavior is due to an error in updating the views. According to Sasha, this could be fixed by forcibly re-querying the container on app-restore, but he believes that is not scheduled for nearest future ... hm ... |
| Comment by Andreas Weder [ 13/Nov/13 ] |
|
This problem still exists in 5.2 beta 1 and shows up the same as in 5.1 final, so:
|
| Comment by Daniel Lipp [ 13/Nov/13 ] |
|
This bug is not showing up in ce-edition: must be that container is not properly refreshed in ee where the publication is not immediately happening but only after approval… |
| Comment by Espen Jervidalo [ 21/Nov/13 ] |
|
for the second use case, here's a snippet from the log: 2013-11-21 10:39:07,290 INFO info.magnolia.module.activation.ReceiveFilter : User superuser succeessfuly deactivated /modules/core/testt on magnoliaPublic. |