Project

General

Profile

Actions

Bug #90176

closed

create and edit translations (pages/tt_content) outside of the website-roots not possible.

Added by Loon Buster over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2020-01-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

hello.

create and edit translations (pages/tt_content) outside of the website-roots not possible.

/library/
/library/sharedAB/  << multilingualism not possible
/domainA.tld/ (root)
/domainA.tld/helloA/
/domainB.tld/ (root)
/domainB.tld/helloB/

.loon

Actions #1

Updated by Christian Eßl about 4 years ago

Had the same problem after updating a project from 8.7 to 9.5, that had a sysfolder structure with pid=0, that also held translated records .
The solution was to simply create a very limited site config for that sysfolder as well, that just holds the rootPageId and the languages it needs:

rootPageId: 684
base: 'https://www.dummy.com/'
languages:
    -   title: Default
        enabled: true
        languageId: '0'
        base: /
        typo3Language: en
        locale: en-INT
        iso-639-1: en
        navigationTitle: ''
        hreflang: en-INT
        direction: ''
        flag: eu
... more languages
Actions #2

Updated by Christian Eßl about 4 years ago

  • Category set to Link Handling, Site Handling & Routing
Actions #3

Updated by Benni Mack about 4 years ago

  • Status changed from New to Closed

Yes. If you have a storage outside of the site root, one must define the languages for this storage folder (via a custom site configuration), otherwise TYPO3 does not know which languages are available. This is also an issue when having different language setups for multiple sites within one installation, and one main storage that has a different language configuration. This has to be considered carefully be the site administrator.

In general, we recommend, moving the storage folder inside the site root.

Actions #4

Updated by Loon Buster about 4 years ago

makes little sense for a multi-domain instance with shared records.

10 years ago I would have seen this narrow-minded restriction as a great innovation; haha.. no even at that time not .. but hey; what can I expect from a system that uses the unit pixel for responsiveness :D

.loon

Actions

Also available in: Atom PDF