Bug #71416
closed
Translate prefix must be not added to bodytext of cType form
Added by Josef Glatz over 8 years ago.
Updated almost 8 years ago.
Description
Problem/Description¶
The „Translate Me“ Prefix is added to configuration property „bodytext“ of the cType mailform of ext:form.
ToDo(s)¶
- When translating a cType mailform, the configuration property „bodytext“ shouldn’t be prefixed.
- Target version changed from 7 LTS to Candidate for patchlevel
at least I can not reproduce that for 8
- Assignee set to Björn Jacob
I will check it out during the sprint in Stuttgart next week.
I performed a test with 7.6.10 and 2 languages and I obtained that, when translating the form, the bodytext (which is "configuration") has been prepended with "[]" e.g.
Original (default) language:
class = cicciform
title = cecciform
enctype = multipart/form-data
method = post
prefix = tx_form
confirmation = 1
postProcessor {
1 = mail
1 {
recipientEmail =
senderEmail =
}
...
Translated:
[]class = cicciform
title = cecciform
enctype = multipart/form-data
method = post
prefix = tx_form
confirmation = 1
postProcessor {
1 = mail
1 {
recipientEmail =
senderEmail =
}
...
Update¶
As I wrote on my issue #68272, the "[]" will be prepended if you type something in the header field; if this is empty, the bodytext will be prepended with "[translate to English]
"
- Status changed from New to In Progress
- Sprint Focus set to On Location Sprint
- Status changed from In Progress to Closed
- Assignee changed from Björn Jacob to Josef Glatz
- Target version deleted (
Candidate for patchlevel)
- Sprint Focus deleted (
On Location Sprint)
We have discussed this during the sprint. Right now, there is no solution for this issue. The disablePrependAtCopy
setting can only be set for the whole table, e.g. tt_content, pages etc. There is no way to set it for a CType or something like this. Therefore we cannot implement a generic solution.
For your installation, Josef, you could get rid of the label in general. Just add it to the specific page or the whole site, see TYPO3 Docs for more information. I hope this is fine with you.
In v8 there will be a new backend wizard which is most likely not affected by this behaviour.
Also available in: Atom
PDF