1. Home
  2. Knowledge Base
  3. Tin Canny LearnDash Reporting
  4. Tin Canny Uploader


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.

Tin Canny Content Uploader in the Classic Editor


Tin Canny Content Uploader in Gutenberg

Upload zip files published directly from your authoring tool only. All modules must be uploaded through our upload tool, as it modifies some javascript files in the modules to ensure that statements are tracked properly.

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.

Display Options

You have three different ways to display Storyline/Rise, Captivate, or iSpring content:

  1. Embed the module in an iFrame on the current page
  2. Use a link or button to launch the module in a Lightbox
  3. Use a link or button to launch the module in a new window

Classic Editor

Your module will be added as a shortcode in the Classic Editor:

Elementor/WP Bakery Page Builder/Other Editors

If you are using a pagebuilder such as Elementor or WP Bakery Page Builder, look for a “text” module and add that to the page.  The editor in the text module should display the Add Tin Canny Media button (see above), which you can use to insert your content.

Gutenberg Editor

You can use the included Gutenberg block to add Tin Canny content using the Gutenberg editor:

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.

Very large files

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:

  1. Publish the zip file as you normally would.
  2. 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.)
  3. Move the big media files elsewhere and remember the folder they were in.
  4. 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).
  5. 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.
  6. On the lesson/topic edit page, note the identifier in the shortcode. You’ll see an snc one.
  7. Connect to the site by FTP. Navigate to /wp-content/uploads/uncanny-snc/.
  8. Find the # corresponding with the shortcode in step 6 and go into it.
  9. Upload the large files to wherever they’re supposed to be.

Was this article helpful?

25 replies
  1. Chantal Forssman
    Chantal Forssman says:

    Hi, is there a way to set the lightbox size globally for all Articulate content to be uploaded? Or do we have to do it manually for each?

    • Ryan
      Ryan says:

      In the current version of Tin Canny you can set a default size for the lightbox globally from the Tin Canny Settings page, but I’m afraid that will take effect for newly uploaded modules only.

    • Ryan
      Ryan says:

      I’m afraid that trial versions are not available for any of our plugins, but if you have questions, we’re happy to answer them.

  2. Martin Wells
    Martin Wells says:

    Hi Ryan,
    I’m trying to upload content but it says unsupported content, created in articulate…
    What is the fix please?

    • Ryan
      Ryan says:

      What kind of module is it? There are 2 likely causes: it’s from an unsupported authoring tool from Articulate (e.g. Storyline 1, Presenter 13, etc.) or the file wasn’t zipped properly. It should be the zip file that the tool creates, not one that you create from exported files (especially on a Mac, which adds hidden files that break the upload).

  3. aaron
    aaron says:

    when I complete a SCORM 1.2 course the results don’t appear to be getting to the reporting functions of tin canny. I am using ispring and uploading using your upload tool is there a setting that I am missing.?

    • Ryan
      Ryan says:

      Hi Aaron, please note that iSpring results will only show up in the Tin Can tab of the Tin Canny reports in the back end. If that’s where you’re checking and still not seeing statements, please submit a ticket or send us an email. We can’t handle site-specific issues in Knowledge Base comments. Thanks!

    • Ryan
      Ryan says:

      I’m afraid I’m not sure what you mean. We support Storyline and Rise in 360, and both have export options that you must use to create a zip file suitable for Tin Canny. If you mean STUDIO 360 (e.g. Presenter), I’m afraid we don’t support it.

  4. John Erickson
    John Erickson says:

    Thanks, Ryan! That helps. So right now we are just working on getting all the course content (authored with Articulate, Engage, QuizMaker) into Storyline 360 so that we can export from there and then test.

  5. david
    david says:

    do you support articulate quizmaker? im getting this message:Unsupported file type detected.
    Please note that any xAPI/SCORM statements sent by this module:
    will not be recorded
    may display errors because the module cannot communicate with an LMS or LRS
    To use this module anyway, select the .html file that launches the module using the file browser below:

    • Ryan
      Ryan says:

      Sorry Cameron, we unfortunately can’t offer it. Right now Tin Canny and WordPress cannot support SCORM packages with offsite assets, and that’s part of the reason we have to limit which authoring tools we support.

  6. Jacques TOLLU
    Jacques TOLLU says:

    Hello, I uploaded the module the iframe or link or new window displays a white screen only not the module itself. It works though on another website but not on this one …. am I missing a parameter ?


    • Ken Young
      Ken Young says:

      Hi Jacques, we replied via email a while ago, but we’re also responding here in case this might help someone else.

      There could be a number of reasons for the problem, so let’s trace what’s happening for you:

      • In Tin Canny, check the Site Check tab and make sure everything is a pass.
      • On the page where the module is showing a white screen, try viewing the console (View > Developer > Javascript Console in Chrome). Are any errors being output? If they are, those might yield clues. Mixed content errors in particular can cause white screens like that.
      • Try with Content Protection in Tin Canny turned off for the associated lesson or topic (or is it a lesson or topic?). See if that makes any difference.

      Hopefully one of those gets us closer.

  7. Philip Hutchison
    Philip Hutchison says:

    Hi Ryan. Can you please be more specific about “SCORM packages with offsite assets”? I just purchased Tin Canny yesterday and am encountering the same error. What exactly is needed to alleviate the issue? What can’t be hosted externally? My package is dead simple and works in every LMS I’ve ever tried. Thanks

    • Ryan
      Ryan says:

      With Tin Canny we do not offer full SCORM compliance; part of the reason is the licensing fee that would make Tin Canny absolutely prohibitively expensive and likely not a viable product. We support certain authoring tools only and in specific ways that allows us to capture and report on data. There is no way to work around these restrictions; you must use supported authoring tools and have the modules hosted locally on the WordPress site for Tin Canny to capture the data properly.

  8. Philip Hutchison
    Philip Hutchison says:

    I’m also a bit concerned about what I’m reading on this page, specifically:

    1) “it modifies some javascript files in the modules to ensure that statements are tracked properly”. Can you please point to documentation outlining the changes made by Tin Canny? The last thing I want is my JavaScript to be modified by an automated system.

    2) “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.)” Don’t know what to say here… if you know Macs add hidden files (assuming you mean .DS_store) your upload script should filter them out automatically rather than saying “Don’t use a Mac”.


    • Ryan
      Ryan says:

      We modify the scormdriver package to tell your module how to pass data to our endpoint. That’s it. If you check that file before and after upload you’ll see that it’s modified very slightly with that change only.

      For #2, we’ll take a look at it, but this is something we don’t currently support and that may cause problems in certain hosting environments.

  9. Vincent Saporito
    Vincent Saporito says:

    When uploading the scorm from Articulate 2 – i am getting an error “something went wrong” – Any idea? The file is only 20megs and weve updated max file size.



Please note that this is not an official support channel and questions/comments may go unanswered.
To request support, log in to your account and click Submit a Request.

Leave a Reply

Your email address will not be published. Required fields are marked *