home » IT technologies » The application thread typo3 could not be started. Configuring typo3 (for beginners to help from experienced). Now piece by piece

The application thread typo3 could not be started. Configuring typo3 (for beginners to help from experienced). Now piece by piece

In this article I will try to tell you what TYPO3 is, what advantages and disadvantages this CMS has, how TYPO3 differs from other CMS and what its scope is. This article is most likely for those who have never worked with TYPO3 before. I have no doubt that on Habré there are people with more experience than mine, and I hope that they will correct me if I am wrong somewhere.

What is TYPO3

TYPO3 positions itself as a site management system for the enterprise. Kasper Skårhøj started developing this system back in 1998. CMS is distributed free of charge under the GNU GPL license, written in PHP using MySQL DBMS (theoretically supports others). TYPO3 became a brand after the commercial success of the third version. The version number has long jumped to the four, but the three in the name has remained since then. The current version is TYPO3 4.6.0.

Why is TYPO3 better than Drupal, Joomla or% CMS%?

In fact, comparing these systems with each other is a thankless task, since they occupy different market niches. For example, Drupal is much better for sites where visitors are expected to contribute to content creation. In Joomla, the editor will be able to quickly figure out how to properly format the text. Why do you need TYPO3 then? Like any CMS, TYPO3 has its advantages and disadvantages. The advantages include flexible configuration of user rights, the ability to use one installation for several independent sites and domains, the ability to use extensions from TER (TYPO3 extension repository) and versioning. The main disadvantages are the complexity of editing, a complex system of options and settings, slow rendering of large pages. One of the main features of TYPO3 - typoscript - is a double-edged sword. On the one hand, most of the settings can be changed without going into the PHP code of the CMS or its extensions, which makes it easier to update the system. On the other hand, you need to learn the typoscript (syntax and basic "options"), in addition, when configuring extensions, the horror begins with smoking manuals (if any), since the names of options for extensions are limited only by the developer's imagination. It is contraindicated to take TYPO3 if:

the customer has a small budget
the customer wants a portal with content from visitors
need a built-in online store
the customer does not want to teach editors
the site has less than 20 or more than 5000 pages
the customer needs a built-in CRM / the customer wants his CRM to work with the site

Naturally, with the help of a large file and straight hands, you can overcome these contraindications, but you should think about whether it is easier to take something else. The ideal niche for using TYPO3 is for small and medium sized companies.

Extensions, extensions ...

Plugins are called extensions in TYPO3. A bunch of these extensions can be found in TER and installed directly through TYPO3. If the required extension is not available, then you can write it yourself. For this, it is recommended to read the documentation for the TYPO3 API, otherwise the result will be quite disastrous. The extensions themselves are available for every taste and color. Some we will see directly on our page (for example, forms or flash films), others will expand the capabilities of the system (for example, using a database to save images) and will not be visible to the visitor, most extensions will do both - the visitor is shown the content and you are given tools to customize this content (news, image galleries, etc.).

TypoScript

TypoScript is not a programming language, it is used only for configuration and is purely declarative. One of the most important features of TypoScript is the ability to write conditions and define constants. On large pages, depending on which branch of the site is a certain page, for example, the number of columns changes. It is logical to use a condition for this, and in a constant you can write the internal ID of the page from which the branch starts. TypoScript is also used to configure extensions (for example, you can adjust the number of news displayed on one page). As a result, TypoScript will be loaded into one large array into which the TYPO3 engine will look during rendering.

How does a TYPO3 site begin?

Oddly enough, it all starts with a regular HTML page that will be used as a template. Usually, so-called markers are inserted into the page (an example can be seen in the picture). After we have prepared the HTML template, we should create a test page in the backend. Then you can start with the TypoScript template. In its simplest working form, TypoScript will simply populate the template with whatever is written in the backend. An alternative to markers is the TemplaVoila extension, which allows you to bind places for output to tags used in an HTML template by id. TemplaVoila also gives the editor more flexible column settings, but the first option is better versioned using CVS, since all information about the template is written to files and not to the database.

His majesty the backend

It will take several articles to describe all the functionality of the backend, here I will only briefly mention the basics. The backend can be divided into three parts: menu, pagetree and work-area (from left to right).

The site structure in TYPO3 is always visible as a tree. In the picture, four sites are combined into one TYPO3 installation. They have different designs, different content and are available under different domains. This can be convenient if the customer needs a separate page for a new project, but does not want to retrain for a new CMS, and the server can be left as it is.

Work-area

On the right we see the work-area. It is here that all data, texts, pictures and other things are entered. Unlike the menu and pagetree, which practically do not change, the work-area changes in accordance with the combination of the selected menu item and page.

Last but not least

At the end of this article, I would like to say that TYPO3 writes pages to the cache (without a cache, TYPO3 is a perversion), has an easily customizable search engine (for large sites there is an extension for solr), can export to PDF, supports RSS, can authorize users via LDAP, can draw pictures with imagemagick / gd and many other cool things. TYPO3 has long been an international project with a large community.
I would be glad if I managed to interest someone in

13.09.2017 11:02

Timeweb customers can install TYPO3 CMS directly from their hosting control panel. Try TYPO3 CMS on Timeweb hosting:

History

The history of TYPO3 CMS dates back to 1997-98, the author of the system is Kasper Skårhøj (Kasper Skorhøj). Distribution - GNU GPL license (free software). Technologies - PHP and MySQL (but supports Oracle Database, PostgreSQL and other DBMS); works on popular servers and operating systems (Linux, Microsoft Windows, FreeBSD and other OS).

TYPO3 CMS became famous after the release of the third version; the current one is 8.7.4, released on July 25, 2017 (documentation).

TYPO3 is both a CMS (i.e. a content management system) and a CMF (i.e. a framework that can be used to create your own content management system). The decision to use TYPO3 as a CMF allows developers to make, firstly, a more convenient admin panel, and secondly, a lighter weight site as a whole (since only the necessary functions will be used).

In short, TypoScript is a special language designed to customize websites and design them. It is not a programming language. It is also important to define that a template in TYPO3 CMS is not just the template that defines the content of the page displayed on the site, but also the TypoScript template, which can then be used to create other pages.

By the way, you can use TemplaVoila to create templates! - a template engine, with which you can turn an HTML template into a TYPO3 template. It is important that this extension has the ability to create dynamic content elements, which allows flexible management of site content.

Why is TYPO3 CMS better than other engines?

This question itself is too provocative to ask, but users are always interested - why should I use this particular platform and not WordPress (Joomla! Etc.)?

TYPO3 CMS is a good platform for a medium to large project, a site for which flexibility and extensibility is important. Of course, the flexibility of the engine translates into the fact that a competent specialist must work with it, who can understand the settings system and understand the work of TypoScript.

If you are acting as a customer (or just wondering what to create a website on), then TYPO3 CMS will suit you if:

you have an average or large budget for website development;
your site is not an online store or a social network;
the number of pages will be approximately average (not small - 10-20, but not large - 5-6 thousand);
will not use built-in CRM.

This does not mean that it is impossible to implement the above in TYPO3; this means that the implementation will be problematic, so it is easier to take some other, more suitable CMS.

To summarize, TYPO3 is perfect for mid-sized companies.

Extensions

Extensions are plugins that can be selected in TER and then installed via TYPO3 CMS using the Extension Manager in the menu. TER - TYPO3 Extension Repository (TYPO3 extensions repository) and it is located. This is the official collection of extensions for TYPO3.

As in other CMS, here extensions have very different functionality: some of them affect only the appearance of the pages, others are responsible for internal capabilities; most of it affects the internal and external sides of the site (talking about news, galleries, etc.). You will have a lot of room to customize these extensions.

Installation

As already mentioned, on Timeweb you can install the engine directly from the control panel; in other cases, you will have to use the official instructions: https://typo3.org/download/

After installation, the admin panel is available at: website address / typo3 /

A separate feature of TYPO3 CMS is the presence of two interface areas, internal and external. The first is responsible for site management, editing; the second is the interface that is generated and displayed on the site, it is available to all visitors.

The administrative part may seem a little more complicated than in other CMS. To work with TYPO3 CMS, it is desirable to have experience in administration and website creation. However, for routine, simple actions, deep programming knowledge is not required - everything can be done from the control panel.

useful links

Official website: https://typo3.org/
Russian-speaking community:

Recently there was a need to write an internet site (store). Since writing by hand is not very convenient, you need to use a CMS. And so, I began to choose. I am not a WEB developer in the full sense of the word. Therefore, I ask you to consider everything described here simply as my deepest IMHO, and treats with understanding.

Choosing a CMS.

