Bug #59844
closed
Create default language entry fails
Added by Marian Pollzien over 10 years ago. Updated almost 9 years ago.
0%
Description
If I try to create a default language entry for a record from another language, an empty page is shown with the close, save and save and close buttons.
An equal problem occurs if you try to create the default language entry for a content element. There a completly other element is shown and a translation is not possible
Files
| empty_create_record_page.png (11.7 KB) empty_create_record_page.png | Marian Pollzien, 2014-06-24 13:05 | ||
| 2014-10-28 agp-558 content en.png (29.1 KB) 2014-10-28 agp-558 content en.png | Christian Weiske, 2014-10-28 11:45 |
Updated by Alexander Schnitzler over 10 years ago
Hi Marian,
why did you add especially me as a watcher here?
Updated by Markus Klein over 10 years ago
Marian, that means some PHP error which is hidden. Please enable displayErrors in the Install Tool, to reveal the error message. Alternatively there might also be a trace in the error log of the webserver.
I suspect that some extension might cause this.
Updated by Markus Klein over 10 years ago
- Status changed from New to Needs Feedback
Updated by Marian Pollzien over 10 years ago
Alexander Schnitzler wrote:
Hi Marian,
why did you add especially me as a watcher here?
Hi Alexander,
this might be an accidential adding. I don't remember adding you on purpose.
Markus Klein wrote:
Marian, that means some PHP error which is hidden. Please enable displayErrors in the Install Tool, to reveal the error message. Alternatively there might also be a trace in the error log of the webserver.
I suspect that some extension might cause this.
Hi Markus,
to clarify the problem. The first from the description will happen if the entry/record is the only existing. The second will happen if an other entry/record exists.
The config displayErrors is active on our developement system, but no error message is shown.
In the log in the Typo3 backend a warning is logged, but it is not very helpful:
Core: Error handler (BE): PHP Warning: Invalid argument supplied for foreach() in /var/www/server-lokal/aida-offshore/mpo/typo3conf/ext/flux/Classes/Backend/TceMain.php line 158
After deactivating flux and all depending extension, the warning wasn't thrown anymore, but the problem remained.
I have tested it on a clean installation and the problem appeared there too.
Here is a step by step instruction:
empty page
- create a new data folder
- add an alternative language entry
- add an entry/record that does not exists anywhere else in the Typo3 and select the non default language
- create the default language entry
- an empty page is shown
completely other entry/record
- add an alternative language entry, if not existing
- add an entry/record that does exists anywhere else in the Typo3 and select the non default language
- create the default language entry
- an other entry/record is shown
Updated by Markus Klein over 10 years ago
So you are actually creating a new content element for a language and then try to translate it to the default language?
Updated by Markus Klein over 10 years ago
Is defLangBinding activated in page TSconfig?
Updated by Christian Weiske about 10 years ago
No. Enabling it does not change the behavior.
Steps to reproduce:
- Add alternative page language record to a page ("english")
- Create new content element, set the language to english and save (see screenshot).
- Open the language dropdown above the save buttons. You will see "Default [NEW]" and "english".
- Click "Default [NEW]"
- You are editing an existing content element which does not have anything to do with the previous element.
Updated by Markus Klein about 10 years ago
- Status changed from Needs Feedback to Accepted
This is a usecase I never had and also have no time to do a super-debugging session on this problem here.
I suppose the problem is somehow related to the assumption that the "to be translated" page gets a valid translation original id, but that will not work in your scenario.
In your case you actually have to modify two DB rows -> the default language has to be crated and translated content needs the translorig field set.
I guess the bug here is that it is possible to initiate this action at all.
Updated by Helmut Hummel about 10 years ago
Markus Klein wrote:
I guess the bug here is that it is possible to initiate this action at all.
I agree.
This is a "translate" action, which can only be done from records in default language, not to the default language.
Updated by Morton Jonuschat almost 9 years ago
- Status changed from Accepted to Closed
Closing this as the translation handling has been reworked in TYPO3 7 LTS. Creating translations in the order described is no longer possible.