Details

    • Sprint:
      Ventoux Sprint 5

      Description

      SiteAccess services state changes during the request lifecyle as it is matched during the beginning of the request life. This makes services that depend on it (e.g. ConfigResolver) not to have the proper instance/state (a new instance is created when siteaccess is matched).

      Solution for this is to make it a synchronized service.

      See http://symfony.com/doc/current/cookbook/service_container/scopes.html#a-using-a-synchronized-service

        Issue Links

          Activity

          Show
          Jérôme Vieilledent (Inactive) added a comment - PR: https://github.com/ezsystems/ezpublish-kernel/pull/718
          Show
          Jérôme Vieilledent (Inactive) added a comment - Implemented in master: https://github.com/ezsystems/ezpublish-kernel/commit/16ace1ee1a1e87b1db08107271c68309dea3f86a

            People

            • Assignee:
              Unassigned
              Reporter:
              Jérôme Vieilledent (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Time Spent - 4 hours Remaining Estimate - 1 day, 4 hours
                1d 4h
                Logged:
                Time Spent - 4 hours Remaining Estimate - 1 day, 4 hours
                4h

                  Agile