Skip to content

FAQ & Troubleshooting

What e-learning standards does SlideMind Bridge support?

Section titled “What e-learning standards does SlideMind Bridge support?”

SlideMind Bridge supports SCORM 1.2, SCORM 2004, and xAPI (Tin Can). Upload your package as a .zip file and Bridge automatically detects the format by looking for imsmanifest.xml (SCORM) or tincan.xml (xAPI).

Any tool that exports a standard SCORM or xAPI package works with Bridge. This includes Articulate Storyline, Articulate Rise, Adobe Captivate, iSpring Suite, Lectora, DominKnow, Adapt, and many others.

Bridge auto-detects and integrates with five LMS plugins: LearnDash, TutorLMS, LearnPress, LifterLMS, and Sensei LMS. When one of these is active, completion status and scores are automatically bridged back to the LMS. LearnDash integration is fully tested; the other four are currently in beta.

Yes. Bridge uploads, plays, and tracks learner progress for all packages regardless of whether an LMS plugin is active. You get full tracking data in the Reports page. The only difference is that completion data is not passed back to an LMS.

All tracking data (status, score, time, suspend data, xAPI statements, SCORM interactions) is stored in a custom database table ({prefix}smbr_tracking). Bridge uses a dedicated table instead of WordPress postmeta for performance — SCORM and xAPI generate many small writes that would bloat the postmeta table.

Two features require a Pro license:

  • Reports — The full reports dashboard with KPIs, learner tables, sparklines, CSV exports, and drill-down views.
  • External LRS forwarding — Forward xAPI statements to an external Learning Record Store (Learning Locker, Watershed, SCORM Cloud, etc.).

A Pro license is obtained through the companion SlideMind WP plugin or as a standalone Bridge license.

Bridge includes a built-in LRS emulator that handles xAPI statements and state for tracking purposes. It is not a full-featured standalone LRS — it stores statements locally and provides data for the Reports page. If you need a complete LRS with advanced analytics, use the External LRS forwarding feature (Pro) to send statements to a dedicated LRS platform.

Should I use the shortcode or the Gutenberg block?

Section titled “Should I use the shortcode or the Gutenberg block?”

Both produce identical output. Use whichever fits your workflow:

  • Gutenberg block — Visual configuration in the sidebar, preview in the editor, no need to remember attribute names.
  • Shortcode — Works in the Classic Editor, in page builders, and in LMS lesson editors that may not support Gutenberg blocks.

Deleting a package removes the package post, all extracted content files, and all associated tracking data (learner progress, scores, attempts). This action is irreversible.

Can multiple packages be embedded on the same page?

Section titled “Can multiple packages be embedded on the same page?”

Yes. Each shortcode or block instance operates independently with its own package ID and configuration. You can embed multiple packages on a single page using any combination of display modes.


Symptoms: The upload spinner runs indefinitely, or you see a “file exceeds the maximum upload size” error.

Solutions:

  1. Check the PHP upload limits displayed at the top of the Packages page. Bridge shows a warning when upload_max_filesize or post_max_size are too low.
  2. Increase these values in your php.ini or .htaccess:
    upload_max_filesize = 128M
    post_max_size = 128M
    max_execution_time = 300
  3. If you are on shared hosting, contact your provider to increase these limits.
  4. Ensure the ZIP file contains a valid imsmanifest.xml or tincan.xml at the root level (or one level deep).

Symptoms: The iframe shows a blank page or a “Security check failed” error.

Solutions:

  1. Not logged in — Learners must be logged in to WordPress. Bridge returns a 401 error for anonymous users.
  2. Expired nonce — If the page has been open for a long time, the nonce may have expired. Reload the page.
  3. Broken package — Try re-uploading the ZIP file. Ensure the package works in a local SCORM player or the authoring tool’s preview.
  4. Server configuration — Some hosting providers block serving HTML files from wp-content/uploads/. Check that your server allows serving static files from the smbr-packages directory.

Symptoms: The learner completes the module, but the status remains “not attempted” or “incomplete” in Reports.

Solutions:

  1. Check the browser console — Look for JavaScript errors or failed REST API calls to /wp-json/smbr/v1/.
  2. REST API blocked — Some security plugins or .htaccess rules block the WordPress REST API. Ensure /wp-json/smbr/v1/ is accessible.
  3. SCORM version mismatch — Verify that Bridge detected the correct version. Check the format badge in the Packages list. If the content was published as SCORM 2004 but Bridge shows SCORM 1.2, re-export from your authoring tool with the correct setting.

Symptoms: The browser console shows “Access-Control-Allow-Origin” errors when xAPI content tries to send statements.

Solutions:

Bridge handles CORS preflight automatically for its xAPI endpoints. If you still see CORS errors:

  1. Conflicting headers — Check if your server or a plugin is adding conflicting CORS headers. Remove any duplicate Access-Control-Allow-Origin headers.
  2. Apache .htaccess — If needed, add CORS headers for the xAPI endpoint:
    <IfModule mod_headers.c>
    SetEnvIf Request_URI "^/wp-json/smbr/v1/xapi/" XAPI_REQUEST
    Header set Access-Control-Allow-Origin "*" env=XAPI_REQUEST
    Header set Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS" env=XAPI_REQUEST
    Header set Access-Control-Allow-Headers "Authorization, Content-Type, X-Experience-API-Version" env=XAPI_REQUEST
    </IfModule>
  3. Nginx — Add equivalent headers in your server block for the xAPI endpoint path.

Symptoms: The learner completes a package but the LMS lesson/topic is not marked complete.

Solutions:

  1. No LMS detected — Check the Packages page for the green “Active LMS detected” notice. If you see a yellow warning, the LMS plugin may not be active.
  2. No course association — The package must be associated with a course. Edit the course field in the Packages list.
  3. Not embedded in a lesson — The shortcode or block must be placed inside an LMS lesson or topic page. Bridge captures the LMS context from the page where the shortcode renders. If the package is embedded in a regular page or post, Bridge cannot determine which lesson to mark complete.
  4. Status not final — Bridge only triggers completion passback for “completed” or “passed” statuses. An “incomplete” or “attempted” status does not trigger bridging.

Symptoms: The Reports menu item does not appear, or the page shows “No packages found.”

Solutions:

  1. Pro license required — Reports require a Pro license. Check that your SlideMind Pro license is active.
  2. No tracking data — If packages have been uploaded but no learner has interacted with them yet, the Reports page shows the empty state message. Have a test user complete a package to generate tracking data.
  3. Permissions — Only users with the manage_options capability (typically Administrators) can view Reports.