Uploaded image for project: 'Magnolia Personalization'
  1. Magnolia Personalization
  2. MGNLPN-189

Remove personalisation-specific cache configuration

    Details

    • Type: Task
    • Status: Closed
    • Priority: Neutral
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1
    • Component/s: Integration
    • Labels:
    • Magnolia Release:
      5.3.6

      Description

      1. Update dependency to cache 5.3
      2. Add update task to use default cache configuration classes again.
      3. Deprecate classes which were merged into cache:
      • info.magnolia.personalization.cache.BypassUncacheableEntriesPolicy
      • info.magnolia.module.cache.filter.UncacheableEntry
      • Instead of info.magnolia.personalization.cache.BypassVariantsCacheStore, it should be enough to set "Cache-control" header to "no-cache" e.g. in VariantResolver filter if it detects a variant.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rkovarik Roman Kovařík
                Reporter:
                rkovarik Roman Kovařík
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: