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

version history limit is not effective with multiple languages

    Details

    • Type: Feature Feature
    • Status: Declined
    • Priority: High High
    • Resolution: Obsolete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      In the case of a massively-multilanguage site, it is common to increase the versionhistorylimit setting, to allow editors to have multiple versions open at the same time.

      Ex:

      • 10 languages defined for content
      • create a draft in each language
      • try to create a 2nd draft in any language => fail, as we already have too many versions created (default version history limit set at 10)

      This is solved by increasing version DefaultVersionHistoryLimit or its per-class equivalent.

      The problem is that this means that a huge number of content versions will be kept in the database, even when the version cleanup cronjobs are scheduled.
      And since there are many languages, this means a lot of rows in the attribute table - real life example: 2500 objects, 32 langauges, 50 max versions, 16M attributes.

      Ideally, the user should be able to configure the system so that:

      • it allows creation of multiple drafts, maybe limiting the number of drafts per-language (instead of having a number of total drafts and without counting archived versions)
      • it still can automatically remove most archived versions, keeping only a few

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Gaetano Giunta (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: