Details
-
Bug
-
Resolution: Done
-
High
-
2.0.0, 2.1.0, 2.2.1, 2.2.2
-
[2.3] Sprint 5
Description
When using a custom CacheAdapter (or using another cache lke redis) and configure it in a siteaccess group for multiple sites, then the siteaccess will still use the default cache.app and the cache_service_name is not taken from the group setting.
ezpublish:
siteaccess:
list: [admin, site1, site2]
groups:
admin_group: [admin]
frontend_group: [site1,site2]
system:
frontend_group:
cache_service_name: 'cache.redis'
site1:
pagelayout: 'pagelayout.html.twig'
Only when we specify again the cache_service_name in the siteaccess site1 , then the new cache will be used.
Here some debug info from cache/dev/appDevDebugProjectContainer.xml:
with group + siteaccess setting: <parameter key="ezsettings.frontend_group.cache_service_name">cache.redis</parameter> <parameter key="ezsettings.site1.cache_service_name">cache.redis</parameter> with only group setting: <parameter key="ezsettings.frontend_group.cache_service_name">cache.redis</parameter> <parameter key="ezsettings.site1.cache_service_name">cache.app</parameter>
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-