E-Mail E-Mail

Phone

0800-8976326 (inside Germany) or +49 711-94969-60

TYPO3 CMS 6.1 - New features and changes

The new version 6.1 of the TYPO3 CMS was released on 30.04.2013. This new version brings many bug fixes and some new or revised features. In this article, we would like to highlight the most important and interesting ones, which are particularly relevant for the end user (admin, integrator, editor).

FAL and RTE images

When updating to TYPO3 6.1, images that were inserted directly in the RTE (HTMLArea) are now also migrated correctly and moved to the fileadmin/_migrated_/RTE/ folder and indexed.

Shape

Form: Checkbox for confirmation page — Checkbox for confirmation page in the new "Behavior" area

The form wizard now offers the option of activating/deactivating the confirmation page by setting a checkbox.

Deactivate CSV/t3d export in list view

Deactivate export from the Single Table View — Standard setting with buttons / deactivated buttons

TSConfig can now be used to deactivate the export of data in the single table view of the list view.

mod.web_list.noExportRecordsLinks = 1

Delete button in the file list

A delete button is now directly available in the file list.

You also receive visual feedback about the deletion process.

System Environment Check

The scripts for the system check of the Install Tool have been moved to a separate script, which works independently of TYPO3.

During the TYPO3 installation, the server environment is now first checked for an optimal configuration. Warning or error messages are also displayed here if necessary.

New "System environment" section in the Install Tool

Checks the server environment and issues warnings or notices if the configuration is not suitable.

Context menu for Typoscript templates

In the template module, the Typoscript template icon now has a context menu that can be used to quickly copy, delete or deactivate it, for example.

Content element "Heading"

The content element "Heading" is now visible in the CE wizard like all other content elements. Previously, you had to select it later using the select box.

Scheduler

Tasks can be selected/deselected by clicking anywhere in the line. A new button has been added to start a task manually.

Scheduler task "System Status Update"

Several e-mail addresses can now be stored for the notification in the "System Status Update" scheduler task.

typolink function faster

Domain records are kept in a cache so that links generated by typolink are created more quickly. For this to work, however, config.typolinkCheckRootline = 1 must be set.

No more Flash uploader

The Flash uploader for files has been removed and replaced by an HTML5 uploader. However, several files can still be uploaded at the same time by selecting them while holding down the CTRL or CMD key or by drawing a selection frame around the files with the mouse.

noTrimWrap.splitChar

noTrimWrap constructions with empty areas collided with the optionSplit, e.g. in the HMENU. Now you can define a different character using splitChar, for example:

noTrimWrap.splitChar = ,

If a number is used, the corresponding character with this number is used, 10 would correspond to a line feed.

stdWrap for config.pageTitleSeparator

stdWrap is now available for config.pageTitleSeparator. For example, you can simply use spaces next to the separator symbol.

Example:

 config.pageTitleSeparator = *
 config.pageTitleSeparator.noTrimWrap = | | |

FLUIDTEMPLATE cObj settings array support

The settings property has been added to the fluid template cObj. Several values can also be transferred here as an array, which can then also be output in the view.

Example:

lib.globalSettings { # Access to constants works, too.
  foo = value
}

page = PAGE
page.10 = FLUIDTEMPLATE
page.10 {
  file = fileadmin/templates/MyTemplate.html
  settings < lib.globalSettings
}

This can be addressed in the view as follows: {settings.foo}

FLUIDTEMPLATE: Content objects can be used as templates

Previously, existing files had to be transferred as templates. Now you can also use content objects.

Example:

page = PAGE
page.10 = FLUIDTEMPLATE
page.10 {
  template = TEXT
  template.value (
    <h1>{data.title}</h1>
    <div class="maincontent">
      <f:format.raw>{content}</f:format.raw>
    </div>
  )
  partialRootPath = fileadmin/templates/partial/
  variables {
    content < styles.content.get
  }
}

INCLUDE_TYPOSCRIPT for backend layouts

