TYPO3 CMS 4.5.25, 4.6.18, 4.7.10 and 6.0.4 released
The TYPO3 Community announces versions 4.5.25, 4.6.18, 4.7.10 and 6.0.4 of the TYPO3 Enterprise Content Management System.
Read moreTYPO3 CMS 4.5.24, 4.6.17, 4.7.9 and 6.0.3 released
The TYPO3 Community announces versions 4.5.24, 4.6.17, 4.7.9 and 6.0.3 of the TYPO3 Enterprise Content Management System.
TYPO3 CMS Code Sprints for 6.1
The final dates are set to go forward with some hard-core-coding for the next TYPO3 CMS Release: The upcoming code sprints for TYPO3 6.1.
Neos Codesprint February 2013
For almost a whole week the Neos core team met in Lübeck for planning the next steps toward the 1.0 release of Neos and implementing some features right away. With, at times, 17 people, this was an intensive sprint with some great results.
ECS13DUS - The Extbase team is bringing it on again
The first code sprint of the TYPO3 CMS project for this year took place last weekend in Duisburg and was hosted by the friendly folks of Rheinschafe GmbH. The Extbase Team met, discussed, worked on issues and got rid of lots of gremlins in that weekend. The timing of tis code sprint leaves enough time to initiate and finalise topics prior to the feature freeze of TYPO3 CMS 6.1 end of March 2013.
TYPO3 Neos 1.0 alpha 3 is now available
Christian Müller tagged the release of TYPO3 Neos 1.0 alpha 3 earlier today.
TYPO3 CMS 4.5.23, 4.6.16, 4.7.8 and 6.0.2 released
The TYPO3 Community announces versions 4.5.23, 4.6.16, 4.7.8 and 6.0.2 of the TYPO3 Enterprise Content Management System.
Ideas for Google Summer of Code 2013
TYPO3 Neos and Flow - January 2013
Announcing TER cleanup process
Everybody recognizes this situation: you're looking for an extension with a certain functionality and after you've installed it all kinds of errors appear about missing functions or even worse, you only see a blank page. Further investigation shows that the extension isn't compatible with your TYPO3 version. For a long time extensions can set the TYPO3 version(s) they are compatible with. Unfortunately not many extension authors use that setting. You could take a look at the date of publication, but even that won't be a sure sign.