Project

General

Profile

Actions

Bug #69999

closed

Cannot create CE without default language

Added by Robert Dickhaut over 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2015-09-21
Due date:
% Done:

0%

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

Description

Language Mode: Strict
TYPO3 6.2(.14)

Tried:
1. Create a new page
1.1 Create a content element in default language
1.2 Content element is visible in frontend

2. Translate page to second language
2.1 Created a CE in the second language without relation to a CE in the default language
2.2 CE not visible in the second language

3. Clicked "copy default content element"
3.1 CE is visible in the second language
3.2 Disabled the original CE in the default language
3.3 CE from default language and the copy of it in the second language not visible - but only the CE in the default language is disabled.

4. Create a new page
4.1 Translated page to a second language
4.2 Edit page and disabled "Hide default translation of page"
4.3 Create a CE in the second language
4.4 CE in the second language is disabled (bug) - the default language page show a 404 (not a bug)
4.5 Create a CE in the default language (not visible in the FE), translate it to the second language
4.6 Now is the CE in the second language visible - but its to complicated and a bug!

So after all tests, we can say:
You cant create CE without have a original one in the default language.
You must create a CE (can be empty) in the default language, to display CE in the second language.
When the CE in the second language didn't have a original CE in the default language, it will be not showed.

It must be possible to create CE only for a (non default) language.

Maybe related to https://forge.typo3.org/issues/48673


Files

test1.png (46 KB) test1.png Riccardo De Contardi, 2017-02-19 20:03
test2-0.png (37.5 KB) test2-0.png Riccardo De Contardi, 2017-02-19 20:03
test3-0.png (35.6 KB) test3-0.png Riccardo De Contardi, 2017-02-19 20:03
test3-1.png (40.7 KB) test3-1.png Riccardo De Contardi, 2017-02-19 20:03
test3-2.png (51.2 KB) test3-2.png Riccardo De Contardi, 2017-02-19 20:03
test4-1.png (51.1 KB) test4-1.png Riccardo De Contardi, 2017-02-19 20:03
test4-2.png (33.7 KB) test4-2.png Riccardo De Contardi, 2017-02-19 20:03
test4-3.png (38.1 KB) test4-3.png Riccardo De Contardi, 2017-02-19 20:03
test4-5.png (41 KB) test4-5.png Riccardo De Contardi, 2017-02-19 20:03
test4-51.png (52.9 KB) test4-51.png Riccardo De Contardi, 2017-02-19 20:03

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #48673: Changed language overlay behaviour in TYPO3 6.*Closed2013-05-30

Actions

Updated by Riccardo De Contardi about 7 years ago

Hi
I have performed the following test with the latest 8.7 master:

my test configuration:
main language: ITA
language id=1: ENG

TS Setup

config.defaultGetVars.L = 0

config.linkVars = L(0-1)
config.uniqueLinkVars = 1
config.sys_language_overlay = 0
config.sys_language_mode = strict
config.language = it
config.locale_all = it_IT.utf8
config.htmlTag_langKey = it-IT
config.sys_language_uid = 0
config.htmlTag_langKey = it

[globalVar = GP:L=1]
plugin.tx_bhsiteconf.language {

config.language = en
config.locale_all = en_EN.utf8
config.htmlTag_langKey = en-EN
config.sys_language_uid = 1
config.htmlTag_langKey = en
}

Test 1

1) Create a new page: 69999-test_ITA (UID=153)
1.1) create content element (Text) - I type in headline "TEST 1" - see attached file test1.png
1.2)* result of http://mysite/index.php?id?153: the content element TEST 1 is visible in frontend*

Test 2

2) 69999-test_ITA > create translation in ENG (69999-test_ENG) see attached file test2-0.png
2.1) switch to columns view > English > create a new content element (Text) I type in headline "TEST 2-1"
2.2) Result of http://mysite/index.php?id?153&L=1: The Content element TEST 2-1 is visible in frontend

Test 3

3) Switch to languages view > see attached file test3-0.png > click on "translate"
on the popup, click on "copy" > next > next
result: the element TEST 1 has been translated > I enable it - see attached file test3-1.png
result of http://mysite/index.php?id?153&L=1: Both Content elements (TEST 2-1 and [Translate to English:] TEST 1) are visible in frontend
3.2) disable the original content element in default language - see attached file test3-2.png
3.3)
result of http://mysite/index.php?id?153: the content element TEST 1 is not visible in frontend
result of http://mysite/index.php?id?153&L=1: Both Content elements (TEST 2-1 and [Translate to English:] TEST 1) are visible in frontend

Test 4

4) Create a new page: 69999-test_ITA2 (UID=154)
4.1) > create translation in ENG (69999-test_ENG2) - see attached file test4-1.png
4.2) 69999-test_ITA > Edit page > disable "Hide default translation of page" see attached file test4-2.png
4.3 switch to columns view > English > create a new content element (Text) I type in headline "TEST 4-3" see attached file test4-3.png
4.4 CE in the second language is not disabled (see previous screenshot) -
result of http://mysite/index.php?id?154: page not found (correct)
result of http://mysite/index.php?id?154&L=1: the content element TEST 4-3 is visible.
4.5) 69999-test_ITA2 > create a content element (Text) I type in headline "TEST4-5"
Switch to languages view > see attached file test4-5.png > click on "translate"
on the popup, click on "copy" > next > next
result: the element TEST 4-5 has been translated > I enable it - see attached file test4-51.png
4.6) result of http://mysite/index.php?id?154&L=1: both content elements [Translate to English:] TEST4-5 and TEST 4-3 are visible.

I also performed the same tests with 7.6.15 and the results are the same except:

- I used "Text and Media" instead of "Text"
- after point 3) the copied content element is called "TEST 1 (copy 1)" instead of [Translate to English:] TEST 1
- after point 4.5) the copied content element is called "TEST 4-5 (copy 1)" instead of [Translate to English:] TEST 4-5

Result: The issue seems solved for 7.6.x and 8.7 (latest master)

Do you think my test is sufficient or that a different test should be performed? Thank you.

Actions #2

Updated by Riccardo De Contardi about 6 years ago

  • Status changed from New to Closed

I performed the same tests of my previous comment on 9.2.0-dev (latest master) and the results are the same.

I think that it is safe to close this issue for now as resolved.

If you think that this is the wrong decision or that a different test should be performed, please reopen it or open a new issue with a reference to this one; please include also a detailed guide about what tests should be performed. Thank you very much.

Actions

Also available in: Atom PDF