Allure xAPI Connect (WordPress)

Overview

Embed and track SCORM 1.2/2004 packages hosted on Allure SCORM-API inside WordPress. Supports LearnDash, LifterLMS, Tutor LMS, and LearnPress with auto-completion.

Install / Update

1. Upload allure-xapi-connect-1.4.3.zip via Plugins → Add New → Upload Plugin.
2. Activate (deactivate/delete older versions first if WP blocks overwrite; settings stay in DB).
3. Go to Allure xAPI → Settings and set:
   • API Endpoint (default https://scorm-api.allurelms.com)
   • API Key (from Allure dashboard)
   • Tenant ID (from Allure dashboard)
4. Click Test Connection.

Upload SCORM packages

• Navigate to Allure xAPI → Packages → Add New.
• Pick a SCORM ZIP; upload goes direct-to-cloud via presigned URL.
• After processing, the package appears with its UUID.

Embed content

• Shortcode: [allure_scorm id="PACKAGE_UUID" width="100%" height="600" mode="embed|lightbox|new_window" title="Optional"]
• Gutenberg block: Insert Allure SCORM Player, choose package, width/height/mode.

LMS integrations

• Edit a lesson/topic → SCORM Content box → pick package and mode; optionally auto-complete on SCORM completion.
• Integrations: LearnDash (lessons/topics), LifterLMS (lessons), Tutor LMS (lessons), LearnPress (lessons).

REST for mobile/SPA

• Per-content lookup: GET /wp-json/allure-xapi/v1/content-scorm?post_id={ID}[&lms=learndash] → { post_id, lms, package_id, player_mode, auto_complete }.
• Exposed field on LearnDash lessons/topics: allurelms_scorm_package_id (e.g., /wp-json/wp/v2/sfwd-lessons?course={COURSE_ID}&_fields=id,title,allurelms_scorm_package_id).

Troubleshooting

• Test Connection fails: recheck API Key & Tenant ID; confirm SCORM-API availability.
• Upload fails: ensure hosting limits aren’t too low; presigned upload bypasses most PHP limits but memory may still apply.
• Iframe blocked: allow your WP origin in frame-ancestors and avoid X-Frame-Options: DENY on the content origin.