Details

    • Sprint:
      Stetind Sprint 7

      Description

      Creating a new content in ezdemo_admin only appears in forntend if you disable firefox/chorme browser cache
      Used tc-1355

        Issue Links

          Activity

          Show
          Damien Pobel (Inactive) added a comment - Pull requests: https://github.com/ezsystems/ezpublish-kernel/pull/266 https://github.com/ezsystems/DemoBundle/pull/3
          Show
          Damien Pobel (Inactive) added a comment - Fixed in ezpublish-kernel: master: http://github.com/ezsystems/ezpublish-kernel/commit/06b7d29c24c834a2559915e7fe40704f10c9a9b7 Fixed in DemoBundle: master: http://github.com/ezsystems/DemoBundle/commit/ee16772443dc6bf0154ac72ca6c10f7cd850c39e
          Hide
          Matthieu Sévère added a comment -

          Does it means that HTTP Cache is not available anymore until this E-tag generator ?

          Show
          Matthieu Sévère added a comment - Does it means that HTTP Cache is not available anymore until this E-tag generator ?
          Hide
          Damien Pobel (Inactive) added a comment -

          You can still configure the HTTP cache based on the expiration as explained on confluence https://confluence.ez.no/display/EZP/HttpCache

          Show
          Damien Pobel (Inactive) added a comment - You can still configure the HTTP cache based on the expiration as explained on confluence https://confluence.ez.no/display/EZP/HttpCache
          Hide
          Matthieu Sévère added a comment -

          Ok, but this type of cache is not refreshed when we modify or create a content, right ?
          I mean by opposition with the view cache which is refreshed when the content is modified.

          Show
          Matthieu Sévère added a comment - Ok, but this type of cache is not refreshed when we modify or create a content, right ? I mean by opposition with the view cache which is refreshed when the content is modified.
          Hide
          Damien Pobel (Inactive) added a comment -

          Since, our controller sets the header X-Location-Id and we implemented a cache purger based on this, even when setting the cache_ttl configuration the cache can be correctly refreshed provided you configured the cache correctly with the good old viewcache.ini.

          Show
          Damien Pobel (Inactive) added a comment - Since, our controller sets the header X-Location-Id and we implemented a cache purger based on this, even when setting the cache_ttl configuration the cache can be correctly refreshed provided you configured the cache correctly with the good old viewcache.ini.
          Hide
          Matthieu Sévère added a comment -

          Great, I'll try this !

          Thank you !

          Show
          Matthieu Sévère added a comment - Great, I'll try this ! Thank you !

            People

            • Assignee:
              Unassigned
              Reporter:
              Joao Pingo (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 hours Original Estimate - 4 hours
                4h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 7 hours, 30 minutes
                1d 7h 30m

                  Agile