TYPO3

TYPO3

TYPO3 CMS 7 backend
Original author(s) Kasper Skårhøj
Developer(s) TYPO3 Association
Initial release 1998 (1998)
Stable release
8 LTS (8.7.4) / July 24, 2017 (2017-07-24)[1]
Preview release
8.6.1 / February 14, 2017 (2017-02-14)[1]
Repository git.typo3.org/Packages/TYPO3.CMS.git
Development status Active
Written in PHP, SQL, JavaScript
Platform Cross-platform
Size 21.5 MB
Available in 51 languages
Type Content management framework, Content management system
License GNU General Public License
Website typo3.org

TYPO3 is a free and open source web content management system written in PHP. It is released under the GNU General Public License. It can run on several web servers, such as Apache or IIS, on top of many operating systems, among them Linux, Microsoft Windows, FreeBSD, macOS and OS/2.

TYPO3 is, along with Drupal, Joomla! and WordPress, among the most popular content management systems worldwide, however it is more widespread in Europe than in other regions. The biggest market share can be found in German-speaking countries.[2][3]

TYPO3 is credited to be highly flexible. It can be extended by new functions without writing any program code. Also, the software is available in more than 50 languages and has a built-in localization system, therefore supports publishing content in multiple languages. Due to its features, scalability and maturity, TYPO3 is used to build and manage websites of different types and size ranges, from small sites for individuals or nonprofit organizations to multilingual enterprise solutions for large corporations. According to the ability to support a corporate environment, it classifies itself as an enterprise level content management system.[4][5]

History and usage

TYPO3 was initially authored by the Dane Kasper Skårhøj in 1997.[6] It is now developed by over 300 contributors under the lead of Benjamin Mack (Core team leader) and Mathias Schreiber (Product Owner).[7]

Calculations from the TYPO3 Association show that it is currently used in more than 500,000 installations. The number of installations detected by the public website "CMS Crawler" was around 384,000 by February 2017.[3][8]

Features

Delivered with a base set of interfaces, functions and modules, TYPO3's functionality spectrum is implemented by extensions. More than 5000 extensions are currently available for TYPO3 for download under the GNU General Public License from a repository called the TYPO3 Extension Repository, or TER.[9]

TYPO3 can run on most HTTP servers such as Apache or IIS on top of Linux, Microsoft Windows or macOS. It uses PHP 5.3 or newer and any relational database supported by the TYPO3 DBAL including MySQL, Oracle, PostgreSQL, and others. Some 3rd-party extensions - not using the database API - support MySQL as the only database engine. The system can be run on any web server with a modern CPU and at least 256 MB RAM. The backend can be displayed in any modern browser with JavaScript. There is no browser restriction for displaying user-oriented content generated by TYPO3.

Since version 4.5, TYPO3 is published with a demo website called "Introduction Package". It enables first-time users to get an working example website quickly and to experiment with built-in features. The package can be enabled from the install tool.[10]

System architecture

Conceptually, TYPO3 consists of two parts: the frontend, visible to visitors, and the administrative backend. The frontend displays the web content. The backend is responsible for administration and managing content. The core functions of TYPO3 include user privileges and user roles, timed display control of content (show/hide content elements), a search function for static and dynamic content, search-engine friendly URLs, an automatic sitemap, multi-language capability for frontend and backend, and more.

Like most modern CMSes, TYPO3 follows the policy of separation of content and layout: The website content is stored in a relational database, while the page templates are stored on the file system. Therefore, both can be managed and updated separately.

TYPO3 defines various basic types of content data. Standard content elements are described as text, text with media, images, (plain) HTML, video etc. Various additional types of content elements can be handled using extensions.

The fundamental content unit is a "page". Pages represent a URL in the frontend and are organized hierarchically in the backends' page tree. Standard pages serve as "containers" for one or multiple content elements. There are several additional special page types:

Internally, TYPO3 is managed by various PHP arrays. They contain all the information necessary to generate HTML code from the content stored in the database. This is achieved by a unique configuration language called TypoScript.

