Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUGFIX] Set fieldname in categories relations #11

Merged
merged 4 commits into from
Apr 15, 2014
Merged

Conversation

fsuter
Copy link
Contributor

@fsuter fsuter commented Apr 15, 2014

In TYPO3 6.2, a table may have several categories fields.
It is thus necessary to set values for the "fieldname" field
when filling the "sys_category_record_mm" table.

Francois Suter added 4 commits April 15, 2014 14:28
In TYPO3 6.2, a table may have several categories fields.
It is thus necessary to set values for the "fieldname" field
when filling the "sys_category_record_mm" table.
The task that migrates the DAM category relations makes two critical
mistakes:

* the uid_local and uid_foreign fields are inverted (sys_category
  is local, sys_file is foreign)
* the table with the categories relation is sys_file_metadata
  and not sys_file anymore.
In the backend, FAL references are ordered using the sorting_foreign
field of sys_file_reference and not sorting. As such the migration
task should fill the sorting_foreign field instead of sorting.

Furthermore, the relevant order from tx_dam_mm_ref is also
sorting_foreign instead of sorting.
The MigrateRelations service checks if a given relation has
already been migrated, by querying the sys_file_reference table.
But it doesn't take the fieldname parameter into account
which means that it will ignore relations to the same file
but from a different field in the same table.
bmack added a commit that referenced this pull request Apr 15, 2014
[BUGFIX] Set fieldname in categories relations
@bmack bmack merged commit 36aaa7a into b13:master Apr 15, 2014
@fsuter
Copy link
Contributor Author

fsuter commented Apr 15, 2014

Brilliant, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants