Project

General

Profile

Actions

Bug #17106

closed

Changes of MM relations wont reliably clear the relevant cache

Added by Ralf Hettinger over 17 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2007-03-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.1
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

A problem arises, if MM relations are changed by a TCE-form (handled by class.t3lib_tcemain.php) and the resulting count of relations stays the same (eg change of sorting or removing n relations and adding n relations).

If the count stays the same, the field counting the number of relations (for example a TCA selectbox with MM relations) will not be updated since the values are considered to be the same - and they are indeed, but there might have been a change in the MM table which isn't considered when checking if updatedb should be performed and consequently caches are cleared.

Without more drastic chances in mind, I'd suggest to not perform the so called "similarity" check in class.t3lib_tcemain.php for TCA fields being configured as foreign_table with MM; therefore those fields will always get updated.

This certainly isn't the most efficient way to solve this but at least removes potential erratic behaviour which is quite hard to track down... just changing the sorting within such fields eg won't affect any cache clearing.

Patch against class.t3lib_tcemain.php of 4.1.0RC2

(issue imported from #M5184)


Files

0005184-4.1.0RC2.patch (1.4 KB) 0005184-4.1.0RC2.patch Administrator Admin, 2007-03-10 00:23

Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #21629: MM relations: rollback not working / sys_history wrongClosedSteffen Kamper2009-11-20

Actions
Actions #1

Updated by Ralf Hettinger almost 15 years ago

Fixed with #21629 and can be closed.

Actions #2

Updated by Chris topher over 14 years ago

Solved by #0012688.

Actions #3

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF