TYPO3 450rc1 » History » Revision 4

Revision 3 (Ernesto Baschny, 2011-01-22 22:33) → Revision 4/8 (Ernesto Baschny, 2011-01-22 22:46)

h1. TYPO3 4.5.0 rc1 

 Released 22.1.2011. 

 {{>toc}} 

 This is the first release candidate for the upcoming version 4.5 of TYPO3. It shows a snapshot of our development on the road to 4.5.0, which will be released on January 26th, 2011. 

 h2. Upgrading and compatibility 

 Download the packages from the "download package page at typo3.org":http://typo3.org/download/packages/ (at the bottom). 

 To upgrade an existing installation of 4.4 to 4.5rc1, please consider the following steps: 

 * Visit the Install Tool: 
 ## Run through "Update wizards" which are new in 4.5 (you can now go through them using the "Next" button) 
 ## Don't forget to use the "Database COMPARE" section and apply all database schema changes. 

 To upgrade from an earlier alpha or beta release of 4.5, please follow the same steps mentioned above. 

 * Read about "Extbase/Fluid breaking changes":http://forge.typo3.org/projects/typo3v4-mvc/wiki/Breaking_Changes. Note that from 4.4 to 4.5 you will be upgrading Extbase / Fluid from 1.2 to 1.3. 

 h2. New installations 

 Try out the *introduction package("tar.gz":http://prdownloads.sourceforge.net/typo3/introductionpackage-4.5.0rc1.tar.gz?download) ("zip":http://prdownloads.sourceforge.net/typo3/introductionpackage-4.5.0rc1.zip?download)* which provides a very easy way of installing TYPO3 and having some example setup already in place. 

 h2. Changes since beta4 

 We done various fixes and enhancements between TYPO3 4.5.0beta4 and 4.5.0rc1. For technical details see ChangeLog included in the typo3_src package. For a list of all changes between the current stable 4.4 and 4.5.0beta4, please read: 

 * [[TYPO3 4.5.0alpha1]] 
 * [[TYPO3 4.5.0alpha2]] 
 * [[TYPO3 4.5.0alpha3]] 
 * [[TYPO3 4.5.0beta1]] 
 * [[TYPO3 4.5.0beta2]] 
 * [[TYPO3 4.5.0beta3]] 
 * [[TYPO3 4.5.0beta4]] 

 Here is a list of the most notable changes in rc1 (comparing to beta4): 

 h3. Dropped Plupload 

 After several reviews, discussions and "hot fixes" to make Plupload integration more stable, we decided to remove it again from trunk so it won't be included in the final release. 

 This project will go on and make its way into 4.6 probably together with the FAL (file abstraction layer) integration (so that it could also be based on an abstract uploading API). 

 h3. Cross Site Request Forgery 

 Thanks to the Security Team, we managed to integrate a much more complete CSRF protection in most C(R)UD (create, update, delete) operations that we have in our backend. Testing is still required, and if you see Exceptions in the form "Invalid Security Token", make sure to report that to the bug tracker, and relate your issue to "17153":http://bugs.typo3.org/view.php?id=17153 

 h3. t3lib_htmlmail deprecated 

 Finally we were able to get rid of all calls from core to t3lib_htmlmail, so that we could finally be able to declare it deprecated. This means that the new t3lib_mail API is the way to go since 4.5. 

 Documentation here: http://wiki.typo3.org/Pending_Documentation#t3lib_mail 

 h3. Tons of Major issues fixed 

 Several fixes for the Pagetree made it even more stable and compatible with other extensions. Some other blockers and changes of behaviour were fixed, enhancing the backwards compatibility. 

 Between beta4 and rc1 our package has gone through: 

 4139 files changed, 43730 insertions(+), 21203 deletions(-) 

 According to the issue tracker: 

 * 6 blockers (aka as "show-stoppers") were fixed 
 * 18 major issues solved 
 * 95 minor issues and optimizations included 

 One last known issue: The t3editor "save" button in fileadmin (which doesn't save) is the last missing known "major" issue which will be solved by Tobi before Monday ("17078":http://bugs.typo3.org/view.php?id=17078). 

 h2. Next steps 

 Please take your time to test this rc1, report any new issues you find in our "bug tracker":http://bugs.typo3.org. 

 We now have less than a week until the final release according to our [[Release Plan]]. Until then we will fix all bugs that we can to make a stable version. The final release will be done on 26th January. If necessary and if enough issues arise until Monday afternoon, we will consider releasing a second release candidate (RC2) by then.