[MGNLUI-1481] Location loses subAppId when switching apps Created: 29/May/13  Updated: 10/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Tobias Mattsson Assignee: Unassigned
Resolution: Cannot Reproduce 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   

Steps to reproduce:

  • Open pages app
  • Open a page for editing
  • The location now includes 'detail'
  • Go to the app launcher
  • Start security app
  • Go to the app launcher
  • Click the Pages app
  • The location no longer has 'detail' in its name


 Comments   
Comment by Federico Grilli [ 11/Jun/13 ]

I was able to pinpoint the cause at info.magnolia.ui.vaadin.gwt.client.applauncher.connector.AppLauncherConnector.createWidget().new Presenter().activateApp(String) where only the app name is passed to activate app and not the sub app id. After a brief discussion with Philipp it was agreed that this is not a critical issue and can be put off to the next bug fix release after 5.0.

Comment by Philip Mundt [ 20/Jun/13 ]

Adding a "?restartApplication" in front of the hash will break the app (show loader gif) completely.
One cannot do anything else than logout afterwards.

Comment by Jozef Chocholacek [ 01/Jul/13 ]

The "?restartApplication" problem has gone - probably due some other fixes for 5.0.1

Comment by Jozef Chocholacek [ 02/Jul/13 ]

After a half day of tracing the code, I'm postponing this to 5.1 - the problem is too deep in the Location handling:

When the app is switched, the fragment without the subAppId is passed - then during the handling of this (incomplete) fragment, the app is restored and a fragment with the proper subAppId is created and handled. But then the execution returns to the handling of the incomplete fragment, and it is then passed to the URI.

Comment by Roman Kovařík [ 10/Mar/21 ]

Can't reproduce on latest https://demo.magnolia-cms.com/.magnolia/admincentral#app:pages-app:detail;/travel:edit

Generated at Mon Feb 12 08:47:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.