Caching in Vvveb CMS works across several layers to keep the system fast while still allowing editors and developers to update content reliably. Each cache type serves a different purpose, and understanding how they interact helps you diagnose why changes may not appear immediately and which cache to clear in each situation.

How caching works in Vvveb

Vvveb caches pages, assets, database queries, images, and compiled templates to reduce server load and speed up page delivery. Most caches are cleared automatically when content changes, for example, saving a post or product triggers invalidation of related cached data. In more advanced scenarios, or when working with custom themes, plugins, or SQL models, you may need to clear specific caches manually.

Cache types and when to clear them

Frontend assets cache

This cache stores optimized versions of CSS and JavaScript files, including minified and combined assets. Clear this cache when:

  • Updating theme CSS or JS files
  • Changing plugin assets
  • Modifying build pipelines or asset loaders

This ensures browsers receive the latest versions instead of stale cached files.

Compiled templates

Vvveb automatically converts HTML theme files into PHP templates for faster rendering. These compiled templates are stored and reused until the source HTML changes. Clear this cache when:

  • Editing theme HTML files
  • Switching themes
  • Updating template structure or Vtpl rules

Clearing forces regeneration of all compiled templates so changes appear immediately.

Database cache

Database queries and content results are cached to reduce repeated lookups. Clear this cache when:

  • Content changes in the admin do not appear on the frontend
  • Custom SQL queries or models are updated
  • Plugins modify database-driven components

This ensures the site displays the most recent data.

Full page cache

When full page caching is enabled, Vvveb stores the entire rendered HTML of a page for maximum performance. Clear this cache when:

  • Page content does not update after edits
  • Theme changes are not reflected
  • Dynamic components appear outdated

This is the most aggressive cache layer and often the reason changes do not appear immediately.

Image resize cache

Images are automatically resized into multiple versions (thumbnail, medium, large, etc.) for different parts of the site. Clear this cache when:

  • Updating product or post images
  • Changing image sizes in theme templates
  • Replacing existing images with new ones of the same filename

Clearing forces regeneration of all resized images.

Model cache

Models generated from SQL files are cached for performance. This cache is primarily used by developers. Clear this cache when:

  • Editing SQL model definitions
  • Adding new fields or tables
  • Updating plugin SQL files

If you are not modifying SQL files, you generally do not need to clear this cache.

Caching is one of the key performance features in Vvveb, and knowing which cache to clear helps keep your site fast while ensuring updates appear correctly.