[MGNLUI-3180] Detail subApp fails to start when initiated from publication messageView Created: 30/Sep/14 Updated: 02/Oct/14 Resolved: 02/Oct/14 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | pages app |
| Affects Version/s: | 5.3.3 |
| Fix Version/s: | 5.3.4 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Federico Grilli |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
To recreate the issue:
The follow error occurs: 2014-09-30 14:54:37,355 ERROR agnolia.ui.framework.app.AppInstanceControllerImpl: Sub-app detail failed to start: null java.lang.NullPointerException at info.magnolia.ui.contentapp.availability.IsNotVersionedDetailLocationRule.isAvailableForItem(IsNotVersionedDetailLocationRule.java:56) at info.magnolia.ui.api.availability.AbstractAvailabilityRule.isAvailable(AbstractAvailabilityRule.java:53) at info.magnolia.ui.framework.availability.AvailabilityCheckerImpl.isAvailable(AvailabilityCheckerImpl.java:104) at info.magnolia.pages.app.editor.PagesEditorSubApp.updateActionbar(PagesEditorSubApp.java:477) at info.magnolia.pages.app.editor.PagesEditorSubApp.doGoToLocation(PagesEditorSubApp.java:244) at info.magnolia.personalization.editor.PersonalizationPagesEditorSubApp.doGoToLocation(PersonalizationPagesEditorSubApp.java:102) at info.magnolia.pages.app.editor.PagesEditorSubApp.goToLocation(PagesEditorSubApp.java:238) at info.magnolia.pages.app.editor.PagesEditorSubApp.start(PagesEditorSubApp.java:199) at info.magnolia.personalization.editor.PersonalizationPagesEditorSubApp.start(PersonalizationPagesEditorSubApp.java:88) at info.magnolia.personalization.editor.PersonalizationPagesEditorSubApp.start(PersonalizationPagesEditorSubApp.java:55) at info.magnolia.ui.framework.app.AppInstanceControllerImpl.startSubApp(AppInstanceControllerImpl.java:385) at info.magnolia.ui.framework.app.AppInstanceControllerImpl.openSubApp(AppInstanceControllerImpl.java:341) at info.magnolia.ui.framework.app.BaseApp.start(BaseApp.java:71) at info.magnolia.ui.framework.app.AppInstanceControllerImpl.start(AppInstanceControllerImpl.java:222) at info.magnolia.ui.framework.app.AppControllerImpl.doStartIfNotAlreadyRunning(AppControllerImpl.java:257) at info.magnolia.ui.framework.app.AppControllerImpl.onLocationChanged(AppControllerImpl.java:337) at info.magnolia.ui.api.location.LocationChangedEvent.dispatch(LocationChangedEvent.java:64) at info.magnolia.ui.api.location.LocationChangedEvent.dispatch(LocationChangedEvent.java:42) at info.magnolia.event.SimpleEventBus.fireEvent(SimpleEventBus.java:78) at info.magnolia.ui.api.location.LocationController.goToWithoutChecks(LocationController.java:103) at info.magnolia.ui.api.location.LocationController.goTo(LocationController.java:97) at info.magnolia.module.workflow.action.PreviewPageAction.execute(PreviewPageAction.java:56) at info.magnolia.ui.api.action.AbstractActionExecutor.execute(AbstractActionExecutor.java:62) at info.magnolia.ui.admincentral.shellapp.pulse.item.detail.AbstractPulseDetailPresenter.onActionbarItemClicked(AbstractPulseDetailPresenter.java:155) at info.magnolia.ui.actionbar.ActionbarPresenter.onActionbarItemClicked(ActionbarPresenter.java:205) at info.magnolia.ui.actionbar.ActionbarViewImpl$1.actionTrigger(ActionbarViewImpl.java:67) |
| Comments |
| Comment by Federico Grilli [ 02/Oct/14 ] |
|
While I could reproduce this on 5.3.3, this seems to have been fixed in 5.3.4-SNAPSHOT even though I couldn't pinpoint the exact issue where this happened. |