Project

General

Profile

Actions

Bug #14574

closed

Multilanguage bug in copy content element

Added by old_chihoang about 19 years ago. Updated over 17 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2005-02-23
Due date:
% Done:

0%

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

Description

Although plugin or sitemap content element dont use the bodytext field, when copy them with the button "Copy default content elements [x]" to another language, the bodytext field get filled with the useless hint "[Translate to {language}:]". After that the backend shows the bodytext field in the pagecontent view but it cannot be edited nor deleted. Last but not least the search finds the text in this bodytext field. Only solution for me was to delete them manually with phpmyadmin, which is really annoying.

(issue imported from #M838)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #14812: by default when doing translation and coping default content element to new language EMPTY headres are filled w. [Translate to]ClosedMichael Stucki2005-06-11

Actions
Actions #1

Updated by old_henk about 19 years ago

The problem lies in the fact (AFAIK) that if the header information is empty, then the info is filled with the bodytext field from the database. And for the sitemap (and tt_news where I found the problem) the info is not used. You can work around this problem by changing the content from sitemap to text, edit the bodytext, and change it back :) -> not nice but works

more solution/ ideas are posible:
1 always use the header info
-> is this what we want for the rest of typo?
2 make a check if the bodytext field is used/needed and if not show the header info
-> more complicated solution
3 only translate fields which are in use?
-> hmmm. I don't know what to think of this...

Maybe somebody has an idea/solution for this... (maybe something to put on the devlist?)

Regards, Henk

Actions #2

Updated by Mathias Schreiber over 17 years ago

TYPO3 Version too old.
The reported version is no longer maintained.

If this bug still persists in 4.0.1, please re-open it again and set the field "Product Version" to the corresponding version.

Actions

Also available in: Atom PDF