The choice of CMS came down to the fact that after reading reviews, I chose the following CMS:
- osCommerce (like because there are many stores on it, many developers, and all sorts of add-ons)
- textpattern (like because it is simple and flexible)
- MODx (like the reviews)
- Joomla (well, hoolie)
- TYPO3 (complex, many large corporations use it, cool (Gazprom, Philips, Cisco, various banks))

Installation

I started to play. I didn't like osCommerce. textpattern is kind of dumb. MODx - not installed. Joomla didn't.
Changed php version to earlier (5.2).
In the meantime, I went to the TYPO3 demo, and my heart skipped a beat. The admin panel is simple, clear and concise. True, I immediately thought that it would become a fig, since such "simple" systems as Joomla did not.
However, TYPO3 4.5 was delivered, immediately localized, and hurray. Everything works.
I put it according to the instructions.

Installing TYPO3

And so, the configuration of my "server":
Notebook Acer 2490 :-)
Windows XP SP3
Apache: httpd-2.2.17-win32-x86-openssl-0.9.8o
MySQL: mysql-essential-5.0.18-win32
PHP: php-5.2.17-Win32-VC6-x86

We type in the address bar of the browser "your domain / typo3 /" so we start the installation. The system displays a message stating that the installer is currently disabled. This is done for security so that no one can invoke the installer without ftp access. To enable the Install Tool, you need to create an empty file "ENABLE_INSTALL_TOOL" (the file has no extension) and copy it to the folder "your domain / typo3conf /".

After creating and copying the file, go back to the browser and refresh the page. The system displays a standard warning that we want install typo3 etc., we read it timidly and press the only OK button.

At the first step, we need to specify a username, password and database address. The address often remains the default, i.e. "Localhost".

At the third, last stage of the installation, we are asked to select actions. We leave what is indicated by default i.e. "Create default database tables", which means to create standard tables. We press Import Database and after a while (the system sends a number of SQL queries) we get to the page that offers us to go to the settings, frontend, backend.

Click on Continue to configure TYPO3 to continue configuring the system (we still need to configure the system for utf8 since we want to develop the site in Russian). On the loaded page, press All Configuration and enter the interface for setting system variables. We are interested in and , set the values \u200b\u200bthey need (described in the article on).

After the above, you can log into the backend of the system. To do this, type in the address bar "your domain / typo3 /". To enter we use the standard login "admin" and the password "password".

Upon entering, the system will immediately show you the warnings marked in this version with a red background. In this case, there are three of them:

1. The standard login and password for the install tool is used

2. You need to check the base indexes

3. A standard login and password is used to enter the backend

By clicking on the corresponding links, we go to the backend module in which we can make the necessary changes, i.e. change admin password, change install tool password, re-index the database. Remember to press the save button after each fix. You can return to the backend start page by simply refreshing the page.

After all the threats have been eliminated, we proceed to the Russification of the interface. For Russification, we need to get the corresponding translations, in typo3 they are installed as extensions, so go to the Ext manager module, which means the extension manager.

At the top of the combo box in this module, we select Translation handling. Our attention is drawn to the interface for downloading translations from the typo3 repository. Select your native language from the list and click Save Selection. For a while the system "thinks", then shows 2 buttons "Check status against Repository" - this is in case we are looking for translation updates and "Update from repository" - update from the repository. We press "Update from repository", we see the status bar decorated in a strict style, and when everything turns green, we can proceed to setting the language of the current user. To do this, select the "User Settings" module and, in the form responsible for the settings of the current user, change the Language from English to Russian. We press save, refresh the page and see that most of the interface has become Russian-language.

TYPO3 has been developing since 1998, first as a commercial development, then as an Open Source system. The rapid development of TYPO3 began in 2002, after the creation of the Extension manager, the release of version 3.5.0 and the launch of new versions of the sites www.typo3.com and www.typo3.org. As a result, TYPO3 has become the main tool of several dozen large and medium-sized European web studios (mostly German).

At the end of 2004, the "TYPO3 Association" was established, an official paid membership organization that coordinates and finances the development of the TYPO3 core and core modules, as well as promotion and marketing.

The TYPO3 Association decided in September 2016 to establish TYPO3 GmbH, which provides commercial support for TYPO3 for the corporate sector. For many large companies, vendor technical support (SLA) is a prerequisite when choosing software.

TYPO3 since version 8 LTS uses Doctrine DBAL to work with the database. This provides support not only for MySQL, but also for Oracle, Microsoft SQL Server and PostgreSQL.

