Requirements and responsibilities
Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: A learning site's update touches enrolment and lesson templates.
xCloud agent capability boundaries · WordPress roles and capabilities
Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Database restore could erase recent learner progress.
Before any database copy or restore starts, the authorized operator restricts the target and quarantines outbound mail, payment, fulfillment and other provider effects. Restored settings may overwrite plugin suppression; reapply sandbox credentials and verify isolation before testing.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: A learning site's update touches enrolment and lesson templates. Completion stays saved and instructor view matches learner view.
Choose the approach
Check progress persistence before and after the change with a test learner. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · Site Security PRO setup and eligibility
Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Record sample enrolment, lesson and expected state
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Record sample enrolment, lesson and expected state; exact site identity, named approver and controlled sample data.
- Action
- Select one learner, lesson, enrollment and completion state in the LMS before the WordPress change.
- Expected result
- The team has a before-state record.
- Verify
- The team has a before-state record. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If progress is not visible to the instructor, define the correct application view first.
Sources: WordPress roles and capabilities · Tutor LMS official documentation and course administration · Create a staging environment in xCloud
Step 2 of 5
Isolate staging effects before copying
- Where
- xCloud Staging Management dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Back up and stage the selected update; exact site identity, named approver and controlled sample data.
- Action
- Before copying learner data or provider settings, restrict staging access and quarantine outbound mail, payment and enrollment hooks at the receiving environment. If these controls are unavailable, do not copy the live database; use synthetic learners on a separately configured test site.
- Expected result
- Staging cannot contact real learners or payment providers during the rehearsal.
- Verify
- Staging cannot contact real learners or payment providers during the rehearsal. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If staging cannot isolate external events, use synthetic learners.
Sources: Create a staging environment in xCloud · xCloud agent capability boundaries · Tutor LMS official documentation and course administration
Step 3 of 5
Complete a lesson as test learner
- Where
- WordPress or selected plugin administrator
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Complete a lesson as test learner; exact site identity, named approver and controlled sample data.
- Action
- Apply only the selected LMS/plugin or template change to staging and record version.
- Expected result
- The test includes the intended change.
- Verify
- The test includes the intended change. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a vendor dependency is incompatible, hold production.
Sources: WordPress roles and capabilities · WordPress plugin administration · Tutor LMS official documentation and course administration · Create a staging environment in xCloud
Step 4 of 5
Verify progress in learner and instructor views
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Verify progress in learner and instructor views; exact site identity, named approver and controlled sample data.
- Action
- Complete a lesson as test learner, sign out and return; compare learner and instructor views.
- Expected result
- Progress persists in both expected views.
- Verify
- Progress persists in both expected views. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the progress resets, inspect LMS storage and session behavior before release.
Sources: WordPress roles and capabilities · Tutor LMS official documentation and course administration · Create a staging environment in xCloud
Step 5 of 5
Release, monitor and reconcile newer progress if recovering
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Release, monitor and reconcile newer progress if recovering; exact site identity, named approver and controlled sample data.
- Action
- After production release repeat with a new test learner and preserve newer completions before any database restore.
- Expected result
- Real learner data is not discarded during recovery.
- Verify
- Real learner data is not discarded during recovery. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a rollback is needed, reconcile enrolled students and progress after backup time.
Sources: WordPress roles and capabilities · Tutor LMS official documentation and course administration · Create a staging environment in xCloud
Maintenance
Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: Completion stays saved and instructor view matches learner view. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud
Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone.
Recovery decisions
If progress differs, preserve the current learner and instructor records before choosing a forward fix or restore. Keep staging mail, payment and enrollment hooks quarantined throughout; reconcile completions added after the backup.
Tutor LMS official documentation and course administration · Site backups in xCloud
AI handoff
Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Review a WordPress business journey app · manual
Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence.
Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision.
- Create and synchronize WordPress staging dashboard · manual
WordPress staging requires an eligible paid plan. The API staging-create operation is for Git sites.
Checkpoint: Use Site overview → Add Staging and staging Site → Manage Staging. Inspect push/pull scope before overwriting data.
- Configure WordPress content, users and selected plugins app · manual
Requires a named WordPress administrator or suitable editor. Plugin behavior, commercial license, payment, email and external integration are verified in the chosen vendor documentation and application; xCloud hosting or MCP reads do not configure them.
Checkpoint: Open the actual WordPress or selected plugin interface, record the version and role, and have the business owner accept a real user journey.
WordPress roles and capabilities · WordPress plugin administration
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Apply only the selected LMS/plugin or template change to staging and record version.
- The business owner compares the controlled sample with this observable result: Progress persists in both expected views.
- Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only.
Feature coverage
- business-acceptance (covered): Completion stays saved and instructor view matches learner view. Verify progress in learner and instructor views
- recovery (covered): Database restore could erase recent learner progress. Release, monitor and reconcile newer progress if recovering
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- Create a staging environment in xCloud
- xCloud MCP documentation and connection profiles
- Site Security PRO setup and eligibility
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Tutor LMS official documentation and course administration