silverstripe-framework/core
Ingo Schommer 06ff9f72b1 Increased recent deprecation warnings from 3.1 to 3.2
The deprecations are supposed to denote the release where
the functionality will be removed, as opposed to the one where
its deprecated. Having 3.1 as a target for recent changes
in popular methods like Object::add_extension() causes
too many short-term hassles, there's no "grace period".
2013-03-20 10:00:51 +01:00
..
manifest Mark private static deprecation notice for 3.2 2013-03-19 10:39:11 +01:00
ArrayLib.php Add codesniffer that ensures indentation is with tabs. 2012-12-12 17:33:31 +13:00
ClassInfo.php Removing ClassInfo::is_subclass_of(), use is_subclass_of() instead 2012-11-15 14:43:13 +13:00
Config.php FIX SplFixedArray causes segfaults in old versions of PHP 2013-03-18 10:22:11 +13:00
Convert.php Use preg_replace_callback over preg_replace with e modifier 2012-12-20 13:40:42 +13:00
Core.php Merge branch '3.0' into 3.1 2013-03-19 22:27:09 +11:00
DAG.php FIX Remove instances of lines longer than 120c 2012-09-30 17:18:13 +13:00
Diff.php API Make HTMLValue replace-able via DI 2013-03-14 12:49:02 +13:00
Extension.php Method visibility according to coding conventions 2012-09-20 10:46:59 +02:00
HTMLCleaner.php API Make HTMLValue replace-able via DI 2013-03-14 12:49:02 +13:00
Object.php Increased recent deprecation warnings from 3.1 to 3.2 2013-03-20 10:00:51 +01:00
PaginatedList.php Merge remote-tracking branch 'origin/3.0' into 3.1 2013-01-21 11:14:57 +01:00
TempPath.php Have tiny_mce_gzip.php use local silverstripe-cache folder if available 2012-09-19 16:43:17 +12:00