TYPO3 8 LTS runs on PHP7, which provides a significant (up to 100%) performance gain in this version.

The system is developing intensively. Every 18 months, a new version of the system is released with a significant development of functionality. Stable LTS (Long Term Support) versions are released with 3 years of support.

Several events are held annually (TYPO3 East Europe, TYPO3 Kongress, TYPO3 User eXperience Week, TYPO3 Developer Days), in which hundreds of developers participate.

Independent developers create hundreds of extensions for TYPO3. Currently, more than 1500 extensions are available for download and automatic installation from

Good afternoon.
I will say right away that I am not a professional freelancer, I just make sites for myself, once just in HTML, then NUKI appears.
A year and a half ago I made a personal project on Joomla + Gallery2 + vbulletin. Now I'm redesigning the site. With a gallery and a forum, I definitely did not feel bad - the most universal. But I will change the heart of the portal. Joomla 1.5 - seems to have improved, but there is no explicit site structure and nested categories. That is, if the site does not imply only the concept of "Section - Categories", then for each article it is necessary to manually add menu items. Therefore, I no longer look at her.
TYPO3 - settled on her. The most versatile of the available, though monstrous, but I take hosting for $ 10, and pay 5 (I got a share). It just works with a bang. The memory limit in the tariff plan is 128, I know how much it costs by default in the settings. Disclaimer - the site starts up and works fine, but there are no visits yet, as it is under development.
I tried to get to know TYPO3 before, when I was making the site, about a year and a half ago. But Then I was completely new to CMS, and I chose what was delivered. Plus, then most of the CMS were at the same level, This is now how many and all high-quality, ajax.
And as there was time, I tried something new, so I tried it.
Monstrous - TYPO3 has been in development for many years, probably ten years. This is of course a minus, a lot of unnecessary, modern CMS with the same functions require less resources. But for the end user, you can turn off everything unnecessary.
In fact, TYPO3 is difficult at first glance, you just need to read a few manuals and test for a week. Then everything is so clear that it is strange to look in the direction of Jomla and Modh. In TYPO3, everything is done more or less visually, it seems to me, especially templates. There is only TypoScript, but it's simple.
There are many extensions, there are a dozen of the most required ones, so they are qualitatively updated and improved.
As for the ready-made assemblies, I would not. There will be a lot of unnecessary things. This is not Joomla, where you installed something, deleted it. Then you will suffer to disassemble other things. Assemblies - to see examples. It's easier to do it yourself from scratch.
Now in parts.
templavoila - make a regular HTML template, so where the modules or content will be displayed, the elements need to be given an ID. You can name it arbitrarily. for instance ... Then, in the system, write a list of names, move the mouse over this and tyts. - there will be displayed something under the name copyright... This is something you describe in TypoSript, or visually insert content: tyts - add text.
TypoScript - in one place you can configure how components and modules will be displayed on the site. This is where you automate everything, for example the formation of the menu. If something will be displayed once, it will be easier to insert visually: tyts - add text.
It's like CSS layout - there is a DIV tag, and in CSS you customize how it looks and where it appears. Only in TypoSript in the role of "DIV" acts - , for example, and in the role of "DIV" attributes in CSS - menu parameters, the list and purpose of which can be found in reference books, everything is simple. Plus, there are many ready-made examples and you can always do something by sticking.
Extensions - everything is collected in one place, in the repository, no need to go to heaps of different sites and forums. Extensions - if these are site components and are displayed on the site, then they can be inserted either manually visually: tyts - add a plugin. and tune it up. Or through TypoSript, where it can be customized and automated for the entire site or its parts.
Added after 1 minute
people help pliz, put russified admin panel, swung the template. I decided to create a page in Russian - everything is fine in the admin panel, on the site itself it is krakozyably. As far as I understand, not the correspondence of encodings. Where and what to fix.
Thanks in advance.
Click to Expand ...

wiki.typo3.biz - everything is described there. Follow it step by step, do not miss.
Added after 21 minutes
Admin panel the most user-friendly. In other systems, everything is scattered in different places: the site tree is on one tab, components on another, and something else is in third place. In Modh, too, it is similar, but somehow intricate.
On the left - modules, that is, what we want to watch and edit. Or - what functions do we need to work with the site now.
In the middle - a tree - choose where (part) of the site we want to do it. Or where to apply these functions of the selected module.
On the right is the actual editing itself.
Everything is logical.