Since Version 9.3 TYPO3 ships with a nice API to handle meta tags. I was looking for a way to provide a fallback og:image to avoid some randomish results and finally made a custom meta tag manager.
This blog is no longer maintained on a regular basis. I refrained from using the FluidTYPO3 extensions (except for vhs) thus I can't provide updates or new tips regarding those. Thanks.
Onepage or Singlepage design sites are quite popular these days especially for sites that don't provide too much content, landing pages or microsites and the like. Creating those in TYPO3 is easy enough with FluidTYPO3. Here's how.
I just wanted to let you know that I updated my examples in the quickstart series of posts to reflect the recent changes in FluidTYPO3. Please be aware that all are now based on TYPO3 6.2.x and the latest dev branches of the extensions which is important regarding namespaces and namespace declarations.
In case you encounter the mysterious net::ERR_CONTENT_LENGTH_MISMATCH error (doesn't apply to Firefox) let me guess: Using TYPO3 6.2.x? Using EXT:vhs? Thought so. The error can be caused by vhs' assets feature in the current TER version 1.8.5 and in combination with
config.enableContentLengthHeader which is enabled in TYPO3 6.2 by default. So to fix it either disable
config.enableContentLengthHeader (uncool) or use the current dev branch of vhs found on GitHub.
The FluidTYPO3 family of extensions underwent some major updates recently. Flux was bumped to version 7.0 which included changes in the naming of most of its viewhelpers. All examples in this blog remain functional but should be updated to reflect the new naming scheme. Unfortunately I don't have enough time for that so in case you came here to follow those examples please head over to fluidtypo3.org and see what has changed.
In a current project I needed a way to replace the wording of selected form labels and messages for certain users. Symfony's translation catalogues seemed the right place to start with as I could simply add different catalogues for those users and use the
translation_domain argument in forms.
In case you find yourself repeating a set of FlexForm fields in multiple FCEs or page templates here's a nice 'hack' to share them across templates.