Project

General

Profile

Actions
Copy link

Bug #62682

closed

Epic #61834: Create future proof Content Element with strong default

Task #61836: Reorganize Content Element properties within backend Extension

Task #61842: Refactor CSS-Styled-Content + Content Elements

Separate core and css_styled_content

Added by Patrick Broens about 10 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Patrick Broens
Category:
Content Rendering
Target version:
7.2 (Frontend)
Start date:
2014-11-04
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

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

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Task #65922: Move unused tt_content TCA fields and the arrangement to css_styled_content or compatibility6ClosedPatrick Broens2015-03-23

Actions
Actions
Copy link

Also available in: Atom PDF