typo3 setting or dancing with a tambourine

The article is intended for those who love the classic installation with handles (for Composer fans, everything is fine anyway).

Smart people will say that there is nothing complicated and there are a lot of manuals on the World Wide Web, but we will talk about the fact that this does not work or the hands of a person with a higher education and self-taught people with incomplete higher education do not grow from there. Using firstvds as a hosting and kvm virtualization system, as well as os Ubuntu 18.04 (with LAMP pre-installed on board) which was enough for typo3 10.4.26 and php 7.2, a solution was found. Below I present the solution, and the background, of course, after.

Working at the moment

Install the necessary packages No. 1

lsb_release -cd ; hostname ; hostname -I ; whoami ; getconf LONG_BIT ; apt install -y mc build-essential software-properties-common curl gdebi net-tools wget curl sqlite3 dirmngr nano lsb-release apt-transport-https leafpad git sudo unzip socat bash-completion checkinstall imagemagick openssl

Install the required packages #2

apt-get update ; apt install -y php7.2 libapache2-mod-php7.2 php7.2-cli php7.2-fpm php7.2-cgi php7.2-bcmath php7.2-curl php7.2-gd php7.2-intl php7.2-json php7.2-mbstring php7.2-mysql php7.2-opcache php7.2-sqlite3 php7.2-xml php7.2-zip php7.2-snmp php7.2-json php7.2-imap php7.2-common php7.2-tidy php7.2-pgsql php7.2-ldap php7.2-soap php7.2-snmp php7.2-xsl  php7.2-recode php-imagick php-pear php-memcache php-apcu

Next, enable all the necessary mods for apache2:

a2enmod dir env headers mime rewrite setenvif 

We open php.ini with any editor (for me it’s mcedit) the file itself is located here: /etc/php/7.2/apache2/php.ini and we fix 2 parameters in it, namely

  • max_execution_time = 360

  • max_input_vars = 1500

Next, we go to the directory with the web content, download our treasured typo3, extract it from the tarball, for convenience we move it to the typo3 directory, create the first installation file and issue rights to the folder and its subdirectories

cd /var/www/html
wget --content-disposition https://get.typo3.org/10
tar xzf typo3_src-10.4.26.tar.gz
mv typo3*/ typo3/
touch /var/www/html/typo3/FIRST_INSTALL
chown -R www-data:www-data /var/www/html/ ; chmod -R 755 /var/www/html/

Then VirtualHosts for apache2 (we naturally replace everything yourdomain with the domain name of your site):

cat >> /etc/apache2/sites-available/yourdomain.conf

<VirtualHost *:80>

     ServerAdmin admin@yourdomain.com
     DocumentRoot /var/www/html/typo3
     ServerName www.yourdomain.com

     <Directory /var/www/html/typo3/>
          Options FollowSymlinks
          AllowOverride All
          Require all granted

     ErrorLog ${APACHE_LOG_DIR}/yourdomain_error.log
     CustomLog ${APACHE_LOG_DIR}/yourdomain_access.log combined


Well, of course, to apply the whole thing with the help of

a2ensite yourdomain ; a2dissite 000-default.conf  ; apache2ctl configtest ;

If the configtest fails, then somewhere in the site config that we created above was screwed up.

Next, go to the address: yourdomain.com and go through a few steps in the gui to unconditionally install cms on your server, namely, setting up a connection to the database and creating an admin user.

Now the background:

1) How smart people used composer, but alas, this machine crashed during further operation (for those who love composer, you can use it, but not all plugins can be installed using this tool)

2) How not smart people tried to take the path of least resistance and discovered https://docs.typo3.org/m/typo3/tutorial-getting-started/main/en-us/Installation/LegacyInstallation.html then saw a terrible inscription

This method of installation is now considered out of date, users are strongly encouraged to use the Composer based Installing TYPO3

Which in Greek means: This installation method is deprecated and it is recommended to install using Composer.

For help article came.

During the installation in the classical way without including some apache mods, as well as not knowing which packages to install, there were still problems when entering the maintenance tab in the admin panel. Sent to reload backend:

The install tool session expired. Please reload the backend and try again.

They didn’t find any solutions in Google, the invented solutions didn’t help either, but the guide that was outlined above helped and everything was installed without dancing with a tambourine. In addition, a number of other problems arose, but basically their description was found on the resource where all it-experts send =). Good luck to everyone and don’t be STUPID with TYPO3.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *