[TYPO3-core] RFC #8635: MM-relations lost during copying/localizing
Ernesto Baschny [cron IT]
ernst at cron-it.de
Mon Jun 9 09:57:48 CEST 2008
Hi again,
just for your information. The bug was not included in any officially
released TYPO3 version, so you can only test it in:
- current trunk
- current TYPO3_4-2-dev (to be 4.2.1)
- 4.2.1rc1 (http://translation.typo3.org/temp_packages/4.2.1rc1/)
Cheers,
Ernesto
Ernesto Baschny [cron IT] wrote: on 09.06.2008 09:47:
> This is an SVN patch request.
>
> Type: Bugfix
>
> Bugtracker references: http://bugs.typo3.org/view.php?id=8635
>
> Branches: TYPO3_4-2, trunk
>
> Problem:
> Copying (or localizing) records with MM-relations to other database
> tables will not copy over the MM-field contents (the relations).
> Instead you will probably get an error like:
>
> "102: These fields are not properly updated in database: (category)
> Probably value mismatch with fieldtype."
>
> This might happen for example when copying an tt_news record with
> categories. The categories assigned to the element are not copied, which
> is pretty critical.
>
> The bug might affect other areas on copy/localize (e.g. flexforms, like
> someone reported in the -dev list some days ago).
>
>
> Solution:
> The origin of the bug is a patch introduced for fixing the problem with
> shifting datetime on copy:
>
> http://forge.typo3.org/repositories/diff/typo3v4-core?rev=3735
>
> This turned off any transformation/processing on copy/localize, which
> turns out to be wrong, at least for MM-relations (might be the case for
> other transformations as well).
>
> The solution is to first reverse the above listed patch and then have
> the fix applied only to the very specific timezone shifting
> transformation to fix that problem, which is what the attached patch does.
>
>
> Note:
> this is pretty critical for inclusion before 4.2.1 release!
>
> Thanks for Matthias Glatt for reporting this.
>
>
> Cheers,
> Ernesto
>
>
More information about the TYPO3-team-core
mailing list