Bug #3292
viewhelper backend support
| Status: | Resolved | Start date: | 2009-05-14 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Bastian Waidelich | % Done: | 100% |
|
| Category: | ViewHelpers | |||
| Target version: | - | |||
| Has patch: | Affected Flow version: |
Description
we need support for using viewhelpers in BE
History
#2 Updated by Bastian Waidelich almost 6 years ago
Bastian Waidelich wrote:
What needs to be done here?
To reply to myself:
Fluid view helpers need to be independent from $GLOBALS['TSFE'] for example. Or they need to implement some TYPO3_MODE switch.
I started doing this while working on #4418.
#3 Updated by Bastian Waidelich almost 6 years ago
- Category set to ViewHelpers
- Assigned To set to Bastian Waidelich
#4 Updated by Bastian Waidelich almost 6 years ago
- % Done changed from 0 to 80
Almost all fluid view helpers work in backend mode too now with following restrictions:
- cObject - works with the somewhat hacky workaround
$GLOBALS['TSFE']->cObjectDepthCounter = 100; - format.crop - simply returns
substr($stringToTruncate, $maxCharacters);in BE mode. Arguments "append" and "respectWordBoundaries" are ignored yet - translate - works partly. language fallback and TypoScript _LOCAL_LANG replacement do not work yet
- link.email, uri.email - work, but the javascript encryption won't be active - But that should be OK for BE mode
#5 Updated by Bastian Waidelich almost 6 years ago
Bastian Waidelich wrote:
Almost all fluid view helpers work in backend mode too now with following restrictions
I forgot:
image view helper does not work at all in BE mode.. We're working on it!
#6 Updated by Bastian Waidelich almost 6 years ago
- Status changed from New to Resolved
- % Done changed from 80 to 100
BE support is implemented.
Not all view helpers work in BE mode yet, but I'm closing this issue for now.