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

Current Content version loading can end up loading wrong version under concurrency

    XMLWordPrintable

    Details

      Description

      Common symptom:
      For not logged in users this will result in login screen, if logged in you'll get permission error or missing content.


      Context:
      In API when loading content in current version, that is done in two steps, first loading content info, then content.

      There are many reports that under concurrency this can lead to wrong version being loaded which makes API check for content/versionread which will throw UnauthorizedException exception.


      Possible solution:

      • Change SPI to allow direct loading of current version, and use that in ContentService
      • 6.13 and up: adapt ContentService::loadContentByContentInfo and Persistence\Cache\ContentHandler::deleteTranslationFromDraft for this

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              andre.romcke@ez.no André Rømcke
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: