TYPO3 450rc2 » History » Revision 3
TYPO3 4.5.0 rc2¶
- Table of contents
- TYPO3 4.5.0 rc2
This is the second and last release candidate for the upcoming version 4.5 of TYPO3. It represents a final rehearsal for the final release of tomorrow.
Upgrading and compatibility¶
Download the packages from the download package page at typo3.org (at the bottom).
To upgrade an existing installation of 4.4 to 4.5rc2, 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.
Note: If you have a "No page in rootline" problem: Please note that the table name "be_layouts" (and the referring fields in pages) were renamed to "backend_layout" in rc1, so if you have used the grid view before, you will have to go to DB COMPARE in the Install Tool at any case. After that you might need to go to DB Tools > Check Reference Integrity. There is no Upgrade Wizard for this.
- Read about Extbase/Fluid breaking changes. Note that from 4.4 to 4.5 you will be upgrading Extbase / Fluid from 1.2 to 1.3.
Changes since 4.4¶
For a list of all changes between the current stable 4.4 and 4.5.0rc2, 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
- TYPO3 4.5.0rc1
We done various fixes between TYPO3 4.5.0rc1 and 4.5.0rc2. For technical details see ChangeLog included in the typo3_src package. Here is a list of the changes in rc1 (comparing to rc2):
Cross Site Request Forgery¶
New Extension Manager¶
Lots of changes and improvements here. Most bugs are resolved.
Please take your time to test this rc2, report any new issues you find in our bug tracker.
Tomorrow we will package the final release - Version 4.5.0 - according to our Release Plan.
We are happy and proud to have reached such a stable state with such a tight schedule and thank all active developers, reviewers and testers for their dedication and patience to get everything working so nicely at the end.