Lifecycle, Security, and Troubleshooting

Lifecycle

Activation provisions Core schema and schedules required work.

Deactivation unschedules work and attempts an ownership-safe static purge.

Uninstall removes persistent Core data only when Delete data on uninstall was explicitly enabled.

Administration security

Administrative actions require manage_options and nonces. Request values are sanitized and output is escaped for its context.

Static writes use WP_Filesystem. Cybermaps does not overwrite or delete a target whose current content differs from its recorded ownership hash.

An endpoint works but the Request Log is empty

  1. Confirm recording is enabled under Discovery Analytics → Data Controls.
  2. Check AI Discovery Status for intended and observed delivery.
  3. Request a dynamic alias such as /ai.json.
  4. Confirm the request reached PHP and the analytics table is healthy.
  5. Remember that diagnostic probes are excluded.
  6. Remember that physical-file, CDN, page-cache, and web-server responses bypass PHP.

A well-known endpoint fails

  1. Inspect its owned-file and reconciliation state.
  2. Confirm the resolved public origin document root.
  3. Inspect nginx, OpenLiteSpeed, or Apache well-known rules.
  4. Validate the public media type.
  5. For RFC 9727, validate the profile parameter and required Link header.

Disk existence is not proof of correct public delivery.

Reconciliation reports a conflict

A conflict normally means the target existed before Cybermaps owned it or its content changed after publication.

Review the file manually. Cybermaps retains it instead of overwriting or deleting it. Remove or relocate the conflicting file only after deciding which publisher should own the route, then regenerate.

Multisite does not write static files

This is intentional. Each site resolves the Static File Engine to off so multiple sites do not compete for shared web-root filenames.