Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Framework import: IDs in links change (e.g. Start Controller) #2016

Closed
davetaz opened this issue Jul 12, 2018 · 3 comments
Closed

Framework import: IDs in links change (e.g. Start Controller) #2016

davetaz opened this issue Jul 12, 2018 · 3 comments
Assignees
Labels
T: enhancement Adding additional functionality

Comments

@davetaz
Copy link

davetaz commented Jul 12, 2018

Expected Behaviour

When you import a course the start controller (and other internal links) should remain working.

Actual Behaviour

They don't as the links have changed as new IDs have been created on import.

Steps to Reproduce

  1. Create a course with a start controller enabled to go to a specific contentPage
  2. Export this course
  3. Re-import the course and try and preview it.

Versions

  • Authoring Tool Version: 0.5.0
  • Framework Version: 2.2.5
  • Operating System: n/a
  • Browser: n/a

Suggested fix

On import give the option to retain IDs.

If importing into the same instance it was exported from this should overwrite the existing course.
If importing into a different instance then perhaps do an up-front check to see if the IDs are available?

This would also help in those cases where external tracking platforms are using the IDs to track completion. Having them change so easily is not useful either.

@lc-thomasberger
Copy link
Member

related to #1752

@taylortom taylortom added the T: enhancement Adding additional functionality label Mar 26, 2019
@dancgray dancgray self-assigned this May 23, 2019
@cksachdev
Copy link
Contributor

@taylortom Could you please advise on how to achieve this functionality in Adapt Authoring.

@taylortom
Copy link
Member

Closing due to inactivity & impending deprecation of the legacy codebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: enhancement Adding additional functionality
Projects
None yet
Development

No branches or pull requests

5 participants