Bug #42904
Column assignment get lost on t3d-export/-import
| Status: | Rejected | Start date: | 2012-11-13 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.5 | PHP Version: |
Description
while trying to safe and restore a pagetree with gridelements the column-assignments gets lost. (tested with 4.7.4/4.7.5)
1. there are warnings about recursion
2. on import (update or 'force UID') the elements are forced into main-column outside the grid-element.
so there is no real backup/restore as elements are modified.
I know, export/import is a core-feature, but gridelements enhance/change the usage of the field and the core does not know about the modification to handle it correctly.
Related issues
History
#1 Updated by Jo Hasenau over 2 years ago
- Status changed from New to Rejected
- TYPO3 Version changed from 4.7 to 4.5
Well - the first is a feature the second one a bug, but both are not the business of Grid Elements but of the core.
1. Any kind of relation between records of the same table will show up with the warning you desribed, when using the exporter.
This is just to make you aware of problems that might occur due to a possible recursion.
Grid Elements is preventing these recursion though, so you don't have to worry about that.
2. Is the result of the fact that the importer uses the same TCE-Main methods as the page module.
So any hook connected to TCE will "see" an import as if a real user would be moving records around.
The problem is, that the importer does not inform the TCE-object or any of it's hooks about the fact, that it is just an import and no real user action.
There is a pending issue #36031 and a related patch in the core tracker with a target version of TYPO3 4.5.15, but as far as I can see it has not been merged yet.
So if you want this to be fixed, maybe you can push it in the tracker and/or on Gerrit.