Bug #26583
closed
Page tree in RTE linkchooser doesnt work after reload in flexforms
0%
Description
When the RTE is loaded from a flexform and the link-chooser is used, only the first click in the pagetree is working. After opening/closing a branch it is no longer possible to navigate in the tree or choose a link.
Updated by Christian Jul Jensen about 13 years ago
The problem here is that FlexForms uses ":" in the fieldname, colons are also used in the browse links class as delimiter for parameters passed on. I am submitting a patch with the delimiter changed to semicolon, and it solves the issue I've encountered, but I dont know the code well enough to catch any side-effects.
Updated by Mr. Hudson about 13 years ago
Patch set 1 of change I05dee76e5aaef50ade1d14f6988a46d8e254da1d has been pushed to the review server.
It is available at http://review.typo3.org/2139
Updated by Mr. Hudson almost 13 years ago
Patch set 2 of change I05dee76e5aaef50ade1d14f6988a46d8e254da1d has been pushed to the review server.
It is available at http://review.typo3.org/2139
Updated by Christian Jul Jensen almost 13 years ago
- Assignee set to Christian Jul Jensen
Updated by Oliver Hader almost 13 years ago
Hey Julle,
can you please give an example how the parameters with FlexForms look on your side?
I guess that there are some more places in RTE (e.g. the custom tag handling) and all those modules that maybe combine array elements similar.
Updated by Christian Jul Jensen almost 13 years ago
Oliver Hader wrote:
Hey Julle,
can you please give an example how the parameters with FlexForms look on your side?
I guess that there are some more places in RTE (e.g. the custom tag handling) and all those modules that maybe combine array elements similar.
Not sure exactly what you mean.
But basically the problem arises every where the field-name is used in a set of parameters that are serialized with implode and ':' as delimeter,
Here is the string that gave me issues before and after the fix
|data_tt_content__506__pi_flexform__data__EmailCompany__lDEF__Global____EBMitPrivat____EBPersonalProfile____ReceiptProfile:EmailCompany.PreEmailText__vDEF_::utf-8
|data_tt_content__506__pi_flexform__data__EmailCompany__lDEF__Global____EBMitPrivat____EBPersonalProfile____ReceiptProfile:EmailCompany.PreEmailText__vDEF_;;utf-8
Stanislas actually commented on the patch and mentioned another place this would occur, I don't know if there would be more.
Updated by Stanislas Rolland almost 13 years ago
Christian Jul Jensen wrote:
The problem here is that FlexForms uses ":" in the fieldname, colons are also used in the browse links class as delimiter for parameters passed on. I am submitting a patch with the delimiter changed to semicolon, and it solves the issue I've encountered, but I dont know the code well enough to catch any side-effects.
Please provide the name of an extension that allows to reproduce this issue.
Updated by Christian Jul Jensen almost 13 years ago
- Status changed from New to Rejected
Ok guys I am sorry about this, but the problem turned out to be in the xml used for the flexforms.
There is indeed a clash with the delimiters, but this is caused by the fieldnames used in the flexforms, these are automatically created from an integrated system and ':' is used as a delimiter there.
So it is not a general problem in TYPO3 and so should be fixed in the integration layer between the 2 systems.
- it wouldn't hurt of course to make a more robust serialization in the RTE, but that is another issue ;)
Sorry for wasting your time with this.