Actions
Task #60574
closed
Deprecate all client related condition matchers
Start date:
2014-07-25
Due date:
% Done:
100%
Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
easy
Sprint Focus:
Updated by Christian Kuhn over 10 years ago
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.
Updated by Gerrit Code Review over 10 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/31820
Updated by Gerrit Code Review over 10 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/31820
Updated by Gerrit Code Review over 10 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/31820
Updated by Anonymous about 10 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 742c8bfa7b73f20541db22ace67c77a142702d53.
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed
Actions