Skip to content
mcorucu docs
mcLogiora0.16.0
0.16.01 min read

Hooks & Filters

Extend mcLogiora through supported WordPress hooks without relying on internal classes.

The supported extension surface is documented in the canonical repository’s developer API reference. Presence in source does not make an internal action or filter public; only hooks with a published contract and @since marker are supported.

Extension principles

  • Depend on mclogiora_ functions and documented hook payloads, not service-container classes.
  • Treat returned arrays as additive contracts: new keys may appear; existing keys should not be renamed or removed.
  • Apply your own capability and visibility checks before rendering IDs returned by a read function.
  • Keep builder and SEO integrations optional and dormant unless the site has opted into them.
  • Do not register a provider or call a provider from a front-end request unless the product contract explicitly allows it.

Adapter boundary

The editor adapter foundation is not a license to rewrite arbitrary builder storage. Use the supported payload-adapter seam for translation-aware integrations and keep source content immutable during read and review flows.

Related articles

Editor IntegrationsUnderstand Classic Editor, Block Editor, Elementor, and compatibility boundaries.Public PHP APIUse the stable mclogiora_ read functions and language switcher template tags.Security ModelUnderstand permissions, nonces, source immutability, and provider boundaries.