#^TYPO3 v10 LTS — Safe and Sound

Today we are thrilled to announce the release of TYPO3 v10.4, also called TYPO3 v10 LTS indicating this is a long-term support version. This version is our new flagship and is, without doubt, one of the most advanced PHP-based open-source content management systems on the market.
After publishing five sprint releases since July 2019, we can proudly claim that we have equipped TYPO3 with the top modern PHP libraries and that we have introduced some fantastic new enterprise features. TYPO3 raises the bar even higher, and the core of the system is more stable than ever.
This article summarizes the major changes of all 10.x sprint releases and why website owners, integrators, developers, and editors alike will embrace the new LTS version.

#^Feature #90917: Replace TypoScript with YAML to use open standards - TYPO3 Core - TYPO3 Forge

Replace TypoScript with YAML to use open standards

#^TYPO3 Version 10.2 — Treasure Hunting!

TYPO3 v10.2 is out now — the last sprint release of the year. A lot of functionality was developed during the TYPO3 Initiative Week (T3INIT19) and TYPO3 v10.2 contains some of these components. We are excited to see that we made a big step forward to shape the next LTS release.

Ever wondered how to add a Fluid paginate widget to a non Extbase extension in TYPO3 #CMS? For example a core Content Element (CE) and fluid_styled_content? It is straight forward when you are familiar with TYPO3, but there was one not quite obvious workaround needed to make it complete. The following solution is tested in TYPO3 v9.1 and v9.2, but it is possible that there will be another solution in core in the future.

I have a TYPO3 default File Links [uploads] Content Element (CE) and wanted to output a collection from a folder with a lot of files. I was surprised, that there was no pagination available, but it is a fluid styled template, so it was easy to add a paginate widget.

Add a template override path to your Template constants:
# Add Fluid Styled Content template override path
styles.templates.templateRootPath = EXT:myext/Resources/Private/ContentTemplates/

Add to your ext Template setup following TypoScript to set an alternative template name for File Links CE. Also add a workaround for non-extbase elements like the File Links CE [uploads]. This is needed so that the Fluid paginate ViewHelper will also work. Otherwise you have pagination, but only results from the first page are shown, because no controller is executed.
##
# Customised TYPO3's File Links Content Element with pagination template.
#
# CType: uploads

# Use a customised fluid styled content template
tt_content.uploads.templateName = MyFilePagination

# Workaround to add functionality for non-extbase elements (https://forge.typo3.org/issues/79430)
tt_content.uploads.extbase {
    pluginName = filelist
    controllerName = filelist
    controllerExtensionName = myext
    controllerActionName = show
}

You can take the default template from typo3/sysext/fluid_styled_content/Resources/Private/Templates/Uploads.html and save it at typo3conf/ext/myext/Resources/Private/ContentTemplates/MyFilePagination.html. In your customised template add the Fluid paginate widget ViewHelper around the for ViewHelper and change the variable according:
<f:widget.paginate objects="{files}" as="paginatedFiles" configuration="{itemsPerPage: 10, insertAbove: 1, insertBelow: 1, maximumNumberOfLinks: 10}">
  <f:for each="{paginatedFiles}" as="file" iteration="fileIterator">

That's it.

Was fighting with Drupal8 half of my work day just to get stupid alternative mail templates for webform handlers with swiftmailer in production. And then in the evening I updated a private project to the new TYPO3 9.2 release and it was such a relief.

#^typo3-v920-released

Off to go Site-Seeing!
Packed with awesome features and perfectly on time, we released a new version of TYPO3 v9.

Was waiting for this for so long, but now I am so slow in getting the projects upgraded from old versions to 8 LTS.

#^Feature Spotlight: Linkhandler

With TYPO3 8 LTS it is now possible to add custom records to the link browser without an extension. This Feature Spotlight shows how to do it.

