Documentation

My UNA Doctor

Vendor: My UNA World
Module: my_una_doctor
Location: UNA Studio
Guide checked: 2 October 2026

My UNA Doctor reviews overall UNA health: environment compatibility, installed modules, maintenance/upgrade state, database/filesystem/cron/log findings and update readiness.

Installation

Use the supplied package and standard installation workflow. The module belongs at modules/newton/my_una_doctor/. Back up the site before installation, an update or a repair.

Run your first scan

  1. Open Studio → My UNA Doctor.
  2. Select Run Full Health Scan.
  3. Review the health percentage together with Critical, Warning and informational findings.
  4. Inspect compatibility, module integrity, maintenance and update-readiness details.
  5. Address each finding using its evidence and instructions.

A health percentage is a summary. It does not replace the individual findings or guarantee that an upgrade is safe.

Compatibility and updates

Doctor reads the installed UNA requirements, PHP extensions, module compatibility declarations and declared dependencies. Where supported, it also reviews official target metadata and limited evidence from a staged upgrade package.

Static package inspection is not a full upgrade rehearsal. An ordinary scan does not execute the target package's check.php. Record your current UNA and PHP versions before planning an update.

Reference comparisons and guarded repairs

Some versions provide a Module Reference Library. Store independently verified packages and review comparison evidence before proposing changes. Module Doctor provides the dedicated package intake and repair-package workflow.

Supported repair work proceeds through scan, preview, preflight, an armed plan, explicit confirmation, rollback evidence, mutation and validation. Controls and available rules depend on the installed version. A diagnostic difference alone does not authorize a repair.

Do not bypass a failed preflight or unresolved rollback journal. Keep the verified recovery point until the post-repair checks pass.

Runtime files and maintenance

Generated files inside a third-party module can affect update readiness. Do not add them to a source baseline just to hide drift. Use the supported protected workflow and recheck afterward.

Doctor distinguishes soft maintenance, hard locks, interrupted-upgrade evidence and protected repair state. Do not delete .bx_maintenance merely because it exists. Visitor Gate settings belong to My UNA World.

After an update

Run another full scan. Confirm the expected module version, UNA file/database version agreement, normal maintenance state and understood compatibility findings. Investigate unexplained tracked-file drift.

All guides · Support