Overview

GeoHazardWatch caches rendered page content and other frequently accessed data in memory to improve response times. Administrators can flush all caches at once or evict a single page without affecting the rest.

When to Clear Cache

Clear the cache when:

A template, plugin, or layout change is not reflecting on existing pages
A page file was edited directly on disk (outside the editor UI)
Required pages have been updated and the changes are not visible
Stale search results appear after editing or deleting pages
An administrator has changed system configuration that affects page rendering

Normal page edits through the UI automatically invalidate the cache for the affected page, so manual clearing is rarely needed.

Clearing All Caches

Go to Admin → Clear Cache
Confirm the action when prompted
The server clears all in-memory caches and displays a confirmation message

The operation is fast and does not require a server restart. Users may notice slightly slower page loads briefly while caches are rebuilt.

Clearing a Single Page Cache

To evict one page without flushing everything, use the API endpoint:

POST /api/admin/cache/clear/page/{identifier}

Where {identifier} is the page UUID, slug, or title. Requires an active admin session.

Example using curl (replace the UUID and cookie):

curl -X POST https://yoursite/api/admin/cache/clear/page/b06973bc-56c2-4da0-8702-08408de8c207 \
  -H "Cookie: connect.sid=your-session-id"

Response:

{ "success": true, "evicted": true, "identifier": "b06973bc-..." }

evicted: false means the page was not in the cache (no action needed).

What Is Cleared

Scope	Clears
All caches (Admin UI)	Rendered page HTML, plugin output, template fragments
Single page (API)	Provider content cache entry for that page only

The page index, search index, and user sessions are not affected by either operation.