It has been suggested that this article should be split into a new article titled Neos (content management). (discuss) (March 2021)
|
This article contains weasel words: vague phrasing that often accompanies biasedorunverifiable information. Such statements should be clarified or removed. (December 2023)
|
This article contains content that is written like an advertisement. Please help improve it by removing promotional content and inappropriate external links, and by adding encyclopedic content written from a neutral point of view. (April 2020) (Learn how and when to remove this message)
|
Original author(s) | Kasper Skårhøj |
---|---|
Developer(s) | TYPO3 Association |
Initial release | 1998; 26 years ago (1998) |
Stable release | |
Repository | |
Written in | PHP, SQL, JavaScript |
Operating system | Windows, Linux, FreeBSD, macOS, OS/2 |
Platform | IA-32, x86-64 |
Size | 18.5 MB |
Available in | 51 languages |
Type | Content management framework, content management system |
License | GNU General Public License version 2 |
Website | typo3 |
TYPO3 is a Web Content management system (CMS) written in the programming language PHP. It is able to run on a variety of web servers, such as Apache, Nginx, or Internet Information Services (IIS), and on many operating systems, including Linux, Microsoft Windows, FreeBSD, macOS, and OS/2. It is free and open-source software released under the GNU General Public License version 2.
TYPO3 is similar to other content management systems such as, Drupal, Joomla! and WordPress. It is used more widely in Europe than in other regions, with larger market share in German-speaking countries, the Netherlands and France.[2][3]
TYPO3 is credited to be highly flexible, as code and content are run separately.[citation needed] It can be extended by new functions without writing any program code. TYPO3 supports publishing content in multiple languages due to its built-in localization system. Due to its features like editorial workplace and workflow, advanced frontend editing, scalability and maturity, TYPO3 makers classify it as an enterprise level content management system.[4][5]
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).[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 in February 2017.[3][8]
TYPO3 provides a base set of interfaces, functions and modules. Most functionality exceeding the base set can be implemented via the use of 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 is able to run on most HTTP servers such as Apache, NginxorIIS on top of Linux, Microsoft WindowsormacOS. It uses PHP 7.2 or newer[10] and any relational database supported by the TYPO3 DBAL including MySQL/MariaDB, PostgreSQL, and SQLite.[11] 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 at least 256 MB RAM and a CPU appropriate for that 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.
Building basic proficiency in TYPO3 takes between a few weeks up to some months. For an author or editor who administers and operates a TYPO3 based website, this requirement can range from a few minutes to a few hours. A developer setting up a website with TYPO3 would need to work intensively with the meta-language Typoscript.[12]
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 CMS's, 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 added 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 added special page types, including:
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.
Designing and developing with TYPO3 is commonly based on the following elements, among others:
###MARKER###
) and range markers, called subparts (e.g., <!-- ###CONTENT### Start --> … <!-- ###CONTENT### End -->
); that were replaced by various content elements or served as a sub template. This template system can still be found in older extensions or installations.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[13] 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.[14]
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]
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, model–view–controller (MVC) based development framework. To ensure backward compatibility, both libraries can be used in the same TYPO3 installation. Extbase is a backport of some features of FLOW3, renamed Neos Flow, a general web application framework.[15]
As it classifies as an enterprise CMS, many global companies and organizations base their web or intranet sites on TYPO3. The majority are 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 organizations running one or more TYPO3 sites are: Airbus, Konica-Minolta, Leica Microsystems, Air France, Greenpeace, and Meda (Sweden).[16][17][18]
Legend: | Old version, not maintained | Older version, still maintained | Current stable version | Latest preview version | Future release |
---|
Branch | Version [19] | Release date | Major changes |
---|---|---|---|
3.x | |||
Old version, no longer maintained: 3.0 | 2001[citation needed] |
| |
Old version, no longer maintained: 3.2 | 17 May 2002 |
| |
Old version, no longer maintained: 3.3 | 3 June 2002 |
| |
Old version, no longer maintained: 3.5 | 18 February 2003 |
| |
Old version, no longer maintained: 3.6 | 30 April 2004 |
| |
Old version, no longer maintained: 3.7 | 24 September 2004 |
| |
Old version, no longer maintained: 3.8 | 23 May 2005 |
| |
Old version, no longer maintained: 3.8.1 | 14 November 2005 |
| |
4.x | Old version, no longer maintained: 4.0 | 7 April 2006 |
|
Old version, no longer maintained: 4.1 | 6 March 2007 | ||
Old version, no longer maintained: 4.2 | 24 May 2008 |
| |
Old version, no longer maintained: 4.3 | 30 November 2009 |
| |
Old version, no longer maintained: 4.4 | 22 June 2010 |
| |
Old version, no longer maintained: 4.5 LTS | 26 January 2011 |
| |
Old version, no longer maintained: 4.6 | 25 October 2011 | ||
Old version, no longer maintained: 4.7 | 24 April 2012 | ||
6.x | Old version, no longer maintained: 6.0 | 27 November 2012[52] | |
Old version, no longer maintained: 6.1 | 30 April 2013 | ||
Old version, no longer maintained: 6.2 LTS | 25 March 2014[58] |
| |
7.x | Old version, no longer maintained: 7.0 | 2 December 2014 |
|
Old version, no longer maintained: 7.4 | 4 August 2015 |
| |
Old version, no longer maintained: 7.5 | 29 September 2015 |
| |
Old version, no longer maintained: 7.6 LTS | 10 November 2015 |
| |
8.x | Old version, no longer maintained: 8.0 | 22 March 2016 |
|
Old version, no longer maintained: 8.1 | 3 May 2016 |
| |
Old version, no longer maintained: 8.2 | 5 July 2016 |
| |
Old version, no longer maintained: 8.3 | 30 August 2016 |
| |
Old version, no longer maintained: 8.4 | 18 October 2016 |
| |
Old version, no longer maintained: 8.5 | 20 December 2016 |
| |
Old version, no longer maintained: 8.6 | 14 February 2017 |
| |
Old version, no longer maintained: 8.7 LTS | 4 April 2017 |
| |
9.x | Old version, no longer maintained: 9.0 | 12 December 2017 |
|
Old version, no longer maintained: 9.1 | 30 January 2018 |
| |
Old version, no longer maintained: 9.2 | 10 April 2018 |
| |
Old version, no longer maintained: 9.3 | 12 June 2018 |
| |
Old version, no longer maintained: 9.4 | 4 September 2018 |
| |
Old version, no longer maintained: 9.5 LTS | 2 October 2018 |
| |
10.x | Old version, no longer maintained: 10.0 | 23 July 2019 | |
Old version, no longer maintained: 10.1 | 1 October 2019 | ||
Old version, no longer maintained: 10.2 | 3 December 2019 | ||
Old version, no longer maintained: 10.3 | 25 February 2020 | ||
Older version, yet still maintained: 10.4 LTS | 21 April 2020 |
| |
11.x | Old version, no longer maintained: 11.0 | 22 December 2020 | Support PHP 7.4 und 8.0 / MySQL 5.7+ / MariaDB / Postgres / SQLite |
Old version, no longer maintained: 11.1 | 23 February 2021 | ||
Old version, no longer maintained: 11.2 | 4 May 2021 | ||
Old version, no longer maintained: 11.3 | 13 July 2021 | ||
Old version, no longer maintained: 11.4 | 7 September 2021 | ||
Current stable version: 11.5 | 5 October 2021 | Long Term Support Release (LTS), fully supported for 3 years until October 2024.[71] | |
12.x | Old version, no longer maintained: 12.0 | 4 October 2022 | First release of TYPO3 12.0[72] |
Old version, no longer maintained: 12.1 | 6 December 2022 | Interoperability with third-party systems[73] | |
Old version, no longer maintained: 12.2 | 7 February 2023 | Improved Backend UI[74] | |
Old version, no longer maintained: 12.3 | 28 March 2023 | Last-Minute Features[75] | |
Current stable version: 12.4 | 25 April 2023 | Long Term Support Version with 3 years of official security and maintenance support[76] | |
13.x | Latest preview version of a future release: 13.0 | 30 January 2024 | First release of TYPO3 13.0 with breaking changes and new system requirements[77] |
13.1 | 23 April 2024 | Reusable components for creating new sites | |
13.2 | 2 July 2024 | Content blocks and new APIs for integrations | |
13.3 | 17 September 2024 | Feature freeze | |
13.4 | 15 October 2024 | LTS-release |
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, now renamed Neos Flow, it along with various other packages then served as the basis for the start of development of project Phoenix.[78]
In September 2012, the TYPO3 developers decided on the name for the new product, "TYPO3 Neos".[79] With TYPO3 Neos 1.0 alpha1, a public test version was released in late 2012.[80][81] 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.[82]
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 TypoScript2toFusion.[83]
{{cite book}}
: CS1 maint: multiple names: authors list (link)
{{cite web}}
: CS1 maint: numeric names: authors list (link)
| |
---|---|
| |
.NET |
|
C++ |
|
ColdFusion |
|
Common Lisp |
|
Haskell |
|
Java |
|
JavaScript |
|
Perl |
|
PHP |
|
Python |
|
Ruby |
|
Rust |
|
Scala |
|
Smalltalk |
|
Other languages |
|