Package identity
- Handle:
webblocks-redirect-manager - Version: 0.1.25
- Type: CMS plugin
- License: MIT
Technical reference
WebBlocks Redirect Manager documentation
Create and manage simple 301 and 302 redirects from the WebBlocks CMS admin area.
Values below come from the current package manifest and Composer metadata.
Runtime requirements
- Current version: 0.1.25
- Host product: WebBlocks CMS
- CMS compatibility: ^1.32
- PHP: >=8.1
- License: MIT
- Catalog status: Public catalog plugin
Installation is disabled-by-default and setup remains an explicit operator action.
- Open System → Plugins in a compatible WebBlocks CMS installation.
- Install the catalog release or upload its validated ZIP artifact.
- Review the manifest, compatibility and permissions before enabling it.
- Enable the plugin, then run explicit plugin setup or migrations when health reports that setup is required.
- Confirm plugin health and complete product-specific settings before exposing its public workflow.
Updates: review release notes and compatibility first. Package replacement must not silently enable the plugin or run migrations.
Inspectable behavior contributed to the host product.
Registered surfaces
- Admin and internal API routes
- Public GET/HEAD fallback
- Plugin health reporter
- One plugin-owned table
Permissions
webblocks-redirect-manager.viewwebblocks-redirect-manager.manage
The public contract describes ownership without exposing secrets or private implementation details.
Data ownership
Owns webblocks_redirect_manager_redirects with source, target, status, enabled state, hit count and last-hit timestamp. Unmatched and protected namespaces bypass redirect evaluation.
Security model
Write operations validate unique normalized paths, URL schemes, status codes and self-target loops. Non-GET/HEAD requests are never redirected.
Disable and uninstall
Disabling makes plugin-owned routes, menus, blocks and behavior inert. Run migrations explicitly after compatible updates. Before uninstalling, export or back up plugin-owned data; package removal and data removal are separate lifecycle decisions.
Health and troubleshooting
Start with the plugin detail screen and health result. Confirm compatibility, required migrations, host services, scheduled commands and external-provider configuration before inspecting application logs.
What exists in the local package today, and what should be expanded next.
Current source set: README, changelog and catalog metadata notes.
Runtime behavior is unusually explicit; add an operator-focused migration and redirect-testing guide.