The Tin Canny Uploader is part of the Tin Canny LearnDash Reporting Toolkit that we developed to help you add e-learning content authored in Storyline, Captivate, or iSpring to a lesson or topic. (H5P modules are added through the H5P plugin rather than uploaded.) The Uploader is integrated with the both the Classic Editor and Gutenberg so you can quickly attach an e-learning module as part of your content creation workflow.
If for any reason the zip file is too big to upload inside WordPress (this would typically include files over 100 MB), this workaround is available but should only be performed for large files:
- Publish the zip file as you normally would.
- Extract the contents of the zip file. (Don’t use a Mac for this, as it can add hidden files that break the upload process.)
- Move the big media files elsewhere and remember the folder they were in.
- Zip the files back up so the structure is the same (minus the large files; just make sure the XML file is still in the root).
- Upload the zip file through the Tin Canny uploader as before. if there’s an error, maybe it wasn’t zipped back up again properly.
- On the lesson/topic edit page, note the identifier in the shortcode. You’ll see an snc one.
- Connect to the site by FTP. Navigate to /wp-content/uploads/uncanny-snc/.
- Find the # corresponding with the shortcode in step 6 and go into it.
- Upload the large files to wherever they’re supposed to be.
You have three different ways to display Storyline/Rise, Captivate, or iSpring content:
- Embed the module in an iFrame on the current page
- Use a link or button to launch the module in a Lightbox
- Use a link or button to launch the module in the current window, or a new window
Important: Make sure you give the module you are uploading a distinct and descriptive title. This title will be identified as the module’s name in the Tin Can Report and it can’t be changed later.
Your module will be added as a shortcode in the Classic Editor:
Or as a Gutenberg block in a Gutenberg post:
Tin Can/xAPI Data
In order to capture Tin Can data, your Storyline/Rise, Captivate, or iSpring module must have been published to xAPI or SCORM (1.2 or 2004). The module will still work if it was published to web but you won’t be able to capture Tin Can data. We recommend publishing to xAPI if the option is available, as in some situations it offers performance advantages over SCORM tracking.