Project

General

Profile

Actions
Copy link

Task #61836

closed

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

Reorganize Content Element properties within backend Extension

Added by Felix Kopp about 10 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-02-21
Due date:
2014-08-08
% Done:

100%

Estimated time:
(Total: 0.05 h)
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

To be prepared for the future of new Content Elements many properties of tt_content should be refactored.
Main problems are: Unused/antiquated fields, unclear naming, un-deterministic spelling.

As discussed at the T3UXW14 the best technical approach is to move fields to EXT: css_styled_content.
Allow extensions for alternative Content Elements with Rendering.

As a first step for a clean up and refactored tt_content properties - specific properties should be moved to EXT: css_styled_content.
New approaches for Content Elements are born with EXT: content_elements and EXT: fluid_contentelements or futuristic Content Element Types.

Files

Field arrangement.pdf (50.4 KB) Field arrangement.pdf Patrick Broens, 2014-09-25 12:05

Subtasks 17 (0 open — 17 closed)

Task #61842: Refactor CSS-Styled-Content + Content ElementsClosed2011-02-212014-08-08

Actions
Feature #13230: tt_content.search.20 should be done with the new FORM mappingRejectedPatrick Broens2011-02-21

Actions
Feature #13229: tt_content.login.20 should be done with the new FORM mappingRejected2011-02-21

Actions
Task #60801: Remove "tt_content >" from SYSEXT: css_styled_contentRejected2014-08-052014-08-08

Actions
Bug #48066: Remove content element Bullet List and migrate dataClosed2013-05-08

Actions
Feature #49547: Media content element: HTML5 as standardClosed2013-07-01

Actions
Feature #44779: No css_styled_content on content element TABLEClosed2013-01-24

Actions
Task #34794: CSS Styled Content should ship HTML5 by defaultClosed2012-03-13

Actions
Bug #37670: Text with image - image dimensionsClosed2012-06-01

Actions
Bug #38460: Using media-element --> Flashfallback failsClosed2012-06-28

Actions
Bug #42070: Media CE (HTML5 <video> element ) controls don't work on ChromeClosed2012-10-17

Actions
Bug #43420: Media element does not render any outputClosed2012-11-29

Actions
Bug #44633: Media-element: Vimeo-video can not play via HTML5Closed2013-01-18

Actions
Feature #47581: Offer possibility to have ordered list with CType bulletsRejectedPatrick Broens2013-04-25

Actions
Bug #49476: css_styled_content borderThick could not be set to 0Closed2013-06-27

Actions
Bug #53305: HTML5 rendering of headers works only if a date is setClosed2013-11-04

Actions
Bug #62682: Separate core and css_styled_contentClosedPatrick Broens2014-11-04

Actions

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Task #79622: Streamline CSS Styled Content and Fluid Styled ContentClosed2017-02-28

Actions
Precedes TYPO3 Core - Feature #61839: Include modern Content ElementsClosed2014-08-112014-08-11

Actions
Actions
Copy link
 #1

Updated by Felix Kopp about 10 years ago

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)

Move everything else to CSS-Styled-Content.

Actions
Copy link
 #2

Updated by Felix Kopp about 10 years ago

  • Subject changed from Move Content Element fields to CSS-Styled-Content to Strip down Content Element

Move additional properties of Content Elements to CSS-Styled-Content.

TYPO3 core will deliver CSS-Styled-Content and a modern version of CSS-Styled-Content with modern Content Elements plus migration wizard.

Actions
Copy link
 #3

Updated by Felix Kopp about 10 years ago

  • Subject changed from Strip down Content Element to Reorganize Content Element properties within backend Extension
Actions
Copy link
 #4

Updated by Patrick Broens about 10 years ago

This means tt_content table definitions, TCA, language labels and user functions, used in TCA

Actions
Copy link
 #5

Updated by Patrick Broens about 10 years ago

  • File Field arrangement.pdf added
  • File Field arrangement.pdf added
Actions
Copy link
 #6

Updated by Patrick Broens about 10 years ago

  • File deleted (Field arrangement.pdf)
Actions
Copy link
 #8

Updated by Felix Kopp almost 10 years ago

  • Status changed from New to Accepted
Actions
Copy link
 #9

Updated by Benni Mack about 7 years ago

  • Status changed from Accepted to Closed
Actions
Copy link

Also available in: Atom PDF