Bug #14797
closed
localized pi_flexform fields show XML source of the original language
0%
Description
Seems as if this is still problem for every FE plugin using flexforms.
After "localizing" the plugin (i.e. news or newloginbox) you will find the
complete XML structure of the original record below the input fields of the
flexform.
Have a look at this screenshot:
http://www.cybercraft.de/fileadmin/screenshots/ff_lang_prob.gif
Checking how the <div class="typo3-TCEforms-originalLanguageValue"> is generated there seems to be no TS value to switch off that behaviour.
There are 3 functions responsible for "default language" in
class.t3lib_tceforms.php":
registerDefaultLanguageData
renderDefaultLanguageContent
renderDefaultLanguageDiff
none of them is configurable via TSconfig and none of them is treating flexform content by parsing the XML. At least one of these possibilities shoud be implemented.
Create a page
Insert a plugin on that page containing flexforms (news, newloginbox or whatever)
translate the page
click on "copy default content elements" or go to the listview and localize the plugin by clicking on a flag
now edit the translated plugin and you will see the whole XML-mess below the input fields.
Is there any reason why original content is shown in translated versions by default? - IMHO this should be an option that is disabled by default but could be enabled when necessary.
(issue imported from #M1169)
Files
Updated by Thomas Hempel almost 19 years ago
I've added a patch (TYPO3 3.8.0) for this.
With this patch it is possible to configure this via User TSConfig for each field in the TCA:
example:
TCEFORM.tt_content.pi_flexform {
disableDefaultLanguage = 1
disableDefaultLanguageDiff = 1
}
If nothing is configured everything is displayed as usual.
If anyone has an idea what would be a better location where to configure this. Please let me know! :-)
The patch is currently a short hack, but it works as aspected for me. I will appreciate any hints and suggestions.
Greets,
Thomas
Updated by JoH almost 19 years ago
This patch just removes the symptom but not the cause.
It seems that the problem is in class.t3lib_befunc.php
It's in function getProcessedValue.
This function makes a simple passthrough for fields of the type flex.
Since it doesn't make any sense to parse the whole flexform as the result of a "processed value" I think it would be good to add another type to the switch in this function that deletes flexform content completely.
Updated by JoH almost 19 years ago
During the bugfixing party Robert Lemke came up with another approach.
We should introduce the boolean parameter "L10n_hideDiff" to the fieldname section to make a decision whether the field value should be shown in localized elements or not.
Updated by Alexander Opitz over 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - TYPO3 Version changed from 3.8.0 to 3.8
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback for over 90 days.
If you think, that this is the wrong decision, then please write to the mailing list typo3.teams.bugs with issue number and an explanation.