The following points should be updated:

➊ Change „root“ → "root" (lower quotes are not used in English).
➋ Update last sentence to take TYPO3 v9 LTS releases into account (sprint releases are not available anymore).
➌ Change button label to "Go to AWS Marketplace" (add "Marketplace").

https://get.typo3.org/version/9 may feature sqlite as supported DBMS for TYPO3 v9.

The composer statement on the official download page (https://get.typo3.org/version/10) will install a TYPO3 v9 instead of v10.

composer create-project typo3/cms-base-distribution my-new-project

~/typo3-10-or-9$ composer create-project typo3/cms-base-distribution typo3-10-or-9
Installing typo3/cms-base-distribution (v9.5.0)

https://github.com/TYPO3-infrastructure/get.typo3.org/blob/e37039b571e13ee5fb9684f109f9f627f3865b86/templates/default/partials/download-area.html.twig#L46

Using * for Composer versioning is a bad practise, so add a warning there

I would love to see an overview, a matrix what is currently supported, in which state it is in and what are the requirements.

While I really like the layout and design of get.typo3.org (it is very appealing visually), a very terse table (where you have the most important information on one page and don't have to click) might be helpful.

For example,

• You have to click if you want to find the PHP support for ELTS versions
• If you want to find the PHP support of older versions (before ELTS) ...

Examples:

1. TYPO3 release / PHP / MySQL version matrix

Taken from Stack Overflow answer: https://stackoverflow.com/a/12911016/2444812, unfortunately no longer maintained for 8,9 and 10.

BTW, this is the answer with the highest number of upvotes on Stack Overflow, I sometimes look at the highest voted questions or answers to see what people find useful and what may be missing in the documentation.

2. PHP Unsupported branches: https://www.php.net/eol.php

At the end of the release notes TYPO3 6, i.e. https://get.typo3.org/release-notes/6.2.31 the link of Download GPG signed release README.md file lead to an error: https://typo3.azureedge.net/typo3/6.2.31/README.md

At Help&Support => security issues, there is a 404.

Report via OTRS Ticket#20181007609000118

Disabling user zoom is not great for the UX.

We should remove this.

Since 9.5.11 I have my log full of the following error:

Core: Exception handler (CLI): Uncaught TYPO3 Exception: Argument 1 passed to TYPO3\CMS\Frontend\Controller\ErrorController::unavailableAction() must implement interface Psr\Http\Message\ServerRequestInterface, null given, called in /var/www/clients/client1/web1/web/typo3_src-9.5.11-patched/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php on line 2674 | TypeError thrown in file /var/www/clients/client1/web1/web/typo3_src-9.5.11-patched/typo3/sysext/frontend/Classes/Controller/ErrorController.php in line 46

Small wording update: the infoBannerBottom should read:

Do you want to contribute to this website or report feedback?

Instead of:

Want to contribute to this website or report feedback?

Also "GitHub" is a brand name (company name) which should be spelled correctly.

Hi, please prefix all the download links with https://

Example: https://get.typo3.org/version/8

E.g. change

wget --content-disposition get.typo3.org/8
to
wget --content-disposition https://get.typo3.org/8

Please keep in mind that it is not sufficient to 301-redirect the resource to a https-secured url. The server does this already, but it is pretty much pointless in a MITM scenario. Reason: When a MITM comes into play, then the attacker will have control over what is responded to the user's request. The attacker will then just not send the 301 and instead respond with a compromised download. Or the attacker will send a 301 pointing to a compromised download.

301ing itself is not an issue as long as the chain of redirects does not leave https.

Hint: I am aware that users should check ckecksums anyways. It's just that if they do that, that's a different story.

Solution for .well-known/security.txt on new hosting environment

@andristeiner

The 5 links

• Release Notes
• Installation Guide
• Getting started
• Download README (incl. signatures)
• See all releases

aren't working on page https://get.typo3.org/version/9

Introduction sentence in section Changes on release notes shows Markdown syntax that is not converted into a proper link.

This problem occurs on all release note pages.
For example: https://get.typo3.org/release-notes/9.5.9

Executing "composer require typo3/cms-core:^9.5" from the Windows commandline leads to some obscure error messages regarding to version dependencies. I worked around this issue by embedding the version informations in double quotes. AFAIK '^' is treated as special character by the commandline interpreter.

TYPO3 v9 on https://get.typo3.org/version/9#system-requirements has MariaDB 10.2 as minimal compatible version while allowing MySQL to be 5.0 to 5.7
https://github.com/TYPO3-infrastructure/get.typo3.org/blob/master/Build/Data/9.json#L18

TYPO3 v8 LTS on https://get.typo3.org/version/8#system-requirements has no specific MariaDB requirement and allows MySQL to be 5.0 to 5.7
https://github.com/TYPO3-infrastructure/get.typo3.org/blob/master/Build/Data/8.json#L19

TYPO3 v7 LTS on https://get.typo3.org/version/7#system-requirements has no specific MariaDB requirement and allows MySQL to be 5.5 to 5.7
https://github.com/TYPO3-infrastructure/get.typo3.org/blob/master/Build/Data/7.json#L19

In INSTALL.md in all of those versions * MySQL 5.5 up to 5.7 or compatible is stated.

In doctrine/dbal 2.7 there is a specific handling for MariaDB >= 10.2.7 and for MySQL >= 5.7 but nothing disallowing older versions.

1. Why is the required version on get.typo3.org for v8 and v9 lower than in INSTALL.md? Definitions in https://github.com/TYPO3-infrastructure/get.typo3.org/tree/master/Build/Data
2. Why is there a specific requirement for MariaDB 10.2 as minimal compatible version for v9?

https://forge.typo3.org/issues/85428

https://get.typo3.org/9.5.13/tar.gz.sig

e.g. get.typo3.org/9/sig (tar.gz.sig) & get.typo3.org/9/zip/sig (zip.sig)

As of today, a new product is available at the AWS Marketplace: TYPO3 CMS v10.x. The first machine image published is the TYPO3 v10.0 sprint release.

This task is to update the wording on the landing page, to include TYPO3 v10 and to replace the logo with their AWS' new logo.

Reported by Benjamin Amir on Slack:

[sic!] Hi All, im watching at typo3 8.7 requirments on typo3.org and im a bit confused about mariadb version: is it 10.0.26 or 10.1.26 or 10.2.26?

This is on page https://get.typo3.org/version/8

In file README.md, the steps required to install the symfony application miss the command to
create the database schema.

When clicking on the button "get version 8" you are redirected to the page https://get.typo3.org/version/8; it should be nice, in my opinion, to point directly to the section of the page where the dowloads are (i.e. to jump directly to the content of the page - something like https://get.typo3.org/version/8#content) skipping the hero image. I hope I made myself clear
What do you think?

When clicking any of the buttons representing a package, e.g. typo3/cms-about, a JavaScript error is thrown and the JSON result from https://get.typo3.org/ajax/composer/helper/generate is shown in the browser.

The JavaScript error:

Composer Helper Error: 0 - composerHelper.js:107:25

in onreadystatechange() https://get.typo3.org/assets/JavaScript/composerHelper.js:107

https://get.typo3.org/release-notes/4.5.33

I assume that should have been converted to a link.

1. Go to https://get.typo3.org/json
2. Look at the headers: content-type: text/html; charset=UTF-8

Should be: content-type: application/json
Charset is by default UTF-8, so it can be removed, see: http://www.ietf.org/rfc/rfc4627.txt

The package list should also be updated after a version change

Hi,

T3 10.2.2 or 10.3.0, cPanel/centOS install

If I try to edit a template record - or even edit a component of the template like the constants - it begins to load but then the constants and setup textareas disappear and get replaced by unedittable text fields far to the right, offscreen. It's so strange that I can better describe it with a screenshot (attached).

-Scott.

Typo3 v10.3.0 set up has been completed with no errors, but i'm still not able to access Backend admin. I am running xampp v7.2.29. The - http://localhost/typo3_olla/typo3/index.php - file not loading.

burger menu is broken on current mac/chrome.
main-nav fly-out does not appear.

The main menu download link always redirects to latest version instead of latest LTS which is preferable especially for beginners.

As a sysadmin of a TYPO3 installation, I like to get a quick overview about TYPO3 minor releases. I want check, when was the last security release.

Atm i get only the latest version and i get no overview (list view) of all releases of a major version.

Hello,

is there a reason why MariaDB 10.4 is not in the support list?

From the changelog there where "only" System/Performence improvements nothing related to SQL language also no Incompatibilities are listed.

https://mariadb.com/kb/en/mariadb-vs-mysql-compatibility/

Other CMS like Shopware etc.. are listing MariaDB 10.3 or greater ...

Originally posted by @Naled in #50 (comment)

Dear Sir or Madam

In the New zip/gz File with Typo3 Version 9.5.0 is the .htaccess File missinig. Is this normal?

Report via OTRS: Ticket#20181007609000118

The following versions should be changed in MajorVersion:

• TYPO3 7 LTS => TYPO3 7 ELTS
• TYPO3 v6.2 => TYPO3 6 ELTS

Hey,

we just had an editor that is not able to put a link onto an image in IE11.
I can reproduce this - instead of on the image, the link gets prepended to the text.

I think it boils down to ckeditor not fully supporting IE11:
ckeditor/ckeditor5#330

I think it would be good to note that IE11 might have shortcomings in the backend in
https://get.typo3.org/version/8

We need to teach clients to use other browsers anyway... In this case it is a municipality but I am trying to convince their IT that they should supply another browser to their employees.

Hi folks!
Thanks for your awesome work, i like it.
I would like to suggest a little extension, which could be adapted from the legacy download page. There was a quick information about the latest version number and its release date. It is much easier than clicking twice to get to the release notes, to see if there is a newer release.
Regards,
Patrick

Ich räume etwas im wiki auf. Hab eine Frage wegen get.typo3.org:
https://wiki.typo3.org/Category:ReleaseNotes
https://wiki.typo3.org/Category:ReleaseNotes/TYPO3_4.0.x
Die Release notes im Wiki werden redirected auf get.typo3.org. Das funktioniert auch generell gut. Es scheinen aber einige zu fehlen:
https://wiki.typo3.org/TYPO3_4.0.1
https://wiki.typo3.org/TYPO3_4.0.2
https://wiki.typo3.org/TYPO3_4.0.3
https://wiki.typo3.org/TYPO3_4.0.4
https://wiki.typo3.org/TYPO3_4.0.5
https://wiki.typo3.org/TYPO3_4.0.6
https://wiki.typo3.org/TYPO3_4.0.7
https://wiki.typo3.org/TYPO3_4.0.8
https://wiki.typo3.org/TYPO3_4.0.9
https://wiki.typo3.org/TYPO3_4.0.10
https://wiki.typo3.org/TYPO3_4.0.11
https://wiki.typo3.org/TYPO3_4.0.12
https://wiki.typo3.org/TYPO3_4.0.13
... etc.
Release notes f. 4.0.x fehlen in der Übersicht get.typo3.org, s. https://get.typo3.org/release-notes/10 go to another version
Die Texte sind noch im Wiki verfügbar, man kann natürlich nicht direct die Seite anspringen wegen redirect, aber in den Editiermodus gehen, z.B.:
https://wiki.typo3.org/wiki/index.php?title=TYPO3_4.0.1&action=edit
Für die anderen Versionen ebenfalls:
https://wiki.typo3.org/Category:ReleaseNotes/TYPO3_4.1.x
...
teilweise fehlen auch nur einzelne, z.B.
https://get.typo3.org/release-notes/4.2.1: fehlt
https://get.typo3.org/release-notes/4.2.10: verfügbar
...
Gesamtübersicht:
https://wiki.typo3.org/Category:ReleaseNotes

The minimum required MySQL version has been adjusted from version 5.7 to 5.5.

From Sybille Peters:
e.g. https://get.typo3.org/version/9

Missing:

• Information about ImageMagick / GraphicsMagick
• additional PHP package required (https://docs.typo3.org/typo3cms/ContributionWorkflowGuide/Appendix/Linux/SettingUpTypo3ManuallyLinux.html#php-7-2)
• additional modules (e.g. mod_rewrite etc. for Apache, I don't know for other Webservers), see https://docs.typo3.org/typo3cms/ContributionWorkflowGuide/Appendix/Linux/SettingUpTypo3ManuallyLinux.html#apache-webserver
• minimum changes to php.ini: e.g. max_execution_time

I would suggest to also check with the Installation Guide (are there discrepancies?):

• https://docs.typo3.org/typo3cms/InstallationGuide/In-depth/SystemRequirements/Index.html (TYPO3 9)
• https://docs.typo3.org/typo3cms/InstallationGuide/8.7/In-depth/SystemRequirements/ (TYPO3 8)
• https://docs.typo3.org/typo3cms/InstallationGuide/7.6/In-depth/SystemRequirements/ (TYPO3 7)

(or switch versions by clicking on "Related Links on bottom of page)

Should full version requirements be documented in the docs or on get.typo3.org? Should one or the other just contain a stub and refer to the other page? The advantage about maintaining it as docs is, the community can make changes. But get.typo3.org is the official download page, so it really should be there (also core INSTALL.md refers to it).

P.S. the page looks very nice :)

Please also see TYPO3-Documentation/TYPO3CMS-Guide-Installation#48 (and https://forge.typo3.org/issues/84841) for changes to minimum requirements for ImageMagick / GraphicsMagic. I'm merging this one right now.

moved from: https://git-t3o.typo3.org/t3o/get.typo3.org/issues/4

We encountered today some issue with the major release of 10.4.0 which should be optimized the next 18 months:

• template https://github.com/TYPO3/get.typo3.org/blob/develop/templates/default/root.html.twig needs to be adjusted for each major release, this information should be fetched from db
• lts field of MajorVersion needs to be manually set on a lts release
• titles needs to be adjusted manually (LTS and ELTS suffixes), title should be changed to product and version only
• descriptions needs to be adjusted manually, should be generated from the infos in the db

The "TYPO3/Default"-set for TYPO3 v8.7 requires typo3/cms-adminpanel:^8.7 which does not exist. The oldest version of typo3/cms-adminpanel is v9.2

Include scritps to log statistics to Matomo. @andristeiner

The composer helper is really great to get all the necessary packages at one. However, it is not possible to select which version should be used. With the recent sprint releases simple copy and paste installs version 10. To install LTS 9 I have to manually add :^9 behind every package and IMHO this defeats the purpose of having this tool in the first place (One click stop to get all composer requirements).

So my feature request: Please add a dropdown that lets me select the version of TYPO3 to be installed and adjust the composer command according to input. Versions should include LTS and sprints.

Cheers

When selecting a composer packages, users can also choose a specific TYPO3 version. The dropdown box currently offers TYPO3 v8 LTS, v9 LTS and v10.1.

The latter needs to be updated to offer the latest sprint release: TYPO3 10.2.

https://get.typo3.org/misc/composer/helper

The latest 7.6.41 release note: https://get.typo3.org/release-notes/7.6.41

The TYPO3 community supported TYPO3 7 ELTS from 2015-11-10 until 2018-11-27.
Extend your support now until 2021-11-27 to get access to the latest security and compatibility updates for this version.

The first line seems to be the timeframe for LTS, not ELTS. Which is correct, because the TYPO3 community supports LTS and not ELTS but I find this misleading. Maybe it is better to write:

The TYPO3 community supported TYPO3 6 ELTS from 2014-03-25 until 2017-04-04.
Extended long term support (ELTS) is available until 2021-11-27

https://get.typo3.org/json lists the following download URLs, which are broken:

https://get.typo3.org/3.3.0/zip
https://get.typo3.org/3.5.0/zip
https://get.typo3.org/4.5.26rc1/zip
https://get.typo3.org/4.6.0/zip
https://get.typo3.org/4.6.0alpha1/zip
https://get.typo3.org/4.6.0alpha2/zip
https://get.typo3.org/4.6.0alpha3/zip
https://get.typo3.org/4.6.0beta1/zip
https://get.typo3.org/4.6.0beta2/zip
https://get.typo3.org/4.6.0beta3/zip
https://get.typo3.org/4.6.0rc1/zip
https://get.typo3.org/4.6.18/zip
https://get.typo3.org/4.7.0alpha1/zip
https://get.typo3.org/4.7.0alpha2/zip
https://get.typo3.org/4.7.0alpha3/zip
https://get.typo3.org/4.7.0beta1/zip
https://get.typo3.org/4.7.0beta2/zip
https://get.typo3.org/4.7.0beta3/zip
https://get.typo3.org/4.7.0rc1/zip
https://get.typo3.org/4.7.0rc2/zip
https://get.typo3.org/4.7.11rc1/zip
https://get.typo3.org/6.0.0alpha1/zip
https://get.typo3.org/6.0.0alpha2/zip
https://get.typo3.org/6.0.0alpha3/zip
https://get.typo3.org/6.0.0beta1/zip
https://get.typo3.org/6.0.0beta2/zip
https://get.typo3.org/6.0.0rc1/zip
https://get.typo3.org/6.0.0rc2/zip
https://get.typo3.org/6.0.5rc1/zip
https://get.typo3.org/6.1.0alpha1/zip
https://get.typo3.org/6.1.0beta1/zip
https://get.typo3.org/6.1.0beta2/zip
https://get.typo3.org/6.1.0rc1/zip
https://get.typo3.org/6.2.0alpha1/zip
https://get.typo3.org/6.2.0alpha2/zip
https://get.typo3.org/6.2.0alpha3/zip
https://get.typo3.org/6.2.0beta1/zip
https://get.typo3.org/6.2.0beta2/zip
https://get.typo3.org/6.2.0beta3/zip
https://get.typo3.org/6.2.0beta4/zip
https://get.typo3.org/6.2.0beta5/zip
https://get.typo3.org/6.2.0beta6/zip
https://get.typo3.org/6.2.0beta7/zip
https://get.typo3.org/6.2.0rc1/zip
https://get.typo3.org/6.2.0rc2/zip
https://get.typo3.org/6.2.10rc1/zip
https://get.typo3.org/7.6-snapshot-20160223/zip
https://get.typo3.org/8.7-snapshot-20170404/zip

The Download-page of typo3.org contains not all required informations about the download.

https://get.typo3.org/version/9

Using that page, I wont't find informations about the extension typo3/cms-tstemplate, if i use the composer-variation
composer require typo3/minimal

I had a diskussion about that in the german mailing-list.

Dieter

The landing page shows details about the upcoming TYPO3 v10 LTS release. However, the current wording is pretty bad if you address people worldwide.

The upcoming LTS 10 release is scheduled for spring 2020.

April is not "Spring" in all parts if the world. For us (in Australia for example), it's Autumn. Welcome to the Southern Hemisphere.

https://get.typo3.org/release-notes/4.5.33

Link is broken too.

• https://get.typo3.org/v1/api/major/10
  • release_date: "2019-07-23T00:00:00+02:00",
  • actually it's not released yet as LTS
  • seems to be date of v10.0.0
• https://get.typo3.org/v1/api/major/9
  • release_date: "2018-01-30T00:00:00+01:00",
  • seems to be date of v9.1.0
• https://get.typo3.org/v1/api/major/8
  • release_date: "2017-04-04T00:00:00+02:00",
  • correct date of v8.7.0
• https://get.typo3.org/v1/api/major/7
  • release_date: "2015-11-10T00:00:00+01:00",
  • correct date of v7.6.0

I'd suggest to always use the date of the final LTS release - or otherwise refine the models

• first_release_date
• lts_release_date (or just release_date)