Project

General

Profile

Actions
Copy link

Bug #16587

closed

MM records not written to database

Added by Robert Destigter over 17 years ago. Updated over 16 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Oliver Hader
Category:
-
Target version:
-
Start date:
2007-07-26
Due date:
% Done:

0%

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

Description

For some reasons MM records are not written to the database. I have reproduced this issue with with the tt_news extension, categories field and the related news field.

The uid of the first item in the list is written to the actual record and after saving the record that item shows up in the list. After that I checked the mm table but it was empty.

It looks like TYPO3 is converting the value to an integer. (Wich returns the first uid in the comma seperated list) and also uses that value to diplay as selected instead of checking the MM table.

Could it be a conflict with IRRE?

Reproduced with TYPO3 4.1.1 and 4.1.2
(issue imported from #M6030)

Files

printscreen.jpg (33.3 KB) printscreen.jpg Administrator Admin, 2007-07-26 16:51
Actions
Copy link
 #1

Updated by Robert Destigter over 17 years ago

I found what was causing this problem. The extension "mmforeign" does this. I don't know if it is a conflict between the TYPO3 version and the extension.

Actions
Copy link
 #2

Updated by Robert Destigter over 17 years ago

I also forgot to select a correct category for this topic

Actions
Copy link
 #3

Updated by Oliver Hader over 17 years ago

So, if you remove the extension "mmforeign" the releation is correctly stored to the MM table? The feature "bidirectional MM relations" was integrated into TYPO3 4.1.0 by Ingmar Schlecht. So, in general you do not need this extension anymore.

Actions
Copy link
 #4

Updated by Helmut Hummel over 17 years ago

Perhaps it has nothing to do with mmforeign but with this bug: http://bugs.typo3.org/view.php?id=5103

Actions
Copy link
 #5

Updated by Robert Destigter over 17 years ago

No, it applied to all MM relations in the TYPO3 installation. After removing mmforeign the problem was solved. As you are saying Oliver, I don't need this extension anymore after upgrading to TYPO3 4.1.

Actions
Copy link
 #6

Updated by Oliver Hader over 17 years ago

Since the removal of the EXT mmforeign solved the problem, I'm closing this bug report. "mmforeign" overwrites parts of t3lib_TCEmain of TYPO3 4.0.x installations. If using this extension with old 4.0.x code in an 4.1.x environment this may break some thing concerning data-storage (like here with the MM relations).

Actions
Copy link

Also available in: Atom PDF