TYPO3 Logo
TYPO3 Core Changelog
Release: main

Loading data.

  • ChangeLog v13
    • 13.3 Changes
    • 13.2 Changes
    • 13.1 Changes
    • 13.0 Changes
  • ChangeLog v12
    • 12.4.x Changes
    • 12.4 Changes
    • 12.3 Changes
    • 12.2 Changes
    • 12.1 Changes
    • 12.0 Changes
  • ChangeLog v11
    • 11.5.x Changes
    • 11.5 Changes
    • 11.4 Changes
    • 11.3 Changes
    • 11.2 Changes
    • 11.1 Changes
    • 11.0 Changes
  • ChangeLog v10
    • 10.4.x Changes
    • 10.4 Changes
    • 10.3 Changes
    • 10.2 Changes
    • 10.1 Changes
    • 10.0 Changes
  • ChangeLog v9
    • 9.5.x Changes
    • 9.5 Changes
    • 9.4 Changes
    • 9.3 Changes
    • 9.2 Changes
    • 9.1 Changes
    • 9.0 Changes
  • ChangeLog v8
    • 8.7.x Changes
    • 8.7 Changes
    • 8.6 Changes
    • 8.5 Changes
    • 8.4 Changes
    • 8.3 Changes
    • 8.2 Changes
    • 8.1 Changes
    • 8.0 Changes
  • ChangeLog v7
    • 7.6.x Changes
    • 7.6 Changes
    • 7.5 Changes
    • 7.4 Changes
    • 7.3 Changes
    • 7.2 Changes
    • 7.1 Changes
    • 7.0 Changes
  • Documenting Changes
  • Sitemap

Contributors Corner

  • View source of current document
  • How to edit
  • Edit current document on GitHub
  1. TYPO3 Core Changelog
  2. ChangeLog v7
  3. 7.0 Changes
  4. Deprecation: #60574 - Client Related Conditions
Report issue View source How to edit Edit on GitHub

Deprecation: #60574 - Client Related Conditions¶

See forge#60574

Description¶

Conditions that depend on client details are unlovely for a number of reasons:

  • Per condition or permutation of conditions that matches, the frontend creates a different cache entry. This can lead to a very high number of cache entrys per page
  • Conditions based on browser or clients on server side are bad practice.
  • The device information in the core is outdated (for example it is possible to match "AMIGA")
  • Setups like reverse proxies give additional headaches with these types of conditions
  • All client related condition types are deprecated with this patch.

Impact¶

Usage of client related TypoScript conditions will result in a deprecation log message. Client related conditions are browser, version, system and useragent.

Affected installations¶

Installations using TypoScript conditions for browser, version, system or useragent.

Migration¶

  • Most usual conditions for specific browsers can nowadays be turned into conditional CSS includes
  • Use libraries such as modernizr for browser support
  • If conditions for specific clients or devices are still needed, they should be done with a userFunc condition and a project like WURFL that keep the device information more recent than the current core code like matching AMIGA
  • Previous
  • Next
Reference to the headline

Copy and freely share the link

This link target has no permanent anchor assigned. You can make a pull request on GitHub to suggest an anchor. The link below can be used, but is prone to change if the page gets moved.

Copy this link into your TYPO3 manual.

  • Home
  • Contact
  • Issues
  • Repository

Last rendered: Sep 06, 2024 17:37

© since 1997 by the TYPO3 contributors
  • Legal Notice
  • Privacy Policy