[TYPO3-irre] RTE in child elements overwrites field in parent element
Oliver Hader
oh at inpublica.de
Fri Jul 13 14:54:17 CEST 2007
Hi,
I decided to drop the possibility to create new records while an AJAX
request to the same method is still in progress. This lock is released
when the previous AJAX request has finished (sucessful or with error).
For TYPO3 4.2 I'm planning to rewrite the name scheme of RTE instances.
Currently this is an increasing number. In future this should be an
identifier like '<table>_<uid>_<field>'. Thus, it's destinct and an
instance of RTE belongs to a certain field of a record.
This is also helpful when sub-children are loaded on demand.
olly
Ingmar Schlecht schrieb:
> Hi Olly,
>
> would it be possible to use random indexes instead of just a count?
>
> I mean, what if you just set the RTE index to something like 9283 or
> such random numbers for IRRE elements?
>
> cheers
> Ingmar
>
> Oliver Hader schrieb:
>> Hi Volker,
>>
>> Volker Graubaum schrieb:
>>> Hi Oliver,
>>>
>>> we'd the same problem too, and the patch solved it too.
>>>
>>> BUT I found another thing related to this. :-)
>>>
>>> When the server reponse for the AJAX element takes to long, and a user
>>> clicks more often to create a new one, some RTE's aren't loaded.
>>> (getting the same error as we get after the FF 2.0.3 Update
>>> "Editor is beeing loaded" )
>> You're right. The previous fix for this problem was to tell TCEforms how
>> many instances of the RTEhtmlarea are existing (since TCEforms starts
>> again counting by zero when used on AJAX/IRRE calls).
>>
>> On clicking the "create new record" link more than once - what is okay
>> in general - TCEforms gets the same value for the $RTEcounter variable.
>> Thus, it will again overwrite another RTEhtmlarea instance... (*argh*)
>>
>> A solution could be to process and index the newly RTE after it has been
>> fetched from server via AJAX. Currently the index is set by
>> PHP/TCEforms, in future I could imagine that JavaScript is doing this
>> dynamically (only in IRRE context, not for regular standard
>> tt_content!). But to do this there are some changes necessary in
>> RTEhtmlarea which would be covered by the term "bugfix" and thus could
>> only be fixed in Trunk.
>>
>> Thus, I'm working on a solution for Trunk and possibly my colleagues in
>> the Core-Team will approve this also for the TYPO3_4-1 branch. We will
>> see...
--
Oliver Hader
http://inpublica.de/
More information about the TYPO3-project-irre
mailing list