Global navigation

   Documentation Center
   eZ Studio & eZ Platform
     User Manual
     Technical Manual
     Glossary
   eZ Publish 4.x / legacy

 
eZ Publish (5.x)

eZ Publish 5.x | For eZ Platform & eZ Studio topics see Technical manual and User manual, for eZ Publish 4.x and Legacy topics see eZ Publish legacy

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

During Setup wizard and manually using ezpublish:configure console command a default configuration is generated currently using FileSystem, using %kernel.cache_dir%/stash to store cache files. It falls back to BlackHole, a non caching cache handler.

The configuration is placed in ezpublish/config/ezpublish.yml, and looks like:

...

If you want to change to another handler, see in Stash handlers configuration below for what kind of settings you have available.

As cache configuration is global to the application, it's currently not possible to have different cache configuration by siteaccess. As such, when having multiple websites using different content repositories, you must only use the BlackHole handler with inMemory caching:

stash:
Note
titleNote for multiple sites installation
Code Block
"inMemory" cache with long running scripts

Use of inMemory caching with BlackHole or any other cache handler should not be used for long running scripts as it will over time return stale data, inMemory cache is not shared across requests/processes, so invalidation does not happen!

Multi repository setup

New in 5.2 is the possibility to select a specific Stash cache pool on a siteaccess or sitegroup level, the following example shows use in a sitegroup:

Code Block
titleezpublish.yml site group setting
     
caches:
   
default
ezdemo_group:
            
handlers
cache_pool_name: 
[BlackHole]
"default"
            
inMemory
database:
true
             
registerDoctrineAdapter: false

This will result to the same persistence cache strategy as in eZ Publish 4.x.

Note
titleNote for "inMemory" cache with long running scripts
Use of inMemory caching with BlackHole or any other cache handler should not be used for long running scripts as it will over time return stale data (inMemory cache is not shared across requests/processes, so invalidation does not happen)!
   ...

"default" here refers to the name of the cache pool as specified in the stash configuration block shown above, if your install has several repositories (databases), then make sure every group of sites using different repositories also uses a different cache pool to avoid unwanted effects. NB: We plan to make this more native in the future, so this setting will someday not be needed.

Stash handlers configuration

...