Feature #16404

flexibilize addPItoST43()

Added by Elmar Hinz almost 15 years ago. Updated almost 9 years ago.

Status:
Rejected
Priority:
Should have
Category:
-
Target version:
-
Start date:
2006-07-25
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Extensions only work with 'css_styled_content' oder 'content (default)' if they use t3lib_extMgm::addPItoST43(). To use another rendering extension an alteration of the function t3lib_extMgm::addTypoScript() is necessary.

Make it more flexible by using a global variable to register the rendering extension:

Replace line 873:

$TYPO3_CONF_VARS['FE']['defaultTypoScript_'.$type.'.']['cssstyledcontent/static/'].=$content

With

$TYPO3_CONF_VARS['FE']['defaultTypoScript_'.$type.'.'][$SomeGlobalVariable].=$content;

<http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/browser/typo3/TYPO3core/trunk/t3lib/class.t3lib_extmgm.php?rev=4768>

(issue imported from #M3930)


Related issues

Related to TYPO3 Core - Bug #22534: csc static template "v4.3" won't include the registered pluginsClosedErnesto Baschny2010-04-28

Actions
#1

Updated by Ernesto Baschny almost 15 years ago

I would propose to postpone this feature to a refactoring of this stuff. I know of no other content rendering engine besides content (default) and css_styled_content, and I don't think there will be more of that before (or even after) TYPO3 5.0. And in 5.0 we need to rethink these things anyway (static templates in sys_templates will probably be gone by then).

#2

Updated by old_lab almost 15 years ago

I would like to have a method to use another rendering system.

know of no other content rendering engine besides content (default) and css_styled_content,...

Maybe thats because it is so difficult to plug one in... ;-)

#3

Updated by Peter Niederlag almost 15 years ago

IMO this feature-request qualifies perfect for 4.1. It's not a great fuss and a small (and backwards compatible) change.

#4

Updated by Ernesto Baschny almost 15 years ago

ok, agreed! :)

#5

Updated by Ernesto Baschny almost 15 years ago

How about $TYPO3_CONF_VARS['FE']['contentRendererTemplate'][] array where all the content renderers can register?

I would leave "cssstyledcontent/static/" hardcoded as it is (in 4.x), because some crazy folk might be using some old or adapted of "local" installation of css_styled_content which would not add itself to this array.

So this would just be used by new content rendering extensions.

#6

Updated by Ernesto Baschny almost 9 years ago

  • Category deleted (Communication)
  • Status changed from Accepted to Rejected
  • Target version deleted (0)
  • PHP Version deleted (4)

Not really needed anymore

Also available in: Atom PDF