I’m migrating an Extbase content element to a FLUIDTEMPLATE cObj CE with dataprocessors.
One problem I step into are Flexform + TypoScript settings.
With Extbase I got a merged settings array of TypoScript and Flexform, with FLUIDTEMPLATE I just get the TypoScript.
I use Flexform and TypoScript settings e.g. to configure a slider:
<div class="slider" data-slick='{settings.slider.slick -> e:format.json.encode()}'>
I checked the example provided by stmllr and made some changes that makes it act like the Extbase FrontendConfigurationManager https://gist.github.com/t3easy/22bdcf7189e0dce76e246a581790e4a4
Main change is, that just FlexForm prefixed with settings. are merged with TypoScript settings. And that I use ArrayUtility::mergeRecursiveWithOverrule.
Hope that helps others to migrate.
Related
I want to use links with <f:link> in HTML element inside handler and in Typoscript with typoscriptObjectPath, for example:
<f:link.page pageUid="13" >Test Page Link</f:link.page>
But they always appear to me as plain text.
I'm using Typo3 11 and Fluid Template.
Do you have to activate something so that it renders as it was done before with the old old link parser?
Let's see if someone can help me
If you wanna get a text parsed as HTML, just use f:format.html() in your Fluid Template. It renders a string by passing it to a TYPO3 parseFunc. By default lib.parseFunc_RTE is used to parse the string.
I made it.
Set the links in Typoscript this way:
lib.redesp = TEXT
lib.redesp.value = Test Link
And in the Fluid template set:
<f:format.html parseFuncTSPath="lib.parseFunc">
<f:cObject typoscriptObjectPath="lib.redesp"/>
</f:format.html>
Don't know if this is the best way, but it works.
I'm running a TYPO3 webseite with TYPO3 version 7.6.16 and the extensions gridelements 7.0.5. In backend the selection for gridelements is empty ... what could be the reason?
also missing is this tap in new page item wizard
Did you follow the steps in manual?
https://docs.typo3.org/typo3cms/extensions/gridelements/Chapters/Installation/Index.html
Include static template
Create some CE backend layouts
Create new Grid Elements
I upgraded TYPO3 6 to 7.6.x and now I can't choose custom layouts in the backend for any content elements in the backend. I only see the default options like "layout 1, layout 2". The reason is obviously that my TCEFORM addings doesn't work..
The following typoscript won't have any effect in a ext-template of a page or in the root setup.ts:
TCEFORM.tt_content.layout.altLabels.2 = Test
TCEFORM.tt_content.layout.removeItems = 2,3
TCEFORM.tt_content.layout.addItems.5 = New Item
I know the problem description is a bit inaccurate. But I don't see the relevant infos which u need. Can u give me an advice what I have to check? Are there known conflicts with extension like fluidcontent, css_styled_content or so?
TypoScript configuring the back end is (though TypoScript by syntax) often called TSConfig and can be added either in page records or via user settings but never in extension templates or similar.
Configuring TCEFORM is usually done in page properties. To add, open page properties of your root page (or the topmost page of the subtree you want to configure) and add your code there.
As in front-end TypoScript you can swap your code to external files.
You need to add this typoscript on Root Page in Page TSconfig.
Edit root page properties and add your typoscript in Resources tab in Page TSConfig section like below image, so it's work fine.
I created a custom content element with a "bodytext" field like this:
bodytext;Text;;richtext:rte_transform[flag=rte_enabled|mode=ts_css],
rte_enabled;LLL:EXT:cms/locallang_ttc.xlf:rte_enabled_formlabel
The text editor doesn't work properly. The links for example are formated like this:
<link 88 - internal-link>test</link>
which doesn't work in the frontend.
RTE is also throwing a lot of info and errors in the backend, here is a screenshot of firebug:
If I use a core content element like "text & media" RTE does work perfectly .. So I guess there is some configuration missing in my extension ?
How did you set up your custom content element? In which file did you set up your bodytext field shown above?
The link formatting like <link></link> is the normal and correct behavior of the RTE. By this way, links can be rendered dynamically having the pageid saved and they will still work even if the domain or pagetitle of the target page changes - this would not work if links would be saved "hard" like <a href="xy">.
However, those link tags have to be rendered using the lib.parseFunc_RTE when outputting the content. For example if you use Fluid for output, just use <f:format.html>{yourBodytextVariable}</f:format.html> and you will get correct links (f:format.html uses lib.parseFunc_RTE by default).
Check out your Typoscript Object Browser to find out more about the lib.parseFunc_RTE object and check out this doc: https://docs.typo3.org/typo3cms/TyposcriptReference/Functions/Parsefunc/Index.html
In TYPO3 6.1, how do I get the tsconfig for the tx_news news extension to work?
I try to add selectable layouts to news items:
tx_news.templateLayouts {
1 = A custom layout
99 = LLL:fileadmin/somelocallang/locallang.xml:someTranslation
}
This should add the new Layout to the Type field, as in:
or did I get that wrong? Where can that new custom layout be selected?
Also, I'm trying to prefill fields in flexforms (when a new plugin is inserted):
TCEFORM.tt_content.pi_flexform.tx_news.sDEF.categoryConjunction = and
But it does not work yet.
How can this be done?
With tx_news.templateLayouts you override the flexform for the news plugin you insert on a page, not for a news record.
Your second code looks almost right, but you forgot settings: TCEFORM.tt_content.pi_flexform.tx_news.sDEF.settings.categoryConjunction = and
And even though this code is right, it will not work because of a bug with flexform fields that have a dot in their name (this is just stupid).
I think the only way to cleanly modify the flexform, is to write a small extension which overrides the default news flexform.