Review main Merged

51962[FOLLOWUP][BUGFIX] Exception when setting "language" to "all" for content

Oliver Hader CR +2 V +2 Easy +15 −14 updated 03/06/17, 22:17

Commit message

The initial change just hid a misbehavior when dealing with a content
element that was defined for the non-existing "all language". In this
case no localizations are possible and the data-map item shall not be
considered at all. This change makes the exception on language "-1"
more explicit and does not hide these side-effects.

Besides that, the functional tests were extended to check the complete
scenario for the defined language to be tested in the frontend.

Review

  • Code review CR +2

    Imported before Forger kept the single votes, the next import adds them.

  • Verified V +2

    Imported before Forger kept the single votes, the next import adds them.

Issues 1

Files 3