Issue Bug Closed

#62682Separate core and css_styled_content

Patrick Broens 11/04/14, 10:48 updated 01/08/16, 11:17

Description

Make it possible to replace css_styled_content with another extension providing content elements without cluttering database and unused definitions and methods.

Keep only the necessary basic properties for content elements:
  • Authoring (user, tstamp, time)
  • Hierarchy (position, sorting, parent page)
  • Visibility (frontend user access, access time)
  • Channel (language, workspace)
Tasks
  • Move tt_content table definition to css_styled_content, except for fields mentioned above.
  • Move relevant TCA to css_styled_content. Keep the basic properties in “frontend”.
  • Move language labels, used in TCA, to css_styled_content.
  • Move user functions, used in TCA, to css_styled_content.
  • Move images, used in TCA, to css_styled_content.
  • Move the content preview for content elements in tx_cms_layout::tt_content_drawItem to css_styled_content

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.