Feature #25046

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

Added by Dominique Feyer about 9 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-02-15
Due date:
% Done:

0%

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)

class.t3lib_befunc.php.patch View (3.09 KB) Administrator Admin, 2011-02-15 16:34

History

#1 Updated by Georg Ringer about 9 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

#2 Updated by Dominique Feyer about 9 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 ;)

#3 Updated by Wouter Wolters about 5 years ago

  • Description updated (diff)
  • Category deleted (Communication)
  • Status changed from New to Closed
  • Target version deleted (0)

Also available in: Atom PDF