- May 20, 2016
-
-
Christoph Hofmann authored
-
- Nov 16, 2015
-
-
Christoph Hofmann authored
-
- Nov 04, 2014
-
-
Dmitry Dulepov authored
-
Dmitry Dulepov authored
-
- Oct 07, 2014
-
-
Dmitry Dulepov authored
-
Simon Schaufelberger authored
Deleting of single entries of decode/encode cache fails sometimes since the items are identified by hash and not by id. Since there is an intval for the hash, the int and the hash don't fit together which results in strange behavior. Change-Id: Ibd7bf4fa4236e5e0e61894959187214c9334b6a4 Fixes: #60585
-
- Oct 06, 2014
-
-
Dmitry Dulepov authored
-
- Mar 12, 2014
-
-
Dmitry Dulepov authored
-
- Feb 17, 2014
-
-
Dmitry Dulepov authored
-
- Feb 11, 2014
-
-
Dmitry Dulepov authored
-
Dmitry Dulepov authored
-
Dmitry Dulepov authored
-
- Oct 09, 2013
-
-
Oliver Hader authored
Add a hook to post process auto-generated configuration. This allows individual processing for e.g. * determine default language in multi-tree websites * define language handling per domain name * individual additions Change-Id: I379399e2aa2ae77fcc6babfdae9bf870f0d5a28d Resolves: #52515
-
Dmitry Dulepov authored
-
- Oct 08, 2013
-
-
Dominique Feyer authored
The duplicate check does'nt check if the current alias is a translation of an existing one. In this case I think the warning doesn't make sense. Resolves: #48944 Change-Id: I8aff29e2260b7f8ab7fd86e18bc4d17acf2579bb
-
Dmitry Dulepov authored
-
Stephan Schuler authored
When decoding the current URL, there might be GET vars that need to be excluded from cHash calculation due to settings in the t3lib_cacheHash object. Reincerting a potentially cached cHash should only be done of the remaining GET vars are meant to influence the cHash. Change-Id: I310a9568f6ab679cdf6bbbd9990712936723ecfd Resolves: #51287
-
Dmitry Dulepov authored
-
- Oct 07, 2013
-
-
Dmitry Dulepov authored
-
- Sep 26, 2013
-
-
Dmitry Dulepov authored
-
- Jul 24, 2013
-
-
Dmitry Dulepov authored
-
Helmut Hummel authored
When decoding the URL preVars, a wrong default value is applied when using valueDefault. Resolves: #41515 Change-Id: Iaaab7221a8f05917f06b81aedb65f182bd1bc95a
-
Helmut Hummel authored
When decoding the URL preVars, a wrong default value is applied when using valueDefault. Resolves: #41515 Change-Id: Iaaab7221a8f05917f06b81aedb65f182bd1bc95a
-
Andreas Beutel authored
Resolves: #45938 Change-Id: Ia23b6ac36018cc11aa1d2854d973138e0e35fcdf Reviewed-on: https://review.typo3.org/18551 Reviewed-by: Dmitry Dulepov Tested-by: Dmitry Dulepov
-
Dmitry Dulepov authored
-
- May 20, 2013
-
-
Dmitry Dulepov authored
-
Dmitry Dulepov authored
-
- May 07, 2013
-
-
Dmitry Dulepov authored
-
- May 06, 2013
-
-
Dmitry Dulepov authored
-
Dmitry Dulepov authored
-
- Apr 11, 2013
-
-
Stephan Schuler authored
Change-Id: I40eda279c7403c3226aa0d594ba73b821028837e Fixes: #41363
-
Dmitry Dulepov authored
-
Dmitry Dulepov authored
-
Benjamin Mack authored
As of TYPO3 CMS, the $GLOBALS['TYPO3_DB']->link is protected (and not a resource anymore due to the switch to mysqli). Thus, the check in realurl, if the extended mysql syntax should be used (= enabled when using MySQL 4.1.0 or later and no DBAL), the check should be different. As realurl only supports TYPO3 4.5 and later, and 4.5 requires mysql 5.0, the check is not needed anymore like it is. Change-Id: I10eda5c206fe0a14c901a560359bd66a48330179 Fixes: #46807 Reviewed-on: https://review.typo3.org/19452 Reviewed-by: Benjamin Mack Tested-by: Benjamin Mack Reviewed-by: Oliver Hader Reviewed-by: Stefan Neufeind Reviewed-by: Wouter Wolters Tested-by: Oliver Hader Reviewed-by: Tilo Baller Tested-by: Tilo Baller Reviewed-by: Ingo Pfennigstorf Tested-by: Ingo Pfennigstorf Reviewed-by: Dmitry Dulepov Tested-by: Dmitry Dulepov
-
- Mar 13, 2013
-
-
Dmitry Dulepov authored
-
- Feb 26, 2013
-
-
Dmitry Dulepov authored
Added information to the manual about calling userFunc for alias processing (thanks to Christian Ludwig)
-
- Feb 08, 2013
-
-
Dmitry Dulepov authored
-
Stephan Schuler authored
If a path expires because of content changes that don't affect its URL, the old URL is marked as "expired" but the new one is not inserted. This happens e.g. if a "speaking url path segment" is given for a page and the page title property is changed. Then the URL is marked as "expired" because "title" might affect the URL, but the new URL equals the old one because "title" isn't used but "speaking url path segment". Change-Id: Id58a56460e6a12b24d837fa4a3487fb9428d1989 Fixes: #42295
-
Dmitry Dulepov authored
-
- Jan 29, 2013
-
-
Dmitry Dulepov authored
-