Since version 1.3.0: BricksMembers can import SCORM ZIP packages through SCORM Cloud, assign them to lessons or pages, launch them with the native SCORM Player Bricks element, and map SCORM completion back into BricksMembers progress.
SCORM is a common learning-content format used by course authoring tools. BricksMembers does not try to run SCORM packages locally inside WordPress. Instead, it uses SCORM Cloud as the runtime provider and keeps WordPress responsible for membership access, assignment, launch buttons, and progress integration.
This keeps the site lean while still letting you use packaged course content from tools that export SCORM 1.2 or SCORM 2004 packages.
What the SCORM module does
- Imports SCORM ZIP packages after validating the package manifest.
- Uploads packages to SCORM Cloud.
- Stores package, SCO, assignment, registration, and event data in BricksMembers tables.
- Assigns an imported package to a WordPress post, lesson, or page.
- Creates learner-specific SCORM Cloud launch links when a member starts the lesson.
- Receives SCORM Cloud postbacks and can sync registration status.
- Marks BricksMembers content complete when the SCORM result satisfies the configured completion policy.
SCORM Cloud is the only exposed provider in this release. The local manifest parser is used for validation and metadata before upload, not for running the course package in WordPress.
Enable SCORM
- Open BricksMembers -> Modules.
- Enable SCORM.
- Open BricksMembers -> SCORM.
- Enter your SCORM Cloud API base URL, App ID, and Secret Key.
- Copy the generated postback URL into SCORM Cloud so completion updates can return to your site.
- Choose your default completion policy and launch defaults.
- Save the settings.
Secret values are stored through the BricksMembers secret option service. If a secret is already saved, the settings screen shows a placeholder instead of exposing the stored value.
Import a SCORM package
Open BricksMembers -> SCORM and use the import panel to upload a SCORM ZIP package. BricksMembers validates the upload before handing it to SCORM Cloud.
- The package must be a ZIP file.
- The ZIP must include
imsmanifest.xmlat the package root. - The manifest must contain at least one launchable SCO.
- Unsafe ZIP paths are rejected.
- Very large or unusually complex packages are blocked by configured limits.
After import, the package appears in the SCORM package list. If SCORM Cloud is still processing the upload, use the sync action on the package row to refresh its import status.
Assign a package to a lesson or page
A SCORM assignment connects one imported package to one WordPress post. Use the assignment panel on the SCORM page to choose the package, target post, completion policy, optional minimum score, and launch mode.
| Setting | What it controls |
|---|---|
| Package | The imported SCORM package to launch. |
| Post | The lesson, page, or content post that owns the SCORM activity. |
| Completion policy | Which SCORM status or score should count as complete in BricksMembers. |
| Minimum score | Optional score threshold for score-based completion. |
| Launch mode | Embedded iframe or new window. |
Assignments do not replace normal BricksMembers access protection. If the target lesson requires a level, enrollment, prerequisite, or drip unlock, BricksMembers checks that access before launching the SCORM lesson.
Add the SCORM Player element in Bricks
Edit the lesson template or page in Bricks and add the SCORM Player element from the BricksMembers element group. The element renders a launch button for the current post assignment.
- Post ID override: normally leave this empty so the current post is used.
- Launch mode: use the assignment setting, force embedded iframe, or force new window.
- Button text: change the visible launch label.
- Button Style and Button Size: use BricksMembers button styles or AutomaticCSS button classes.
Do not paste SCORM Cloud launch URLs into Bricks content. Launch URLs are created per learner registration and should come from the SCORM Player element.
How completion works
When BricksMembers receives or syncs a SCORM result, it evaluates the assignment’s completion policy. If the registration satisfies that policy, BricksMembers marks the assigned post complete through the normal progress system.
completed: SCORM reports completed.passed: SCORM reports passed.complete_or_passed: either completed or passed counts.complete_and_passed: both completed and passed are required.score_threshold: the reported score must meet the minimum score.
Because completion flows through the normal BricksMembers progress owner, dashboards, progress bars, structure progress, automations, and other completion-aware features can react to SCORM completion like they do for other lesson completion events.
Security and access notes
- SCORM ZIP files are treated as untrusted uploads and validated before import.
- Only users with SCORM management permission can save settings, import packages, assign packages, or sync imports.
- Learners must be logged in before launch.
- Non-admin learners must be able to read and access the target post before BricksMembers creates a launch link.
- SCORM Cloud postbacks must include the configured postback secret.
- Launch, sync, and postback requests are rate limited.
Troubleshooting
The package will not import
Confirm that the ZIP includes imsmanifest.xml at the root and that the package contains a launchable SCO. Also check that your SCORM Cloud credentials are saved and valid.
The launch button says the lesson cannot launch
Check that the package is imported successfully, the package is assigned to the current post, and the current member can access the post according to your BricksMembers access rules.
Completion does not update
Check the SCORM Cloud postback URL and secret, then sync the registration from the SCORM admin area if needed. Also confirm that the assignment completion policy matches what the SCORM package reports.
Current boundary
BricksMembers 1.3.0 supports SCORM Cloud import, launch, tracking, postbacks, sync, and completion mapping. It does not expose a local SCORM runtime. Local SCORM hosting would require separate runtime, resume, CMI persistence, secure asset serving, and browser compatibility work.