With the 8LTS release the TYPO3 core integrated a feature that was provided by numerous extensions in the years before: the Linkhandler (read the Feature RST). It is now possible without the need of further extensions to make custom records available in the link browser. So if you e.g. have a product application integrated in your TYPO3 system you can make the products available in the link browser so that your editors can link to products as they can to pages.

The integration of custom records in the link browser is quite easy and consists of two parts.

nice tool when you work with #TYPO3.

TYPO3 Console: Getting things done

The TYPO3 console is a great tool in order to get things done quickly. It provides many commands that will ease your live with TYPO3 a lot. Even if you are not used to command line tools, you should, no, you must have a look at this post.

The new forms framework makes a great impression. Not so sure about the new RTE (CKEditor). No question the old one (htmlArea) was a beast and terrible to configure, but when you once had a right configuration, it was very powerful. We will see how much effort it will be to customize the new editor.

#^TYPO3 v8.5 released

Christmas came early this year - TYPO3 v8.5 has been released just now, including some very exciting and promising changes. This so-called sprint release is one further step towards TYPO3 8 LTS, scheduled to be published in April 2017.

Custom Content Elements made easy – EXT:mask

„Mask“ is a TYPO3 extension which makes it really easy to create custom content elements and enrich backend layouts. This post is about the motivation, the howto and the differences to other “templating“ solutions. I am convinced that this extension will solve most of your requirements for individual content elements.

Use content element relations in TYPO3 extensions

Wouldn’t it be cool to enable editors to use standard or custom content elements in your extensions? The consequence is that you do not have to develop each and every functionality again. In this post I will show you, how you can use all available content elements of your installation.

Even after years working with #TYPO3 I am still impressed by the amazing and powerful configuration possibilities with #TypoScript. Just discovered a very elegant way how to configure the behaviour of the quick search fields in the backend when you want to link another content element.
On one page I want to change the behaviour of this quick search for a specific field in a content element and limit the results that can be searched.

To be concrete in calendar (extension: cal) event content elements (table: tx_cal_event) I want to limit the results that are available as locations for this event (field: location_id) which are queried from the table tt_address. I only want to get results that have set the field tx_cal_controller_islocation in the table tt_address. Of course you could edit the $TCA (Table Configuration Array) of tx_cal_event and change the definition of the suggest wizard globally, but there is a much more flexible and elegant way.

Just put this TSconfig in a PageTS or UserTS depending how you want this behaviour to be deployed, for example for a group of users only or a specific page only.
# Limit Location Suggest Wizard to cal-islocation addresses
TCEFORM.tx_cal_event.location_id.suggest.tt_address.searchCondition = tx_cal_controller_islocation=1


#^Wizards Configuration — Suggest wizard — TCA Reference 7.6 documentation

This renders an input field next to the selector of group-type fields (when internal_type is db) or of select-type fields (using foreign_table). After the user has typed at least 2 (minimumCharacters) characters in this field, a search will start and show a list of records matching the search word. The "suggest" wizard's properties can be configured directly in TCA or in page TSconfig (see TCEFORM properties).

#^TCEFORM ->TCEFORM_suggest — TSconfig Reference 8-dev documentation

Each level of the configuration overwrites the values of the level below it:
    "suggest.default" is overwritten by "suggest.[queryTable]".
    Both are overwritten by "[table name].[field].suggest.default" which itself is overwritten by "[table name].[field].suggest.[queryTable]"
suggest.default:
Configuration for all suggest wizards in all tables
suggest.[queryTable]:
Configuration for all suggest wizards from all tables listing records from table [queryTable]
[table name].[field].suggest.default
Configuration for the suggest wizard for field [field] in table [table name]
[table name].[field].suggest.[queryTable]
Configuration for the suggest wizard for field [field] in table [table name] listing records from [queryTable]

Interesting idea, but wondering who will pay so much for extended support that has not yet cared or planned budget for an upgrade.

#^Announcing TYPO3 CMS 4.5 Extended Long-Term-Support Plans

