Download the PHP package wazum/cache-guard without Composer
On this page you can find all versions of the php package wazum/cache-guard. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download wazum/cache-guard
More information about wazum/cache-guard
Files in wazum/cache-guard
Package cache-guard
Short Description Prevents backend cache flushes of protected cache groups in production-like contexts
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package cache-guard
Cache Guard
Deliberate cache control for TYPO3: protect the warmed system caches from destructive backend flushes between deployments, and flush precisely the caches you mean to. Editors keep clearing page caches, deployments keep flushing everything, and you can clear a single cache (e.g. fluid_template) instead of wiping the whole system group — while the bulk flush of warmed system caches stays locked in production.
Installation
No setup needed — the defaults lock the system cache group in Production contexts.
Locking system-cache flushes
Between deployments the warmed system caches (compiled PHP code, Fluid templates, l10n, …) should not be wiped by a stray backend click. Cache Guard prevents that in production-like contexts, while everyday page-cache clearing keeps working.
What it blocks
- Flushing of configured cache groups (default:
system) in configured application contexts (default:Production, matched as prefix, soProduction/Stagingis included). - The full opcache reset triggered by "Flush all caches"; targeted single-file opcache invalidation keeps working.
- It replaces the "Flush all caches" entry in the clear-cache toolbar with a disabled notice while the lock is active; the dropdown and "Flush frontend caches" stay in place.
[!NOTE] Intercepting the opcache reset requires TYPO3 13.4+ — on 12.4 the cache-group lock applies, but the opcache reset is not intercepted.
What it leaves alone
- "Flush frontend caches" (pages) keeps working for editors.
- CLI:
vendor/bin/typo3 cache:flushalways works — deployments are unaffected. - The Install Tool / Maintenance "Flush cache" and the DI container cache (system-maintainer territory).
- Tag-based invalidation (
flushCachesByTag/flushCachesByTags) — targeted invalidation is not a bulk clear.
Configuration
Admin Tools → Settings → Extension Configuration → cache_guard:
| Option | Default | Description |
|---|---|---|
lockedGroups |
system |
Comma-separated cache groups that must not be flushed from the backend |
lockedContexts |
Production |
Comma-separated application context prefixes in which the lock is active |
Defense in depth (optional)
Hide the "Flush all caches" entry per user/group via User TSconfig (UI only, the lock above is the actual enforcement):
Flushing individual caches (CLI)
Clear only specific caches without wiping a whole group — e.g. recompile Fluid templates after a deployment without touching the warmed PHP-code, l10n or DI caches:
All identifiers must be valid or nothing is flushed. The dependency injection cache is not flushable this way — use cache:flush --group di.
Run the option without a value (or with an unknown name) at a terminal to pick interactively:
In CI and deployment, pass --no-interaction (-n) so a missing or unknown identifier fails with a clear error instead of opening the picker:
Requirements
- TYPO3 12.4, 13.4 or 14.3
- PHP 8.2, 8.3, 8.4 or 8.5 (TYPO3 12.4 runs on 8.2–8.3)
License
GPL-2.0-or-later — see LICENSE.
All versions of cache-guard with dependencies
typo3/cms-core Version ^12.4 || ^13.4 || ~14.3.0
typo3/cms-backend Version ^12.4 || ^13.4 || ~14.3.0