Contao version 4.3.2 is available. The bugfix release fixes the security vulnerability CVE-2016-10074, which was found in SwiftMailer, a third-party software we are using in Contao.
Contao version 3.5.21 is available. The bugfix release fixes the security vulnerability CVE-2016-10074, which was found in SwiftMailer, a third-party software we are using in Contao.
Contao version 4.3.1 is available. The bugfix release fixes several minor back end problems with e.g. the custom layout sections or the file upload. In addition, the changes from Contao 3.5.20 have been ported.
Contao version 3.5.20 is available. The bugfix release fixes a problem with displaying running repeated events and with sorting pages in the page picker. In addition, a potential XSS weakness found and reported by Pascal Gerundt has been fixed.
Contao version 4.3.0 is available. The feature release includes more flexible custom layout sections, a "save and duplicate" button, an image service and the possibility to exchange the form template. Additionally, the back end theme and the HTTP/2 support have been improved.
Contao version 3.5.19 is available. The bugfix release fixes a problem with rebuilding the search index and with redirecting to the home page, if the language is not part of the URL. Also, two performance optimizations have been implemented, which greatly reduce the number of database queries in the event list and on pages, which are not marked as language fallback.
Contao version 4.2.5 is available. The bugfix release fixes several problems, including an issue with the e-mail address obfuscation and an issue with requesting a new password when a member account is locked. In addition, the front end performance could be massively optimized.
Contao version 3.5.18 is available. The bugfix release fixes several problems, including an issue with showing running events in the list of upcoming events and an issue with creating the administrator user in the install tool. In addition, the requests when rebuilding the search index are now run sequentially to prevent too many simultaneous requests.