The TYPO3 CMS version 4.5, released in January 2011, was the first version having the label “Long Term Support” attached to it. After 4 years of support, we hope that everybody has upgraded to our latest version TYPO3 CMS 6.2 LTS (or to CMS 7 which has been released meanwhile). The LTS support is going to end on March 31st, 2015, which already includes only high priority and critical fixes related to browser and security. Still, version 4.5 is among the most popular TYPO3 versions on the web.

I love FLUIDTEMPLATE's new partialRootPaths and layoutRootPaths since TYPO3 CMS 6.2. I just forget EVERY time the reversed order of them.

Finally a content dimension for translations.

#^News - TYPO3 Neos 1.2 Beta released - TYPO3 Neos

by Neos Team on November 14th, 2014
The first beta of TYPO3 Neos version 1.2 has been released for testing. The release first and foremost marks the introduction of translation in Neos. Secondly, a great amount of work has been put into enhancing the author experience with a broad range of features, improvements and fixes. Overall, t...

#CMS #Neos

Somehow it is quite irritating the huge difference between which #PHP version is still used and which PHP versions are still officially supported.

#^PHP minimum requirements for TYPO3 CMS 7

The next major version of TYPO3 CMS will be called 7 and will have PHP version 5.5 as its minimum PHP version. We consider this step vitally important to our new release strategy for several reasons.

What a changelog

#^TYPO3 CMS 6.2.4 - TYPO3Wiki

This document contains information about TYPO3 CMS 6.2.4 which was released on July 8th, 2014. This is part of a combined release of TYPO3 CMS 4.5.35, 6.1.10 and 6.2.4. The usual upgrading procedure applies. No database updates are necessary. Here is a list of what was fixed since 6.2.3: If you have skipped one or more versions while upgrading to t...

Including Content Dimensions finally, so hopefully multi-language will arrive soon.

#^News - TYPO3 Neos 1.1 released - TYPO3 Neos

by TYPO3 Neos Team on June 19th, 2014 We, the Neos Team, are pleased to release TYPO3 Neos 1.1. For this release, we wanted to build a strong foundation for the major features that we are preparing for future releases. As such, we focused on stability and performance improvements. One of the biggest new features in this release is a ...

Heute war es also so weit. Das lang erwartete TYPO3 CMS 6.2 LTS Release ist erschienen #TYPO3CMSLTS
#^TYPO3 6.2 Release Notes

TYPO3 is a free, feature-rich Enterprise class Open Source Web CMS based on PHP with a vast international community of developers and supporters. typo3.org is the official resource for TYPO3 and offers tutorials, downloads, an extension repository and information about the TYPO3 community like mailing lists, blog, events

Leider hatte ich es total verpeilt und auch erst heute Mittag über die Release Party in Bonn erfahren, es aber doch zum Glück noch dahin geschafft. UnserActive contributor vom TYPO3 CMS Philipp hat die Neuerungen und Änderungen der 6.2 vorgestellt und viel dazu erzählt. Die Bonner Internetagentur SimpleThings war so freundlich und hat uns ihre Räumlichkeiten zur Verfügung gestellt und auch für Getränke und Knabbereien gesorgt. Vielen Dank fürs nette Sponsoring und die tolle Location.
Der nächste Bonner TYPO3 Usergroup Stammtisch ist für Anfang Mai geplant zum Thema TYPO3 Migration auf 6.2. Freue mich schon sehr darauf. #TYPO3UG

Multiple Vulnerabilities in TYPO3 CMS

It has been discovered that TYPO3 CMS is vulnerable to Cross-Site Scripting, Information Disclosure, Mass Assignment, Open Redirection and Insecure Unserialize.

Finding these damn two lines are the reason why I am still awake.
plugin.tx_cal_controller {
   view.event.organizer.description = TEXT
   view.event.organizer.description.field = description
}
Now I can finally use the \###MODULE__ORGANIZERLOADER### marker properly in event detail view. So easy and logical.