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

[Symfony 2.8] First load doesn't load the configuration

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.4.5, 2015.11.2, 1.3.0
    • Fix Version/s: 5.4.7, 1.4.0-beta1
    • Component/s: Platform stack
    • Labels:
      None

      Description

      It seems there is an issue with current beta of eZ Platform and Symfony 2.8.

      First load after clearing the caches (with rm -rf) does not load the configuration properly. Presumably, semantic configuration for current siteaccess is not correctly recognized.

      Every subsequent load works fine.

      This does NOT happen on Symfony 2.7.

      EDIT: This also does not happen on 2014.11 when hacked to run Symfony 2.8.

      To reproduce:

      1) Install dev-master of ezplatform. This will automatically install Symfony 2.8.

      2) Clear caches with rm -rf ezpublish/cache/*. DO NOT run cache:clear.

      2) Add a bogus content_view rule to ezpublish/config/ezplatform.yml. The purpose of the rule is to specify non existing template, which means that we should get an exception.

      ezpublish:
          system:
              site_group:
                  content_view:
                      full:
                          folder:
                              template: 'non_existing'
                              match:
                                  Identifier\ContentType: [folder]
      

      3) Open the frontpage and notice that the page is loading fine and the exception is NOT thrown, which means that our rule is not correctly loaded first time. Only subsequent loads throw the exception.

        Issue Links

          Activity

          Hide
          André Rømcke added a comment -

          Ok, seems like this is the same issue as we have had in 5.x all along as when every time a service depending on SiteAccess direct or indirect needs to be lazy (or avoid loading it) to not cause issue if inited before SiteAccess is.

          We still need better protection against this, and 2.8 seems to just make that even more obvious.

          Show
          André Rømcke added a comment - Ok, seems like this is the same issue as we have had in 5.x all along as when every time a service depending on SiteAccess direct or indirect needs to be lazy (or avoid loading it) to not cause issue if inited before SiteAccess is. We still need better protection against this, and 2.8 seems to just make that even more obvious.
          Show
          Jérôme Vieilledent added a comment - New PR: https://github.com/ezsystems/ezpublish-kernel/pull/1666
          Hide
          Bertrand Dunogier added a comment -

          7afb420 merged to 6.1, 6.2, 6.3 and master.

          Show
          Bertrand Dunogier added a comment - 7afb420 merged to 6.1, 6.2, 6.3 and master.
          Hide
          André Rømcke added a comment - - edited

          QA: You should now be able to test Symfony 2.8 when using dev-master (aka ~1.4.0@dev) of eZ Platform and eZ Platform demo.
          https://github.com/ezsystems/ezplatform/commit/8da8196331a2acf159bee3de1571a6dd33588df7
          https://github.com/ezsystems/ezplatform-demo/commit/8da8196331a2acf159bee3de1571a6dd33588df7

          Show
          André Rømcke added a comment - - edited QA: You should now be able to test Symfony 2.8 when using dev-master (aka ~1.4.0@dev ) of eZ Platform and eZ Platform demo. https://github.com/ezsystems/ezplatform/commit/8da8196331a2acf159bee3de1571a6dd33588df7 https://github.com/ezsystems/ezplatform-demo/commit/8da8196331a2acf159bee3de1571a6dd33588df7
          Hide
          Rui Silva (Inactive) added a comment -

          This issue, much like on version 5.4, could not be reproduced on an updated 6.3, on several tries.
          Sanity tests were executed on the scope, with the latest fix and no issues were found. Error 500 happens as expected right away on first load of content with contentView rule matching a non-existing template.
          Latest fix was also tested on sanity scope on master (since previous fix already fixed it) and nothing is broken.
          Approved by QA for 6.3 and master.

          Show
          Rui Silva (Inactive) added a comment - This issue, much like on version 5.4, could not be reproduced on an updated 6.3, on several tries. Sanity tests were executed on the scope, with the latest fix and no issues were found. Error 500 happens as expected right away on first load of content with contentView rule matching a non-existing template. Latest fix was also tested on sanity scope on master (since previous fix already fixed it) and nothing is broken. Approved by QA for 6.3 and master.

            People

            • Assignee:
              Unassigned
              Reporter:
              Edi Modrić
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: