I have a number of end-users who are only given application-level access, primarily to access a Workshop application via Carbon.
Some users have been bookmarking a specific Workshop application on their browsers, but unfortunately these links are soon to become outdated as we refactor our Marketplace deployment setup and deploy our use case into a Workshop module with a separate RID.
Is there any way I can setup an automatic redirect for users who have bookmarked the old Workshop module so that they can access the updated Workshop module instead?
Failing which we’d probably have to setup a button with some text to ask users to navigate to the new application page themselves, which isn’t as elegant.
I am assuming the current users are using a url that is /view/latest/ and not pinned to a specific version in which case you can consider updating the old workshop to have an embedded workshop widget in it which will point to the new Workshop application. Make sure page header is off and there is no padding and it will look identical to if you went to the new app directly.
Additionally, as you mentioned you can also add a popup to inform the users the link has changed and a button to redirect them which will allow them to bookmark the new version.
Great idea! Are there any performance/functionality drawbacks to be aware of when embedding Workshops as such? (especially when the embedded Workshops also have further embedded Workshops…)
The embedded Workshop module will not begin loading until the lightweight “wrapper” Workshop module loads, so there is some additional latency for each level of Workshop embedded module nesting.
Otherwise, there is no way currently to do something like deprecate a Workshop module and have it automatically redirect, but using embedded modules as mentioned seems like a good way to support this.