Managing the Cache Directory
WP-ImmoMakler stores various generated files under wp-content/cache/immomakler/ so they do not need to be regenerated on every page load. This page explains what is stored there, how to set the size limit, and how to clear the cache completely when needed.
What is in the Cache
Section titled “What is in the Cache”The cache directory contains exclusively regenerable data. You can delete its contents at any time without data loss — missing files are automatically recreated on the next request.
| Subdirectory | Contents | Edition |
|---|---|---|
pdf/pdfs/ | Generated PDF print views per property | PLUS |
pdf/fonts/ | Dompdf font metrics cache (very small, required during rendering) | PLUS |
pdf/images/ | Converted images for PDF generation (e.g. AVIF → JPEG) | PLUS |
tmp/pdf/ | Temporary Dompdf files during PDF rendering | PLUS |
public/maps/ | Pre-generated static Google Maps images | PLUS |
fast-api/ | Generated proxy script for address autocomplete in radius search | PLUS |
User Interface
Section titled “User Interface”Management is done in your website’s backend (wp-admin) under WP-ImmoMakler → System Info, in the row WP-ImmoMakler Storage Used.
You will find:
- Current Size Display – Total size with a breakdown by photos/attachments, transfer files, and cache. Marker files (
.htaccess,index.html) are not counted. - Refresh – Recalculates the sizes without reloading the page.
- Clear Cache – Deletes the entire
wp-content/cache/immomakler/directory. A confirmation prompt must be accepted. - Cache Limit – Dropdown with options 500 MB, 1 GB, 5 GB, 10 GB, 25 GB, 50 GB, 100 GB, and “Unlimited”. The default is 1 GB. The selection is saved immediately when changed.
How the Size Limit is Enforced
Section titled “How the Size Limit is Enforced”When you select a limit other than “Unlimited”, a background job runs hourly to check whether the cache has grown too large. If the limit is exceeded, the oldest regenerable files are deleted until the total size falls back below the limit.
When saving a new, lower limit, the cleanup is executed immediately — you do not need to wait for the next hourly run.
The following contents are excluded from automatic cleanup so that your website’s functions are not affected:
pdf/fonts/– the font metrics are required during every PDF render and are only a few kilobytes in size.fast-api/– the radius search address autocomplete proxy script is not regenerated once it has been removed..htaccessandindex.html– protection files against directory listings on Apache and Nginx.
When Should I Clear the Cache?
Section titled “When Should I Clear the Cache?”In most cases, manual cleanup is not necessary — the automatic size control handles it. A complete clear via the Clear Cache button is useful when:
- You expect an immediately updated print view after updating the PDF template and do not want to wait until the old cached version is replaced through regular operation.
- You are troubleshooting storage space issues on the server and want to permanently set a lower limit.
- Support asks you to do so for diagnostic purposes.
Protection Against Unauthorised Access
Section titled “Protection Against Unauthorised Access”WP-ImmoMakler automatically creates an .htaccess file in protected cache subdirectories that blocks direct access to individual files on Apache. Since Nginx does not process .htaccess, an empty index.html is additionally placed in each directory to prevent directory listings.
Full access protection for individual files cannot be implemented under Nginx via the plugin. If required, you can add a corresponding location block in your server configuration that blocks wp-content/cache/immomakler/ (except the public/ subdirectory) for external requests.
Storage Location and Paths
Section titled “Storage Location and Paths”| Path | Meaning |
|---|---|
wp-content/cache/immomakler/ | Root directory of the cache |
wp-content/cache/immomakler/public/ | Publicly accessible content (e.g. maps); no .htaccess access protection |
wp-content/cache/immomakler/fast-api/ | Radius search proxy script; must remain accessible from the web |
In multisite installations, each site receives its own subdirectory under fast-api/{blog_id}/.