Details

      Description

      The eZ admin has significant stability issues. These are thought to relate to session time out issues but result in generic failure messages in the Admin.

      Example error screens are attached. We feel that the errors occur more frequently when users session lengths are higher.

      The feeling is that the underlying cause of these stability issues are loss of session - resulting in the application failing. The issues can be replicated by spending ~ 1 hour on eZ admin. The exact steps differ, as underlying reason does not seem to relate to specific tasks.

      This issue results in users losing work, failures to publish content and is a critical issue in a fast moving media environment.

        Issue Links

          Activity

          Hide
          Bertrand Dunogier added a comment - - edited

          It is not a duplicate, Paulo Nunes. It can be seen as related, since it affects sessions expiration, but it's still a long shot.

          Show
          Bertrand Dunogier added a comment - - edited It is not a duplicate, Paulo Nunes . It can be seen as related, since it affects sessions expiration, but it's still a long shot.
          Show
          Bertrand Dunogier added a comment - - edited Kernel https://github.com/ezsystems/ezpublish-kernel/pull/1769 merged to: 6.4@37e75da . 6.5@22c407a master@1806bf2 . Platform UI Fix for 1.4, 1.5 and master: https://github.com/ezsystems/PlatformUIBundle/commit/05f34de0acaf4f774fc6ebc94cb85f5c510b4680 https://github.com/ezsystems/PlatformUIBundle/commit/0aab4856a924b02982a37f942a42546c59ee9ee0
          Hide
          Bertrand Dunogier added a comment -

          As André has explained, 1.5 needs whatever happens to be merged into master. As far as I can recall when speaking with Damien, the fix for master is an improved version of the maintenance one.

          I had the same situation with the REST side, and I have created a distinct improvement for it (https://jira.ez.no/browse/EZP-26329, related to this issue).

          Show
          Bertrand Dunogier added a comment - As André has explained, 1.5 needs whatever happens to be merged into master. As far as I can recall when speaking with Damien, the fix for master is an improved version of the maintenance one. I had the same situation with the REST side, and I have created a distinct improvement for it ( https://jira.ez.no/browse/EZP-26329 , related to this issue).
          Hide
          Yannick Roger (Inactive) added a comment -

          I merged 1.5 into master on Platform UI and created a follow up for 1.6 assigned to Damien EZP-26332

          Show
          Yannick Roger (Inactive) added a comment - I merged 1.5 into master on Platform UI and created a follow up for 1.6 assigned to Damien EZP-26332
          Hide
          Rui Silva (Inactive) added a comment -

          Tested and approved by QA for 6.4, 6.5 and master.
          Specific tests for the frontend scenarios could not be run, so sanity tests were executed in general on sessions for these versions.

          Show
          Rui Silva (Inactive) added a comment - Tested and approved by QA for 6.4, 6.5 and master. Specific tests for the frontend scenarios could not be run, so sanity tests were executed in general on sessions for these versions.

            People

            • Assignee:
              Unassigned
              Reporter:
              Mark Cotton
            • Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: