Skip to content

Fix migration for content group publish range

Daniel Gerhardt requested to merge fix-content-group-publish-range-migration into master

There were two issues:

  • The migration was not adjusted to the new meaning of -1 for firstPublishedIndex.
  • Contents which are not part of a ContentGroup (archieved contents) did not have their model updated.

Related: !367 (merged)

Merge request reports