Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-28888

Custom cache_service_name can not be set from siteaccess group

    Details

    • Sprint:
      [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>
      

        Issue Links

          Activity

          Hide
          André Rømcke added a comment -
          Show
          André Rømcke added a comment - PR ready for testing: https://github.com/ezsystems/ezpublish-kernel/pull/2420
          Hide
          David Wulf added a comment -

          Hi André

          this bug is currently a blocker for our ez 2.0 migration. We heard that it is currently being qs-ed. Can you confirm?

          Thank you
          David

          Show
          David Wulf added a comment - Hi André this bug is currently a blocker for our ez 2.0 migration. We heard that it is currently being qs-ed. Can you confirm? Thank you David
          Hide
          André Rømcke added a comment -

          Hi,

          this was released some time ago in ezpublish-kernel 7.2.3:
          https://github.com/ezsystems/ezpublish-kernel/releases/tag/v7.2.3

          FYI In the mean time 7.2.4 is also out:
          https://github.com/ezsystems/ezpublish-kernel/releases/tag/v7.2.4

          And so are a few other fixes as part of eZ Platform 2.2.3:
          https://github.com/ezsystems/ezplatform/releases/tag/v2.2.3
          https://github.com/ezsystems/ezplatform-ee/releases/tag/v2.2.3

          Hope this helps with your migration

          Best,
          André

          Show
          André Rømcke added a comment - Hi, this was released some time ago in ezpublish-kernel 7.2.3: https://github.com/ezsystems/ezpublish-kernel/releases/tag/v7.2.3 FYI In the mean time 7.2.4 is also out: https://github.com/ezsystems/ezpublish-kernel/releases/tag/v7.2.4 And so are a few other fixes as part of eZ Platform 2.2.3: https://github.com/ezsystems/ezplatform/releases/tag/v2.2.3 https://github.com/ezsystems/ezplatform-ee/releases/tag/v2.2.3 Hope this helps with your migration Best, André

            People

            • Assignee:
              Unassigned
              Reporter:
              Ramzi Arfaoui
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile