When adding text content to a TYPO3 site you most probably Copy & Paste it from some other files. Chances are even high that you have a formatted Word document or a PDF file, which you got from your client or some other department of your company. And you all know what happens next: when pasting the formatted text as is to TYPO3’s Rich Text Editor (RTE), the format of the text is preserved, messing up your text layout. Meh.
TYPO3 CMS 6.2 LTS Extbase & Fluid Cheatsheet by Patrick Lobacher
More as a reminder to myself, but surely useful for everyone working with Extbase and Fluid on a daily basis, here the link to the great and indispensable TYPO3 CMS 6.2 LTS Extbase & Fluid Cheatsheet, which was updated and published by Patrick Lobacher on February 5th 2015 for the latest LTS version of TYPO3 CMS.
And by the way, an overview on what was new in TYPO3 CMS 6.2 LTS and what is new in TYPO3 CMS 7.0 can also be found on Patrick’s homepage.
String comparison in Fluid since TYPO3 6.1 (in case you missed it like I did)
When searching the Internet for how to compare two strings in TYPO3’s templating engine Fluid, you will still find a lot of pages telling you to do it this way:
|
1 2 3 |
<f:if condition="{0:myvar} == {0:'test'}"> Displayed if myvar is "test". </f:if> |
Basically you had to create two single valued arrays and compare their values. This has always been an awkward workaround. But over the time you got used to it.
But today I realized that this is not up-to-date anymore – in fact for quite some time. Already since version 6.1 of TYPO3 CMS string comparison in Fluid is more like you’d expect it to be:
|
1 2 3 |
<f:if condition="{foo.bar} == 'stringToCompare'"> Will result true if {foo.bar}'s represented value equals 'stringToCompare'. </f:if> |
Clean and natural, as this example taken from the comments of the current Fluid IfViewHelper shows.
Strange thing is that even official TYPO3/Fluid documentation doesn’t necessarily tell you about this change (like e.g. the TYPO3Wiki, from where the first example was taken), what might have caused me (and others probably, too) to overlook it. So I hope this post will help to spread the word about this small, but noteworthy fact.
The king is dead, long live…? TemplaVoilà and its epigones – Part 2: Grid Elements and Themes
Continuing my article series (find part 1 here) on TemplaVoilà replacements I take a look at two TYPO3 extensions, which have the potentials to play big roles in the upcoming years when it comes to templating in TYPO3: the already very well-known Grid Elements extension and the not (yet) so famous Theme Packages project.
The king is dead, long live…? TemplaVoilà and its epigones – Part 1: FluidTYPO3
For years TemplaVoilà (TV) was the de facto standard for building complex website layouts in TYPO3. But since further development has more or less ceased and as the release of the next LTS version of TYPO3 is imminent, an answer to the question, of what to use instead of TV, is badly needed. Luckily there exist quite a few pretenders to the throne, TemplaVoilà left abandoned, though a new king has not been crowned yet.
With this post I start a series of articles, in which I will try to give an overview of already available alternatives to TemplaVoilà, while also showing some other ongoing efforts inside the TYPO3 community for improving the page and content templating capabilities of TYPO3 CMS.
Looking for some advanced TYPO3 Flow configuration options? Take a look at Settings.yaml!
Though configuring TYPO3 Flow is very straightforward and pretty well documented, the Definitive Guide tells you more about how to configure your installation/package than telling you about what exactly you can configure. Here is where the Settings.yaml of the TYPO3.Flow package steps in.
Basic TYPO3 Flow and TYPO3 Neos resources
Even though TYPO3 Flow, TYPO3 Neos and Fluid are pretty well documented you can get sometimes a little bit lost when looking for specific information. Especially the usability of the official TYPO3 websites is not really great, as the page structure is IMO not well thought-out. And not to tell about the search functionality, which is currently pretty useless in most cases (e.g. have you ever tried to search for a Fluid ViewHelper on docs.typo3.org? Not quite the definition of meaningful search results…).
Quicktip: Find and replace data in MySQL
In case you need to replace a string in a certain field in MySQL use this small snippet:
|
1 |
UPDATE [table_name] SET [field_name] = REPLACE([field_name],'[string_to_find]','[string_to_replace]'); |
Problems getting to run TYPO3 Neos on your Mac? Here is probably how to fix it
In case you wanted to try out the new Content Management System TYPO3 Neos, either in a Beta version or in version 1.0, you may have come across a weird problem when installing it on your local development environment on your Mac.
One common pitfall when working with TYPO3 extension powermail
I’ve had the problem myself, when I used powermail years ago for the first time. And I’ve seen it again and again with other developers since then: The extent use and automatic inclusion of jQuery and some other Javascript libraries is a constant cause for non-working powermail forms, after having it set up. And too often the developer is at first clueless, why it’s not working, as the problem’s resulting from a fact, he is not necessarily aware of: Javascript conflicts, which occur as soon as you add the powermail static TypoScript templates to your website.

(4 votes, average: 4.75 out of 5)