http://screencast.com/t/L3Asbi2E - Wizard link Target not rendering in front
Front side code is
TITLE
But target not rendering
AFAIK the f:link.page ViewHelper does not interpret typolinks (that is what you have).
You should use a ViewHelper that does, for example the v:link.typolink ViewHelper from the extension vhs. You'd use it like this:
{namespace v=FluidTYPO3\Vhs\ViewHelpers}
<v:link.typolink configuration="{parameter: youvariablehere}">Linktext</v:link.typolink>
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 have followed the tutorial for making a sitepackage and I am at the point of content mapping.
The problem is, all the text from the rte is being wrapped in <p> tags so the output looks like this:
<p><h2>A Heading</h2></p>
<p><p>Some Text</p></p>
The problem appears to be how fluid_styled_content is included, I have tried both:
<INCLUDE_TYPOSCRIPT: source="FILE:EXT:fluid_styled_content/Configuration/TypoScript/setup.txt">
#import 'EXT:fluid_styled_content/Configuration/TypoScript/setup.typoscript'
The problem goes away if I manually add fluid_styled_content in the typo3 template includes. So how do I include it properly within my site package?
Problem is that the filename changed. You need to use: <INCLUDE_TYPOSCRIPT: source="FILE:EXT:fluid_styled_content/Configuration/TypoScript/setup.typoscript">.
You also can use the newer import: #import 'EXT:fluid_styled_content/Configuration/TypoScript/setup.typoscript'
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
does anybody know how to implement the image cropping for a custom extbase extension ? I know how to display the image form field for the backend part, but not the rendering in the extension template.
I know that the fluid_styled_content sysext uses the TYPO3\CMS\Frontend\DataProcessing\GalleryProcessor assigned to the textmedia content element via typoscript in the extension setup.txt, but I don't know how to implement it in a custom extension.
Can anybody help me here ?
thanks,Lukas
It's quite easy I found out. The viewhelper f:media renders the image correctly, taking into account the image settings in the image field.
<f:media
file="{image}"
width="{column.dimensions.width}"
height="{column.dimensions.height}"
alt="{column.media.alternative}"
title="{column.media.title}"
/>
Fluid template example:
<f:image
image="{image}"
alt="{image.originalResource.title}"
width="460c"
height="460c"
treatIdAsReference="TRUE"
/>
Value {image} must contain FAL image object.
Image is cropped by attributes width="460c" and height="460c".
I have a custom edit (browser page) for my dexterity content type. In template I have defined a form using Bootstrap and added some Angular JS code for form behavior. It is working. :)
I need to replace a simple textarea with rich text widget. So how can I render in my template the rich text widget (one that is normally used in dexterity)?
If you are using Mockup (not sure if anybody use it on Plone 4) you can find tips there: Obtaining the "default" mockup TinyMCE configuration on Plone 5
Otherwise (the Plone 4.3 version of TinyMCE) it's only a matter of CSS classes and configurations.
<textarea name="..."
class="pat-tinymce mce_editable"
data-mce-config JSONCONFIGURATION_HERE">
</textarea>
I've an add-ons that enable TinyMCE on simple forms; look at the cose to find how to obtain the JSON configuration: See rt.zptformfield.
I've also a blogpost about the approach I used there but it's in italian :-) - http://blog.redturtle.it/usare-widget-plone-in-semplici-template-html
It should suffice to apply the class mceEditor on the textarea.
If that shouldn't work, include the initialization in your template:
tinyMCE.init({
elements : "id-of-textarea",
});