WordPress and Moodle

WordPress workflow#

1. Install the DRM-X Universal Player plugin on a staging site.
2. Enter environment credentials in administrator-only settings; the Access Key must never appear in page HTML.
3. Map post metadata or a shortcode such as [drmx_player] to a trusted Published protected file Content ID.
4. Connect entitlement through the provided filter or supported LearnDash/LearnPress course-access check.
5. Select a server-owned named policy template.

Download WordPress package

Moodle workflow#

1. Install the maintained filter in a staging Moodle environment.
2. Configure Site ID, Site Key, and Access Key in administrator settings.
3. Map the activity or filter markup to a trusted Content ID.
4. Require the learner to be authenticated and enrolled with course access before creating playback.
5. Test teacher, student, suspended, expired, guest, and unenrolled roles.

Download Moodle package

Safe customization#

Theme the player and map your content catalog freely. Keep these choices on the server: DRM-X Content ID, subject, named policy or custom policy, rental window, allowed quality, and entitlement. Do not accept them from shortcode authors who are not trusted administrators.

Production acceptance#

• Confirm private pages and API responses are not cached across users.
• Verify logged-out, expired, and unenrolled customers cannot create playback.
• Confirm HTML source contains no DRM-X Access Key or successful playback response.
• Exercise Stop, navigation, mobile backgrounding, and concurrent-stream limits.
• Update plugins through a controlled administrator process and retain a rollback copy.