Feature #25046: Allow the usage of t3lib_befunc::getProcessedValue() in the frontend - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Feature #25046

closed

Allow the usage of t3lib_befunc::getProcessedValue() in the frontend

Added by Dominique Feyer about 13 years ago. Updated over 9 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Target version:

Start date:

2011-02-15

Due date:

% Done:

Estimated time:

PHP Version:

5.3

Tags:

Complexity:

Sprint Focus:

Description

The separation between BE and FE is sometime a big issue in some projet. I supply a little patch to allow the use of t3lib_befunc::getProcessedValue() in a frontend extension. The idea is not to port all the BE API to the FE, but a coding a copy of getProcessedValue in FE it's not a good option.

The proposed patch simply add a proxy method t3lib_befunc::sL to switch between $LANG->sL and $TSFE->sL depending on TYPO3_MODE

(issue imported from #M17601)

Files

class.t3lib_befunc.php.patch (3.09 KB) class.t3lib_befunc.php.patch

Administrator Admin, 2011-02-15 16:34

Actions

Copy link

Updated by Georg Ringer about 13 years ago

IMO having this in the core is not an option. I know the seperation is sometimes very liming but still you can use such a function in your extension as well

Actions

Copy link

Updated by Dominique Feyer about 13 years ago

I wait about this kind of answer, so I release fefunc to TER with some static function from t3lib_BEfunc usable in FE (without Workspace support). You can close this issue ... or this not really issue ;)

Actions

Copy link