Allure Connect SCORM and xAPI

Run SCORM in WordPress without running your own SCORM engine. Allure Connect hosts your SCORM 1.2 and SCORM 2004 packages and delivers them to signed-in WordPress learners. Add a course to any post or page with the Allure SCORM Player block or [allure_scorm] shortcode, then choose an embedded player, lightbox, or new window. Learners can resume incomplete sessions. Administrators can review progress, scores, time spent, completion status, and related xAPI activity. When you use LearnDash, LifterLMS, Tutor LMS, or LearnPress, the plugin can also mark the linked lesson complete after the package reports SCORM completion. Allure Connect keeps the hosted runtime, session data, and xAPI Learning Record Store together, so your WordPress site can deliver and track interactive training without maintaining a local SCORM engine. Learn more and create a free sandbox account: https://allureconnect.com Third-Party Services This plugin requires Allure Connect, a hosted SaaS described at https://allureconnect.com. The connector sends service requests to the Allure Connect application at https://app.allureconnect.com for API credentials, SCORM package upload and hosting, learner launches, session and progress tracking, xAPI storage, and analytics. The plugin cannot upload, launch, resume, or track SCORM content without an active Allure Connect account and valid API credentials. Depending on the feature used, requests may include your configured API key and Tenant ID, package metadata and ZIP uploads, WordPress user identifiers, linked post IDs, LMS identifiers, learner progress, scores, completion status, session identifiers, and xAPI statement data. Use of the Allure Connect service is governed by:

• Terms: https://allureconnect.com/legal/terms
• Privacy Policy: https://allureconnect.com/legal/privacy

Features

• Host SCORM outside WordPress - Upload SCORM 1.2 and SCORM 2004 ZIP packages from WordPress while Allure Connect hosts and serves the runtime
• Embed without custom code - Add training to posts and pages with the Allure SCORM Player block or [allure_scorm] shortcode
• Choose the learner experience - Launch content embedded, in a lightbox, or in a new window
• Resume incomplete sessions - Return each learner to an existing incomplete session
• Track learning outcomes - Review progress, scores, time spent, completion status, and related xAPI activity
• Sync LMS completion - Optionally complete a linked LMS lesson after the package reports SCORM completion
• Connect four WordPress LMS plugins - Built-in adapters for LearnDash, LifterLMS, Tutor LMS, and LearnPress

LMS Integrations This connector includes named compatibility for these major WordPress LMS plugins:

• LearnDash - Add SCORM content to lessons and topics and mark LearnDash items complete after SCORM completion.
• LifterLMS - Add SCORM content to LifterLMS lessons and mark lessons complete from SCORM completion.
• Tutor LMS - Add interactive SCORM modules to Tutor LMS lessons and sync completion.
• LearnPress - Add SCORM packages to LearnPress lessons and sync lesson completion.

SCORM packages can also be embedded on standard WordPress posts and pages without an LMS. When an LMS lesson is linked to a package, the plugin passes the WordPress post ID and LMS identifier through launch, progress, and completion routing so reused packages complete the correct lesson. All third-party LMS names are trademarks of their respective owners. Compatibility does not imply endorsement by those vendors. How It Works

1. Create an Allure Connect account and open Dashboard → Integrations → API Keys
2. Install the plugin, enter your API key and Tenant ID, and test the connection
3. Upload a valid SCORM 1.2 or SCORM 2004 ZIP from Allure xAPI → Packages
4. Add the course with the Gutenberg block, shortcode, or a supported LMS lesson integration
5. Let signed-in learners launch or resume the course, then review sessions, scores, completion, and related xAPI activity

Shortcode Usage [allure_scorm id="package-uuid"] Options:

• id - Package UUID (required)
• width - Player width (default: 100%)
• height - Player height in pixels (default: 600)
• mode - Display mode: embed, lightbox, or new_window (default: embed)
• title - Optional title for lightbox/new_window modes
• post_id - Optional WordPress post ID used for LMS completion routing when a SCORM package is reused
• lms - Optional LMS identifier used with post_id for LMS-specific routing

Requirements

• WordPress 5.8 or higher
• PHP 7.4 or higher
• Allure Connect account and API credentials (start at https://allureconnect.com)

1.4.9

• Lead the WordPress.org listing with the customer outcome: run SCORM in WordPress without maintaining a local SCORM engine.
• Replace release-QC screenshots with a clean upload → embed → learn → measure product story captured from a disposable WordPress site and the hosted Allure Connect demo.
• Use allureconnect.com for public brand, documentation, and legal links while keeping app.allureconnect.com for authenticated application and connector traffic.
• Clarify the hosted-service dependency, xAPI scope, learner access boundary, SCORM support wording, and resume behavior.
• Update embedding security behavior, including CSP and frame-header handling, while leaving SCORM launch, progress, and completion logic unchanged.

1.4.8

• Update the plugin display name to the official Allure Connect SCORM/xAPI naming for WordPress.org owner validation.
• WordPress.org review readiness: resolved all Plugin Check errors and warnings — prepared statements / escaping and sortable-column whitelisting for admin reporting queries, and documented direct database access on the plugin's own tables.
• Fix the package score-distribution histogram (literal % was mis-parsed by prepared statements).
• Replace a WordPress 6.1-only function with a 5.8-compatible equivalent and remove the redundant text-domain loading call.
• Allow large SCORM uploads to finish processing by using a longer, filterable API timeout (fixes request timeouts on big packages).
• Declare the Gutenberg editor bundle's WordPress runtime dependencies so the Allure SCORM Player block registers reliably on a fresh site.
• Expand cached package ID columns, run a schema-only migration, and normalize live package IDs in the report filter so long Connect package IDs persist and completed launches render cleanly in the Sessions report.
• Omit absent optional scores from progress requests so WordPress REST validation accepts completion updates instead of leaving sessions at Unknown.

1.4.7

• Reliability: the player script now loads once per page (prevents duplicate progress submissions) and reliably flushes final progress when a learner closes the tab.
• Security: player messages are validated by their source and completion webhook callbacks require a signed (HMAC) request.
• Store each launch's WordPress post and LMS context (adds a session database column on update) so reused SCORM packages always complete the correct lesson.
• Validate uploaded SCORM files as real ZIP archives before processing.
• Admin analytics charts now load from a bundled copy of Chart.js (no external CDN).
• Minor fixes to storage/quota display and completion-status handling.

1.4.6

• Add block keywords so the SCORM Player block surfaces quickly in the block editor.
• Improve WordPress.org listing copy with named compatibility for LearnDash, LifterLMS, Tutor LMS, and LearnPress.
• Pass WordPress post/LMS context through SCORM launch and progress routing so reused packages complete the correct LMS lesson.
• Harden session completion routing for reused SCORM packages and require signed/API-key-authenticated webhook callbacks.
• Improve WordPress.org readiness: sanitize saved player settings, use consistent nonces for frontend launches, and document the Allure Connect service dependency.
• Package release files are built from the maintained WordPress plugin source.

1.0.0

• Initial release
• SCORM 1.2/2004 support
• Shortcode and Gutenberg block
• LearnDash, LifterLMS, Tutor LMS, and LearnPress integrations
• Session tracking and reporting