Closed CTLocalGovTeam closed 9 years ago
cc @kellyhutchins.
Kelly, is there a reason the item URL has the group stored in it? It seems like the app should be able to handle which group to use and it shouldn't be forced in the URL because then the app cannot change it. Thoughts?
Ideally, it would not be there at all. Only set in the application JSON.
cc @iwittenmyer.
@driskull tested with the templates in online and they do read the group id from the app data so it seems like we don't need the url param. Sounds like a bug should be submitted to online to remove the group id from the url param for the configured app.
Submitted issue for this. 3131
Issue resolved for 3.13 closing here.
@driskull Steps to reproduce:
We see that when a gallery app is published, the app url contains the groupid of the group that was used to publish the app. When a different group is chosen using the configuration panel, it is saved to app configuration. However, the app url still retains the original groupid that was used to publish the app. Hence, when the app launches, boilerplate gives highest priority to URL parameters and ignores the groupid that was saved to app configuration.
We don't think this is a boilerplate issue, since we are of the opinion that url parameters must always be given highest priority. What would be ideal is that the configuration app (configureApp.html) should update the app url with the new groupid when the group is changed.
Please suggest a solution or a workaround that will reflect the changed group.