Package identity
- Handle:
webblocks-quiztem - Version: 0.3.2
- Type: CMS plugin
- License: Proprietary
Technical reference
WebBlocks QuizTem documentation
Build CMS-managed QuizTem catalogues, collection pages and quiz introductions from live QuizTem data.
Values below come from the current package manifest and Composer metadata.
Runtime requirements
- Current version: 0.3.2
- Host product: WebBlocks CMS
- CMS compatibility: ^1.82.0
- PHP: >=8.3
- Additional requirement: QuizTem >=1.22.2
- License: Proprietary
- Catalog status: Product integration
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 routes
- Three system block types
- QuizTem Content Source
- Public presentation stylesheet
Permissions
webblocks-quiztem.viewwebblocks-quiztem.manage
The public contract describes ownership without exposing secrets or private implementation details.
Data ownership
QuizTem remains the source of truth for quizzes, attempts and results. CMS remains the source of truth for pages, navigation, shared slots, SEO and media.
Security model
The plugin reads only QuizTem's public contracts and never queries QuizTem tables directly. Secure quiz attempts and results remain in QuizTem.
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 architecture notes.
Architecture ownership is clear; installation and troubleshooting deserve dedicated public pages.