Login / Status
developer.Resource
Home . Development . Articles . Changes in TYPO3 4.0.1
Sponsors
hosted by punkt.deTYPO3 and Open Source Magazine
  Intended Audience Backend skin >> 

By Thomas Esders 

Although the TYPO3 developers clearly write down all changes, it is not very easy to understand and convenient for people who just want to know the interesting changes. This document aims to give you a short sum-up.

Intended Audience

This document is made for all TYPO3 users who would like to have a short overview of what has changed in the new TYPO3 release version 4.0.1. This is a maintenance release, it does not contain any feature enhancements.  

Installation and upgrade

The update to this version should be straight forward. For details on how to update a TYPO3 installation see [1]. For latest news on this TYPO3 release see [2]. 

The Update Wizard which was introduced in TYPO3 4.0 has been slightly reworded to make the functionality more easy to understand. Additionally, the typo3temp/ subdirectories were not created automatically which caused warnings in the Install Tool. This bug has been fixed. 

Important bugfixes

In this release, more than 60 bugs have been fixes. Here are some of the most important: 

  1. The HTTP status was incorrect for pageNotFound_handling when external URL is specified as 404 page 

  2. The Mail forms did not work with <input type="image"> submit buttons 

  3. Frontend Editing: edit form on page did not work in TYPO3 4.0 

  4. Several issues for "CSS styled content" have been resolved 

  5. Linking images to hidden pages resulted in click-enlarge 

  6. Wrong HTTP status 503 was sent when $TSFE->set_no_cache() was called from a plugin 

  7. config.formMailCharset did not work 

  8. Some broken references to the “media” folder have been fixed 

  9. Fixed RTE bug: images were removed under some special conditions when saving 

  10. config.spamProtectEmailAddresses returned garbled links sometimes 

  11. Localized flexforms did not work properly 

  12. Extension manager: The label for enabling unreviewed extensions is more clear now. The search scope (all/reviewed) is displayed on the import extensions page.