Plugin Catalog And Package Compatibility

The plugin catalog helps operators discover packages and review their compatibility before installation. Catalog availability does not install, enable or approve a plugin automatically.

Check the package author, version, supported CMS/PHP versions, dependencies and release notes. Obtain the package from a trusted source and verify the supplied checksum when available. A checksum verifies file identity; it does not establish that a package is trustworthy.

Use the CMS plugin installation workflow. Installation, enablement, setup, updates and removal are separate operations with their own permission and dependency checks. Follow Plugin Ecosystem and Catalog and Plugin System for the supported contracts.

Plugins declare their owned blocks, administration surfaces, routes and dependencies through CMS extension points. A catalog listing does not promise an undeclared integration, future commercial licensing, third-party vendor onboarding or a particular payment provider. Use the package's current documentation and the target installation's discovery responses to confirm availability.

See Plugins for the available guides and installation requirements.