fluid

问题 I use the following syntax in my fluid template to render the media files in news: <f:for each="{v:content.resources.fal(field: 'fal_media',table:'tx_news_domain_model_news',uid:'{newsItem.uid}')}" as="singleImage"> <div style="background-image: url({singleImage.url})" class="teaser__image"></div> </f:for> German is my default language, English the overlay language. In the English news I have implemented a different media image, but only the German (default) image is shown. How can I render

问题 What would be the recommended method to add custom page property fields in TYPO3 6.2? In 4.5 I used TemplaVoila which had its own page module and made it easy to add data records on a page level. 回答1: There are several approaches: The "vanilla" approach: Create an extension (and with it the file ext_emconf.php ) and then create a file ext_tables.sql in the extension root. In it you can put SQL-definitions for the new fields, by defining a CREATE TABLE statement for the pages table: CREATE

问题 What is to be understood by "Fluid powered TYPO3" (as stated by http://fedext.net/) and what are its benefits for the integration? Are there other modern templating approaches for TYPO3 6.x that would be best practice to switch to now? I don't understand the different systems that are around at the moment and I need some clarification. The background of the question, what I am looking for: Don't use Templavoila Keep it simple, little coding overhead That's why I still use markers! Enable

问题 I use in TCA 'uebersetzungen' => [ 'exclude' => true, 'label' => 'LLL:EXT:maschinen/Resources/Private/Language/locallang_db.xlf:tx_maschinen_domain_model_maschine.uebersetzungen', 'config' => [ 'type' => 'select', 'renderType' => 'selectSingle', 'items' => [ ['6:1', 1], ['8:1', 2], ['11:1', 3], ['14:1', 4], ], 'size' => 4, 'maxitems' => 1, 'eval' => '' ], ], to get the output in fluid template with <f:switch expression="{maschine.uebersetzungen}"> <f:case value="1">6:1</f:case> <f:case value=

问题 I tried to show a list of news articles with the LIST-Modul grouped by year. The year itself should be displayed as headline for each group of articles. Like 2014 -------- article 1 article 2 article 3 -------- 2013 -------- article 4 article 5 ... I tried to implement it with the f:groupedFor viewhelper in the standard list.html template of the extension. inside the pagedNews part. But TYPO3 throws the exception: http://wiki.typo3.org/Exception/CMS/1237900529 I also tried the viewhelper

问题 This is a continuation of a previously asked and answered question that has cropped up again and needs a different solution ( different problem but same error message ). Again the links to the shippingAddress action are not rendering: <f:link.action action="shippingAddress" controller="Order" arguments="{address: shippingAddress, changeAddress: 1}"><f:translate id="seethroughweb.shop.change-address">Change</f:translate></f:link.action> When debugging and expecting to find that the address

问题 I use TYPO3 CMS 6.2.14, vhs 2.3.3 , Flux 7.2.1 and FluidContent 4.3.1 - my TYPO3 Editor need the opportunity to upload SVG-Images via vhs -ViewHelper. I've made a new FluidTYPO3 Content Element (FCE), but there's no SVG Image visible in frontend. Mmhh? Flux-FlexForm <flux:field.file name="imgIcon" allowed="jpg,gif,png,jpeg,svg" uploadFolder="uploads/tx_myext" minItems="0" maxItems="1" size="1" /> ... <v:media.image src="uploads/tx_myext/{imgIcon}" alt="Icon" /> Output <div class="small-2

问题 This question is similar to that one: RTE in own backend module based on Extbase and Fluid but not the same, so i created a new question. I create a comment-extension for typo3 Version 8.7.7 I have added a RTE Editor (CKEditor) to a textarea field in my BackendModule. Therefore i have the following TCA in my comment-model: 'text' => [ 'exclude' => true, 'label' => 'LLL:EXT:rmcomment/Resources/Private/Language/locallang_db.xlf:tx_rmcomment_domain_model_comment.text', 'config' => [ 'type' =>

问题 I search for a way to test my extbase-extension. I work with two different templatepaths for front- and backend. module.myext{ view { templateRootPath = myext/Resources/Private/Backend/Templates/ partialRootPath = myext/Resources/Private/Backend/Partials/ layoutRootPath = myext/Resources/Private/Backend/Layouts/ } } The backendmodule works without any problem, but my test will not get the different templatepath. If i write the view.templateRootPath to config.tx_extbase in the ext_typoscript

问题 I'm combining a TypoScript CONTENT Object with a fluid template. In the page template: <f:cObject typoscriptObjectPath="lib.myItem" /> In TS: lib.myItem = CONTENT lib.myItem { table = tt_content select.where = colPos = 0 select.languageField = sys_language_uid renderObj = FLUIDTEMPLATE renderObj { file = {$customContentTemplatePath}/Myfile.html layoutRootPath = {$customContentLayoutPath} partialRootPath = {$customContentPartialPath} dataProcessing { 10 = TYPO3\CMS\Frontend\DataProcessing