[MGNLUI-567] Implement direct content activation Created: 16/Jan/13 Updated: 18/Mar/13 Resolved: 31/Jan/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Description |
|
This is basically the implementation of https://magnolia.atlassian.net/browse/BL-127 |
| Comments |
| Comment by Samuli Penttilä [ 29/Jan/13 ] |
|
While testing I got this exception to console. /magnoliaPublic/ returns 404 so this is most likely a configuration issue. What concerns me is that in admincentral there is no feedback that something went wrong. 2013-01-29 14:31:42,527 ERROR info.magnolia.module.activation.ExchangeTask : Failed to deactivate content. |
| Comment by Federico Grilli [ 29/Jan/13 ] |
|
Re feedback, that should be fixed now. As to the ExchangeTask error make sure that
|
| Comment by Samuli Penttilä [ 30/Jan/13 ] |
|
Thanks. Activation works after changing configuration but status column stays red until pages app is restarted. Deactivating a page does not seem to work for me as it will cause an error. Digged the exception and this is where it fails. Caused by: javax.jcr.ItemNotFoundException: 674469eb-31c2-4dc3-aaa9-935469790539 |
| Comment by Federico Grilli [ 30/Jan/13 ] |
|
Cannot reproduce the ItemNotFoundEx, likely related to something local to your environment. Will file a separate issue for the status column not updated immediately after de/activation succeeds. |
| Comment by Federico Grilli [ 31/Jan/13 ] |
|
Further testing revealed that the path, workspace and identifier in an the action def would never change the after the definition class having been initialized so that you are basically activating or deactivating the same node over and over again |
| Comment by Samuli Penttilä [ 31/Jan/13 ] |
|
My steps to reproduce de-activation problem. Deletion happens recursively. Deleted pages are not visible in old admin interface either. |
| Comment by Federico Grilli [ 31/Jan/13 ] |
|
OK, you turned the author instance into a public one, setting it as a subscriber of itself, hence the error and the deletion (see related issue |
| Comment by Samuli Penttilä [ 04/Feb/13 ] |
|
Works as intended with two instances. Created follow-up ticket |