[TYPO3-templavoila] Cannot delete items from repeatable FCEs

[Jan Loderhose]

Son of a b....

That was it. Thank you very much, Rutger




Am 09.07.2012 15:58, schrieb Rutger Mik | Zeeman Reclamegroep:
> Hi Jan,
> 
> You probably also cannot move items within your FCE's too.
> 
> Try to uninstall the 'advanced frontend editing' extension.
> I had exactly the same problem, and solved it by uninstalling this
> extension.
> 
> This is an known conflict between the 2 extensions, it is already reported.
> 
> If you did not install this extension in the first place, look for other
> jQuery/javascript related extensions and disable them.
> 
> 
> Kind regards,
> 
> Rutger Mik
> 
> 
> Zeeman Reclamegroep
> 
> 
> Op 9-7-2012 11:12, Jan Loderhose schreef:
>> Hi everyone,
>>
>> currently I face the problem that items in repeatable FCEs can not be
>> deleted by neither TYPO3 editors nor admins.
>>
>> The behaviour experienced seems correct in the first place. Open the FCE
>> for editing. Click on the delete icon of the item to be deleted. Confirm
>> the JS dialog that you're sure you want to delete. Save the FCE.
>>
>> Now the behaviour changes to unexpected since after the reload the
>> deleted item shows up again. Amicably under the hood nothing changes.
>> The content of field "tx_templavoila_flex" remains untouched.
>>
>> What I did so far:
>>
>> * Updated TV to the current version 1.7.0. (TYPO3 4.5.17 is already up
>> to date)
>>
>> * Updated mapping information of the respective FCE to remove message
>> "The current mapping information is different from the mapping
>> information in the Template Object" in the TV module.
>>
>> * Opened all gates to the PHP and TYPO3 error logs.
>>
>> * Installed an activated ext devlog.
>>
>> * Checked if any table or fields need to be updated via the install toll
>> -> database analyser.
>>
>> This changed nothing and none of the activated error logs (system/PHP
>> error log, TYPO3 log, TYPO3 BE log, devlog) show any message much less
>> any error related to the described scenario.
>>
>> I do not want to file a bug in the BT before it's not certain that the
>> described scenario is a (new) bug.
>>
>> Has anybody experienced - and maybe solved - this problem before or can
>> relate the problem to an existing bug?
>>
>> Thanks Jan
>>
>