Review main Merged Breaking

52132[!!!][BUGFIX] Resolve API based content element registration inconsistency

Benjamin Kott CR +2 V +2 Normal +192 −51 updated 08/27/17, 11:19

Commit message

To solve an inconsistency issue for API based content element
registration between CSS Styled Content (CSC) and Fluid Styled Content
(FSC) through `Extbase` or `addPItoST43` we are now Introducing a new
shared content object for content elements and drop the active usage of
lib.fluidContent.

The generated code relied on the existence of the removed lib.stdheader
and also ignored layouts, frames, spacebefore, spaceafter in context of
Fluid Styled Content.

For content element registration lib.contentElement is now used for CSC
and FSC and replaces the usage of lib.fluidContent. The generated code
was slightly adjusted to match the requirements of all content rendering
definitions and can be adapted to the specific needs of a content
element rendering definition anytime since a reference is used now
instead of a hard defintion.

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 2

Files 36

Show 16 more files