Migration, flux:field.file to inline FAL
Upgrade wizard class to convert instances of flux:field.file which is now deprecated on TYPO3 9.5 and removed on TYPO3 10.4, to instances of inline FAL relations.
Community library
Browse practical patterns shared by the FluidTYPO3 community.
Upgrade wizard class to convert instances of flux:field.file which is now deprecated on TYPO3 9.5 and removed on TYPO3 10.4, to instances of inline FAL relations.
Lists all subpages of selected entry pages, sorted in alphabetical order.
Hides FAL forms until first saving and displays a message.
Let the Backenduser just put in a startpage for the navigation as a content element. For when reskinning sitemap is to cumbersome.
Realize dynamic colPos based sections with custom configurations like background-color using flux.
Implementation of Google Maps with one or more markers. When having multiple markers, the bounds are fit to them.
If you are in the need for a one liner to migrate all EXT:fluidpages based page layouts and EXT:fluidcontent based fluid content elements because the provider extension has got a new name (for whatever reason) use these SQL commands
Useful if you have two languages in your typo3 project and want to switch between them.
Create 2-6 Columns with advanced Column Settings
This adds a new indexer configuration type to the ke_search extension.
This is an example to show how you could specify a fluidcontent element as only allowedContentType
If you want to use `content_fallback` you will notice that `v:content.render` doesn't work here in older versions of VHS.
This snippets shows you A how to define flux settings via TypoScript for your frontend plugin and B how to use the controllerAction ViewHelper in such a scenario.
As the title says. Builds the html Object like: id="#s1043" data-test="{"myVarName":"1"}"
Code for creating a FCE for displaying content in two flexible width columns.
This will help you to "allow" or "deny" a FluidContent FCE in a flux:grid.column.
Example for creating a menu with vhs:page.menu in a recursive way. Just set a start page and the whole tree gets rendered.
If you use css_styled_content and need to override the default container for a content element of type fluidcontent_content, you can achieve this using tt_content.stdWrap.outerWrap.cObject. This Gist goes one stage further and compares the name of the actual Fluid template being implemented to allow a more specific wrapper.
How to treat news detail view different for a all subcategories of a specific root category (this example only works for two levels of categories). It shows how to use v:switch, v:variable.typoscript and v:iterator ViewHelpers.
Rendering a browse menu with prev/next which detects first and last page. (2 Buttons only)
If you want to split long FlexForm definitions into multiple partials and use them in other templates, here is the way to go!
How to manually render page menus or treat specific page uids different from others in a menu
Site header with Twitter Bootstrap "MegaMenu". Navigation rendered with VHS and Fluid as MegaMenu with image shown if it exist. If no image resource exists standard rendering of sub pages is used.
This section defines all metatags which are used to have defined in a website. It also contains the most relevant OG-Tags for facebook. It can also be used as an example how to read FAL images related to a page record. Here it is used as og:image.
This Gallery FCE is a example how to use FAL images in Flux Content Elements.
A small example of two domain model classes connected with an MM table, with all TCA required to operate the table in TYPO3 generated by Flux by using annotations on the PHP class doc comments.
Shows how to use the v:or ViewHelper instead of multiple f:if conditions to select the first value that is not empty and use or output it. Explains how the ViewHelper can be used together with f:if (and any other condition ViewHelper) or as an alternative to it.
Shows how to manually loop and render pages using v:page.menu instead of the built-in rendering which can only be affected in key aspects like class names. Includes a demonstration and small explanation of special properties which are added to each page's data, containing a pre-built link, link text and link tag CSS class name.
Example of how to create a simple subclass of \FluidTYPO3\Flux\Form and utilise the initializeObject method to create new fields upon Form instance creation. Also includes an example on how to use a Provider to return different Form instances based on arbitrary values.