[!!!][TASK] Deprecate all client related condition matchers 20/31820/4
authorSascha Egerer <sascha.egerer@dkd.de>
Fri, 25 Jul 2014 16:45:03 +0000 (18:45 +0200)
committerGeorg Ringer <georg.ringer@gmail.com>
Mon, 8 Sep 2014 13:17:44 +0000 (15:17 +0200)
commit742c8bfa7b73f20541db22ace67c77a142702d53
tree675cf69f5dcdb505fbfa1402c4184677ecca2149
parenta37fce1798901607bbd5377bcafe1b26f827979d
[!!!][TASK] Deprecate all client related condition matchers

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
* Most usual conditions for specific browsers can nowadays turned into
  conditional CSS includes
* Conditions based on browser or clients on server side are
  bad practice.
* 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
* Setups like reverse proxies give additional headaches with these
  types of conditions
* All client related condition types are deprecated with this patch.

Resolves: #60574
Releases: 6.3
Change-Id: Ib9e78748e87a2f7e04fa1b606415ad1d8d302374
Reviewed-on: http://review.typo3.org/31820
Reviewed-by: Susanne Moog <typo3@susannemoog.de>
Tested-by: Susanne Moog <typo3@susannemoog.de>
Reviewed-by: Markus Klein <klein.t3@reelworx.at>
Tested-by: Markus Klein <klein.t3@reelworx.at>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com>
typo3/sysext/core/Classes/Configuration/TypoScript/ConditionMatching/AbstractConditionMatcher.php
typo3/sysext/core/Documentation/Changelog/master/Deprecation-60574-ClientRelatedConditions.rst [new file with mode: 0644]