Task #60801

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

Remove "tt_content >" from SYSEXT: css_styled_content

Added by Ben N about 5 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Content Rendering
Target version:
Start date:
2014-08-05
Due date:
2014-08-08
% Done:

0%

Estimated time:
0.05 h
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
no-brainer
Sprint Focus:

Description

It would be preferable to not have that rude approach in a system extension (please enlighten me if this is definetely necessary). I'd like to pre-set some config-options in the tt_content namespace before the EXT is loaded.
The part

#**********************************
# tt_content is started
#**********************************
tt_content >

in setup.txt obviously intereres with that.

History

#1 Updated by Felix Kopp almost 5 years ago

  • Parent task set to #61842

#2 Updated by Frank Naegler almost 5 years ago

I am not sure, but I think to ensure that nothing was set before, also for a stable system, it is not wrong to clean tt_content at this position.

#3 Updated by Mathias Schreiber over 4 years ago

  • Target version changed from next-patchlevel to 7.2 (Frontend)

#4 Updated by Benni Mack over 4 years ago

  • Target version changed from 7.2 (Frontend) to 7.4 (Backend)

#5 Updated by Benni Mack about 4 years ago

  • Status changed from New to Rejected

This is necessary. It is not about being rude, but about have a clean and proper way of making sure that CSS styled content behaves exactly as it should be - without side effects, and not allowing integrators mess around with it. Ideally, if you need CSS Styled Content (or parts of it), you should copy these parts into your own extension.

If you have any further questions on the topic, feel free to contact me.

Also available in: Atom PDF