Documentation / 7.5.1

Extension and lifecycle reference

Build separate extensions using the plugin’s documented lifecycle and integration contracts.

Build separate extensions using the plugin’s documented lifecycle and integration contracts.

How it works

CYBERMAPS is a complete standalone WordPress plugin. Its Extension API 2.0 exposes:

  • endpoint metadata registration;
  • read-only access to the final publication-eligibility service; and
  • read-only access to saved content report runs.

Extensions implement and route their own capabilities; CYBERMAPS retains ownership of its settings, tables, files, lifecycle, and public namespace.

Activation creates the required analytics, translation, and report storage, schedules log cleanup, adds rewrite rules, and initializes publication state. Relevant settings changes invalidate caches and schedule ownership-safe static reconciliation. Deactivation clears scheduled events and rewrite rules. It also removes unchanged CYBERMAPS-owned generated output; reactivation schedules restoration for the selected physical-publication mode.

Uninstall always clears scheduled hooks and attempts to remove unchanged CYBERMAPS-owned generated files. Persistent options, tables, and post metadata are removed only when Uninstall Cleanup was enabled beforehand. Edited and pre-existing files are retained.

The 6.0 data upgrade is an idempotent, stepwise transaction with a renewable owner lock, persisted step state, exponential retry backoff, and post-write verification. New installations are stamped at the current data version before defaults are created, while existing installations retain and normalize their configuration. The four structured configuration roots and operational coordination options are explicitly non-autoloaded.