Project

General

Profile

Actions

Feature #64023

closed

Refactor TSFE initialization so that it may be used for eID scripts, etc?

Added by Lucas Jenß almost 10 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
Could have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-12-22
Due date:
% Done:

0%

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

Description

Right now, the TSFE is being initialized in index_ts.php and the initialization procedure cannot be re-used, i.e. when trying to create a TSFE instance from an eID script. This is especially problematic since an inproperly initialized TSFE may "work" in the sense that there are no obvious errors, but it may be incompletely populated thus causing issues that are hard to track down.

Thus the question is if the a subset of the functionality currently contained in TYPO3\CMS\Frontend\FrontendRequestHandler#handleRequest, i.e. the subset that initializes the TSFE, could be refactored into e.g. TypoScriptFrontendController::createAndInitialize.

Actions #1

Updated by Mathias Brodala almost 10 years ago

What is the advantage of having an eID script being run with a fully initialized TSFE?

If you need a full environment maybe eID is not the solution for you. You could use a custom page type or solutions like EXT:typoscript_rendering instead.

Actions #2

Updated by Jigal van Hemert almost 10 years ago

  • Status changed from New to Rejected

eID is meant for small, fast requests that only need a very minimal set of features. Other solutions exist for using fully or partially initialised TYPO3 frontends.

If you think this not correct post a request in typo3.teams.bugs to ask for the issue to be re-opened.

Actions

Also available in: Atom PDF