Documentation

Albums LightGallery Getting started My UNA Doctor My UNA Finances My UNA Mail Doctor My UNA Module Doctor My UNA Stream Doctor My UNA Tickets My UNA World README RELEASE 0.5.0 RELEASE 0.5.1 Troubleshooting and support Wiki Home

My UNA Module Doctor

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

Module Doctor reviews module archives, keeps verified reference packages, compares them with installed modules and prepares controlled repair workspaces and repaired packages.

Install and open

Use the release's installable module ZIP and checksum, following Getting started. The module folder is modules/newton/my_una_module_doctor/. Open Studio → My UNA Module Doctor.

The working areas include Overview, Module Reference Library and Repaired Packages. Available actions depend on the installed build.

Add a reference

  1. Open Module Reference Library.
  2. Upload the module ZIP you want to review.
  3. Read the intake result. Correct missing structure, invalid metadata or unsupported package layout before proceeding.
  4. Verify the accepted package and record its SHA-256 identity.
  5. Confirm its internal module name and version match the module you intend to compare.

Use an independently known-good package as the reference. An archive copied from a modified live installation is not automatically a clean baseline. A full installer and a version-to-version updater have different purposes.

Compare an installed module

Choose the reference and run the offered comparison. Review metadata, source files, classes, registrations, compatibility and SQL declarations.

Classify modified, missing and extra files. Some extra files may be generated runtime data; a difference does not by itself prove corruption. Keep comparison and verification evidence with the package identity.

Plan a controlled repair

Start with a verified backup. Review the proposed repair plan and any preflight findings. Where the installed build offers a protected repair workspace, verify its identity and the exact proposed operations before confirming them.

A repaired package is a separate artifact. Review its validation, download or publish result and intended import/install target. Importing files is not equivalent to a completed native UNA installation or update.

Manage packages

Use the library's explicit deletion control when a stored upload is no longer needed. Check the package identity and keep any copy needed for recovery. Removing a library upload must not be confused with uninstalling a live module.

Troubleshooting

If an upload is rejected, check the package's top-level layout, install/config.php, internal name, version and checksum. If an import or repair fails, preserve the result and rollback evidence; do not repeatedly overwrite the module.

A corrected local Studio icon does not automatically repair the remote Marketplace Info popup.

All guides · Support