Issue Bug Closed

#89541Siteconfig.yaml with not used language-config breaks the server

Christian Hackl 10/30/19, 12:21 updated 07/09/24, 12:00

Description

Siteconfig.yaml with a second language config which is currently not used at the backend – so no translation exists, tries to get the 404 page in the selected language (which does not exists).

For example:
SiteConfig:

languages:
  -
    title: Deutsch
    enabled: true
    languageId: '0'
    base: /
    typo3Language: de
    locale: de_DE.UTF-8
    iso-639-1: de
    navigationTitle: Deutsch
    hreflang: de
    direction: ltr
    fallbackType: strict
    fallbacks: ''
    flag: de
  -
    title: English
    enabled: true
    languageId: '2'
    base: /en/
    typo3Language: default
    locale: en_US.UTF-8
    iso-639-1: en
    navigationTitle: English
    hreflang: en
    direction: ltr
    fallbackType: strict
    fallbacks: ''
    flag: en-us-gb

If the Backend has no translation and no language defined, then you try to get “domain.tld/en”, then TYPO3 tries to get the “domain.tld/en/404” page over and over again – infinite loop (which does not exist).
Until the webserver crashes.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 7

  1. Christian Eßl changed category 03/04/20, 17:18

  2. Georg Ringer commented and changed status New Needs Feedback 03/08/20, 00:32

    hey,

    so also no sys_language exists? then this behaviour is ok as the config.yaml is the single point of truth.

  3. Christian Hackl commented 03/29/20, 19:07

    Georg Ringer wrote:
    > hey,
    >
    > so also no sys_language exists? then this behaviour is ok as the config.yaml is the single point of truth.

    but if no sys_language exists then shouldn’t TYPO3 provide an available 404 page instead of hanging in a loop?

  4. Benni Mack commented 06/03/20, 16:22

    Christian Hackl wrote:
    > Georg Ringer wrote:
    > > hey,
    > >
    > > so also no sys_language exists? then this behaviour is ok as the config.yaml is the single point of truth.
    >
    > but if no sys_language exists then shouldn’t TYPO3 provide an available 404 page instead of hanging in a loop?

    The only way to “overcome” this would be a sanity check in the Sites module or Reports module to show that there are languages configured that are not in the database. At the time of the frontend, there is no database connection (and no check if a sys_language record or a page even exists).

    At the same time, we could catch the “infinite loop” somehow.

  5. Georg Ringer changed status Needs Feedback Accepted 10/20/20, 23:12

  6. Georg Ringer commented and changed status Accepted Resolved 06/06/24, 10:58

    in the meantime there is no sys_language anymore and therefore issue can be closed

  7. Benni Mack changed status Resolved Closed 07/09/24, 12:00