External files can now be integrated via INCLUDE_TYPOSCRIPT in the configuration field of the backend layouts. This means that backend layouts can now also be outsourced and versioned. At the moment, however, the external files can only be read; it is not yet possible to write to these files from the config field.

Example:

<INCLUDE_TYPOSCRIPT:source="FILE:fileadmin/be-layouts/layout_homepage.ts">

Deactivate body tag generation

A new Typoscript option deactivates the automatic generation of the opening body tag in HTML. This can be useful when using Templavoila, for example.

config.disableBodyTag = 1

stdWrap for string-padding (similar to the PHP function str_pad)

The new stdWrap property strPad can be used to extend strings by a certain number of defined characters.

Example:

string = TEXT
string.value = TYPO3
string.strPad {
  length = 10
  padWith = _
  type = both
}

Results in the output of: __TYPO3___

Parameter:

strPad.length
integer
Default: 0
The length of the output string. If the number is negative, less than or equal to the length of the string, nothing is changed.

strPad.padWith
string
Default: (space)
Character or character string used to "pad" the string.

strPad.type
list of keywords
Default: right
Determines the side of the string to be "padded". Possible values are "left", "right" or "both"

Extension Manager

The Extension Manager now offers visual feedback when downloading and installing an extension.

The button for updating the extension list is now recognizable as such.

The form for uploading an extension is more visible.

Click on the version number to call up a list of all versions

Further information on the extension and link to the documentation

Detailed information on the extension and a link to the documentation when you display the versions of an extension.

The button for saving the extension configuration is now located in the header area of the page.

Content element "File links"

The sorting of the output of the content element "File links" now works.

FAL

When creating a new file storage, the LocalDriver is now automatically selected and all settings are visible.
The display of referencing in the information about a file in the file list module now works.
Files with umlauts are renamed correctly during upload, ü becomes ue etc.

Media element

Since FAL, selecting a file via the wizard does not return the path to the file, but only something like file:211, where 211 would be the uid of the file. This did not work in TYPO3 6.0.

Setting the color space in the install tool

Some versions of Imagemagick use the sRGB color space instead of the RGB color space. The [GFX][colorspace] parameter can be used to determine the color space to be used. Possible values: CMY, CMYK, Grey, HCL, HSB, HSL, HWB, Lab, LCH, LMS, Log, Luv, OHTA, Rec601Luma, Rec601YCbCr, Rec709Luma, Rec709YCbCr, RGB, sRGB, Transparent, XYZ, YCbCr, YCC, YIQ, YCbCr, YUV

LocalConfiguration.php is created during installation

Previously, the dummy, government and introduction packages included a typo3conf/LocalConfiguration.php with default values. Now this file is no longer used, instead the file FactoryConfiguration.php is located in the typo3_scr/typo3/sysext/core/Configuration/ directory, which is used as a template for LocalConfiguration.php. If you call TYPO3 in the browser, Bootstrap checks whether the LocalConfiguration.php exists, if not, the Install Tool is called and creates this file from the template.

Remote functions

The system extension "Static Templates" has been completely removed
The HMENU types HMENU_LAYERS, GMENU_LAYERS and GMENU_FOLDOUT have been removed.

Before an upgrade

Before you upgrade to TYPO3 CMS 6.1, you should definitely activate the deprecation log via the install tool. Here you can see whether your own website or extensions use functions that are no longer available with 6.1.

Depending on the number of page views, the page should run for a few hours or possibly even days before the deprecation log is evaluated. Depending on the extensions used, you may have to wait with an upgrade until an updated version of the extension is available.

Conclusion

These were just the most noticeable and interesting changes. Of course, a lot more has happened "under the hood", above all numerous bugs have been fixed and tasks that had been pending for some time have been completed. If you want to find out more about the changes, you can take a look at the changelog or read the PDF on the new features in TYPO3 CMS 6.1, kindly provided by Patrick Lobacher.

For the end user, however, TYPO3 CMS 6.1 brings a few nice improvements, and some shortcomings that were sometimes quite annoying under 6.0 (Extension Manager!) have been fixed. The extent to which problems may occur with installed extensions remains to be seen.

Updated: 17.07.2024