Design elements

Designing and developing with TYPO3 is commonly based on the following elements, among others:

Page tree
Representation of all pages of a site, their structure and properties
Constants
System-wide configuration parameters
Template
Since TYPO3 6, the template engine Fluid is an agreed standard. It combines HTML markup with simple control structures. It can be extended by custom view helpers.
Until version 4.3, an HTML skeleton was used, with markers (e.g., „###MARKER###“) and range markers, called subparts (e.g., <!-- ###CONTENT### Start --><!-- ###CONTENT### End -->); that were replaced by various content elements or served as a subtemplate. This template system can still be found in older extensions or installations.
TypoScript
TypoScript is a purely declarative configuration language. In Typoscript, configuration values are defined, which are parsed into a system-wide PHP array. TypoScript is object-based and organized in a tree-like structure.
Extensions
Additional plug-ins to enable additional functions. See Extensions
PHP
As TYPO3 CMS is written in PHP, therefore most features can be modified or extended by experienced users. Mentionable here is the XCLASS mechanism, by which classes and methods can be overwritten and extended. If available, hooks are preferred.

Extensions

Extensions are the cornerstone in the internal architecture of TYPO3. A feature that was introduced with version 3.5 in 2003 is the Extension Manager, a control center managing all TYPO3 extensions. The division between the TYPO3 core and the extensions is an important concept which determined the development of TYPO3 in the past years. Extensions are designed in a way so they can supplement the core seamlessly. This means that a TYPO3 system will appear as a unit while actually being composed of the core application and a set of extensions providing various features.[11]

Diagram of the basic TYPO3 system architecture

They can be downloaded from the online repository (TER) directly from the backend, and are installed and updated with a few clicks. Every extension is identified by a unique extension key (for example, tt_news). Also, developers can share new or modified extensions by uploading them to the repository.[9]

Examples for popular extensions:

Generally, extensions are written in PHP. The full command set of PHP 5.3 can be used (regarded the system requirements of the specific TYPO3 version), but TYPO3 also provides several library classes for better efficiency: Best known and most used is the piBase library class. With introduction of TYPO3 4.3 in 2009, piBase has been replaced (or extended) by the Extbase library, which is a modern, MVC-based development framework. To ensure backwards compatibility, both libraries can be used in the same TYPO3 installation. Extbase itself is a backport of some features of FLOW3, a general web application framework.[12]

Notable projects

As it classifies as an enterprise CMS, many global companies and organisations base their web or intranet sites on TYPO3. The majority is based in german-speaking countries, such as the state of Saxony-Anhalt, the german Green Party, the University of Lucerne (Switzerland), the University of Vienna (Austria) and the Technical University of Berlin. International organisations running one or more TYPO3 sites are: Airbus, Konica-Minolta, Leica Microsystems, Air France, Greenpeace and Meda (Sweden).[13][14][15]

Releases

Version history

Legend: Old version Older version, still supported Current stable version Latest preview version Future release
Branch Version [16] Release date Major changes
3.x
Old version, no longer supported: 3.0 2001
  • First public release[17]
Old version, no longer supported: 3.2 May 2002
  • Several bug fixes[18]
Old version, no longer supported: 3.3 3 June 2002
Old version, no longer supported: 3.5 18 February 2003
  • Several bug fixes
  • Introducing the Extension Manager - users can now write their own extension modules
Old version, no longer supported: 3.6 30 April 2004
  • Create XHTML code in standard content elements
  • XML storage for content elements
  • Introducing basic database abstraction concept[20][21]
Old version, no longer supported: 3.7 24 September 2004
  • Simplified content-localisation
  • Extended permission system
  • Renewed TypoScript-Engine
Old version, no longer supported: 3.8 23 May 2005
  • Multi-language ability for the backend (introducing language packs)
  • GraphicsMagick support
  • Improved frontend search[22]
Old version, no longer supported: 3.8.1 14 November 2005
  • Several bug fixes and security improvements[23]
4.x Old version, no longer supported: 4.0 7 April 2006
Old version, no longer supported: 4.1 6 March 2007
  • Improved page tree with Ajax
  • Introducing Inline Relational Record Editing (IRRE)[26]
  • Improved UTF-8 support and enabling of InnoDB features
  • Current version: 4.1.15[16][24][27]
Old version, no longer supported: 4.2 24 May 2008
  • Many GUI improvements in the backend, including AJAX features, extended features of the text editor
  • Improvement of frontend login and extension update process
  • Current version: 4.2.17[28]
Old version, no longer supported: 4.3 30 November 2009
  • Modified frontend editing
  • Flash uploader and recycle bin for the backend
  • New system reports & system scheduler
  • Introducing the new caching framework
  • Security improvements with Salt (cryptography) & RSA
  • Integration of Extbase & Fluid features
  • Current version: 4.3.14[29]
Old version, no longer supported: 4.4 22 June 2010
  • Full backend redesign incl. performance improvements
  • Simplified installation, first Introduction Package - a complete website template
  • CSS and javascript compression, HTML5 support in frontend
  • Current version: 4.4.15[30][31]
Old version, no longer supported: 4.5 LTS 26 January 2011
  • First release with long-term support (LTS), until March 2015,[32][33] incl. support of IE6
  • Extended long-term support (chargeable), until March 2016[34]
  • UTF-8 as default charset and HTML5 in backend[35]
  • Refurbished backend forms and extension manager
  • Integrated protection against CSRF
  • Current version: 4.5.40[1][36][37][38][39]
Old version, no longer supported: 4.6 25 October 2011
  • Internationalization with XLIFF
  • New website form content element
  • Security & performance improvements
  • Current version: 4.6.15[40][41][41][42][43]
Old version, no longer supported: 4.7 24 April 2012
  • Complete Accessibility for new installations acc. to WCAG[44]
  • Introducing new HTML5 elements like <audio> & <video>, improvements for TCEforms[45]
  • Introducing the Government Package
  • Current version: 4.7.19[46][47][48]
6.x Old version, no longer supported: 6.0 27 November 2012[49]
Old version, no longer supported: 6.1 30 April 2013
  • Automatic updates for the Core and for translations, e.a.[53][54]
  • Latest version: 6.1.11 [16]
Older version, yet still supported: 6.2 LTS 25 March 2014[55]
  • Second release with Long Term Support (LTS), until April 2017[32]
  • File Abstraction Layer (FAL) re-worked
  • Install Tool re-written and Distribution Management added
  • Responsive image rendering and mobile device preview
  • New documentation module added
  • Enhanced security features
  • Latest version: 6.2.28 (2016-11-01) [16]
7.x Old version, no longer supported: 7.0 02. December 2014
  • general code cleanup, speed improvements through outsourcing of an old compatibility layer, refresh of the visual appearance of the backend.[56]
Old version, no longer supported: 7.4 04. August 2015
  • Backend Overhaul Vol 2
Old version, no longer supported: 7.5 29. September 2015
  • general code base improvements, Backend Overhaul Vol 3
Current stable version: 7.6 LTS 10. November 2015
  • Third release with Long Term Support (LTS), support until November 2018[32]
8.x Old version, no longer supported: 8.0 March 2016
  • general code cleanup, speed improvements through outsourcing of the old compatibility layer, refresh of the visual appearance of the backend. Usage of performance improvements through PHP7 requirement.[56]
Old version, no longer supported: 8.1 3. May 2016
  • Most notable: Doctrine integration, UX rework of workspace module, general cleanup.[57]
Old version, no longer supported: 8.2 05. July 2016
  • Ogg, flac and opus media support
  • Removed support for compatibility6 extension.[58]
Old version, no longer supported: 8.3 30. August 2016
  • Doctrine DBAL migration
  • Tree rendering with SVGs
  • Unified linking syntax
  • PHP 7.1 support[59]
Old version, no longer supported: 8.4 18. October 2016
  • Mobile backend
  • Documentation API
  • Easier migrations
  • Access flexform values by TypoScript.[60]
Old version, no longer supported: 8.5 20. December 2016
  • New form framework,
  • Integration of CKEditor [61]
Current stable version: 8.6 14. February 2017
  • Improvements in frontend editing.[62]
Future release: 8.7 LTS 04. April 2017
  • Long Term Support Release (LTS), bugfixes for 18 months, security support for 36 months, until March 2020.[63]

Neos

A completely rewritten version (code-named "Phoenix") was originally planned as TYPO3 version 5.0. While working on this new release and analyzing the 10-year history and complexity of TYPO3 v4, the TYPO3 community decided to branch out version 5 as a completely separate product, one that wouldn't replace version 4 in the near future and as such needed to have its own name. Published as FLOW3, it along with various other packages then served as the basis for the start of development of project Phoenix.[64]

In September 2012, the TYPO3 developers decided on the name for the new product, "TYPO3 Neos".[65] With TYPO3 Neos 1.0 alpha1, a public test version was released in late 2012.[66][67] In May 2015 the TYPO3 Association and the Neos team decided to go separate ways, with TYPO3 CMS remaining the only CMS product endorsed by the Association and the Neos team publishing Neos as a stand-alone CMS without any connection to the TYPO3 world. [68]

In January 2017, Neos 3.0 has been published, along with a new version of Flow framework and a name change of its configuration language from TypoScript2 to Fusion[69]

See also

References

  1. 1 2 3 "Download". TYPO3 - The Enterprise Open Source CMS.
  2. "Distribution of Content Management Systems among websites that use German". w3techs.com.
  3. 1 2 "TYPO3". cmscrawler.com.
  4. TYPO3 - The Enterprise CMS
  5. Hinderink e.a., Werner Altmann; René Fritz; Daniel (2005). TYPO3 : enterprise content management (1. ed.). Birmingham [u.a.]: Packt Publ. ISBN 1-904811-41-8.
  6. "The History of TYPO3". The History of TYPO3. Retrieved 2012-04-11.
  7. "TYPO3 Core development".
  8. "TYPO3 in numbers". TYPO3 - The Enterprise Open Source CMS.
  9. 1 2 "Extension Repository". TYPO3 - The Enterprise Open Source CMS.
  10. "Introduction Package". wiki.typo3.org. Retrieved 9 February 2017.
  11. "What are extensions?". TYPO3 - The Enterprise Open Source CMS.
  12. Official Extbase MVC Framework Documentation
  13. "TYPO3 case studies". typo3.org. Retrieved 9 February 2017.
  14. "Recently added sites". TYPO3 Reference Blog. Retrieved 9 February 2017.
  15. "Case studies". typo3.com.
  16. 1 2 3 4 5 http://typo3.org/download/ Information on support cycles of TYPO3 versions
  17. Installation manual for TYPO3 3.0
  18. Installation manual for TYPO3 3.0 w/ Screenshots of version 3.2
  19. "TYPO3". sourceforge.net.
  20. Source code of all newer versions with release dates
  21. Jo Bager (3 May 2004). "Typo3 3.6.0 fertig gestellt". heise online.
  22. "Category:ReleaseNotes/TYPO3 3.8.x". typo3.org.
  23. release notes for TYPO3 3.8.1
  24. 1 2 http://typo3.org/news/article/support-for-typo3-40-is-officially-over/ End of life of TYPO3 4.0
  25. "TYPO3 4.0". typo3.org.
  26. "Inline Relational Record Editing". TYPO3 Wiki.
  27. "TYPO3 4.1". typo3.org.
  28. "TYPO3 4.2". typo3.org.
  29. release notes for TYPO3 4.3
  30. release notes for TYPO3 4.4
  31. t3n Redaktion. "TYPO3 4.4: TYPO3 wird einsteigerfreundlicher, schöner, schneller – Hier die wichtigsten Neuerungen". t3n Magazin (in German).
  32. 1 2 3 "TYPO3 Roadmap".
  33. "4.5 LTS support extended because of 6.2 final release postponed, since they have promised to keep the LTS overlapping period 12 months.".
  34. "Announcing TYPO3 CMS 4.5 Extended Long-Term-Support Plans". typo3.org.
  35. "TYPO3 450alpha3 - TYPO3 4.5 Projects - TYPO3 Forge". typo3.org.
  36. "Overview - TYPO3 4.5 Projects - TYPO3 Forge". typo3.org.
  37. "buzz.typo3.org: TYPO3 4.5 will be the most secure TYPO3 version ever.". typo3.org.
  38. Ernesto Baschny. "TYPO3 4.5 LTS Status Report T3CON10". slideshare.net.
  39. Ernesto Baschny. "TYPO3 4.5 Kick-Off Presentation #t3dd10". slideshare.net.
  40. TYPO3 4.6 release date rec. 6. October 2012
  41. 1 2 "Login". TYPO3 - The Enterprise Open Source CMS.
  42. "Login". TYPO3 - The Enterprise Open Source CMS.
  43. typo3.org: A Brief Introduction to TYPO3 version 4.6
  44. TYPO3 Receives German Governmental Funding for Accessibility and Usability Project, rec. 27 Juli 2011
  45. "Feature #12664: Idea about faster loading modules - Core - TYPO3 Forge". typo3.org.
  46. "Wiki - TYPO3 4.7 Projects - TYPO3 Forge". typo3.org.
  47. "TYPO3 4.7 release notes".
  48. "Home: TYPO3 Government Package". typo3.org.
  49. http://typo3.org/news/article/typo3-60-release-schedule/
  50. "Development Report: File Abstraction Layer". TYPO3 - The Enterprise Open Source CMS.
  51. TYPO3 6.0 Release Timeline - typo3.org
  52. "TYPO3 6.0 - Back to the Future". TYPO3 - The Enterprise Open Source CMS.
  53. 1 2 "The TYPO3 Core Team is giving a short summary about the upcoming releases of TYPO3.". TYPO3 - The Enterprise Open Source CMS.
  54. "Feature #43703: Add a task to auto update languages - Core - TYPO3 Forge". typo3.org.
  55. "New release plan for 6.2 LTS". Retrieved 8 December 2013.
  56. 1 2 http://typo3.org/news/article/retaining-compatibility-to-typo3-cms6/
  57. https://typo3.org/news/article/typo3-v81-tightening-the-screws/. Missing or empty |title= (help)
  58. https://docs.typo3.org/typo3cms/extensions/core/8-dev/Changelog/8.2/. Missing or empty |title= (help)
  59. https://typo3.org/news/article/releasing-typo3-v83/. Missing or empty |title= (help)
  60. https://typo3.org/news/article/releasing-typo3-v84/. Missing or empty |title= (help)
  61. https://typo3.org/news/article/typo3-v85-released/. Missing or empty |title= (help)
  62. https://typo3.org/typo3-cms/roadmap/. Missing or empty |title= (help)
  63. https://typo3.org/typo3-cms/roadmap/. Missing or empty |title= (help)
  64. "The TYPO3 Core Team is giving a short summary about the upcoming releases of TYPO3".
  65. Dambekalns, Karsten. "TYPO3 Neos and Flow - September 2012". TYPO3 Association. Retrieved 12 October 2012.
  66. "TYPO3 Neos Alpha Releases". TYPO3 Association. Retrieved 9 May 2013.
  67. "Change Log Neos 1.0.0 alpha2". TYPO3 Association. Retrieved 9 May 2013.
  68. "Neos and TYPO3 split".
  69. "Neos 3.0 and Flow 4.0 Released". neos.io. Retrieved 9 February 2017.

Further reading

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.