DEPRECATION WARNING

This documentation is not using the current rendering mechanism and will be deleted by December 31st, 2020. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.

Introduction

What does it do? | Screenshots | Quickstart | Changelog |

What does it do?

If you want to render some TypoScript as a Content Element, you can use this plugin. This plugin is really a small plugin without any deeper logic, but should help you with your daily work.

Screenshots

hmenu

Showing some TypoScript Object in Frontend (e.g. a HMENU)

flexform

You can add a TypoScript-Path in Plugin Edit View

setup

This is another Example Setup to render the current Year in Frontend

extension_manager

Decide if the plugin view is cached in general or not in extension manager settings

Quickstart

  • Import Extension from TER
  • Add some TypoScript to the current (or the root) page (e.g. lib.temp)
  • Add the plugin to a page
  • Write lib.temp into the FlexForm Field
  • Done

Changelog

All changes are documented on http://forge.typo3.org/projects/extension-typoscript2ce

Version Release Date Release Description
1.1.1 2016-07-13 Removed some copy paste errors. No functional changes.
1.2.0 2017-01-25 Move to github, add composer.json, Update dependencies for TYPO3 8.x
1.1.1 2016-07-13 Small bugfixes
1.1.0 2016-01-23 Set dependencies to PHP5 minimum Update dependencies to TYPO3 6.0-7.x PSR-2 Refactoring
1.0.2 2014-08-08 RST Documentation is not rendered in TER - change in Manual
1.0.1 2014-08-05 RST Documentation is not rendered in TER - change in Manual
1.0.0 2014-07-28

Refactored to Extbase and Namespaces

TYPO3 6.0 or higher required now

Breaking Change to 0.1.0: The FlexForm Field has changed, so you have to add the TypoScript Path again after updating

0.1.0 2009-03-31 Initial Upload to TER