Bug #58306
closed
Copy bug with inline records in flexforms
0%
Description
We have noticed bugs when copying elements that have inline records inside of flexforms.
Essentially when copying an element that uses flexforms to store, the copy uses the FAL record count as the file reference ID.
If there are three FAL records in the field it will end up with just one FAL record with and id of 3. It there is one FAL record in the field it will make the copied record linked to a FAL record of id 1.
Here is a video showing clearly showing the problem.
http://www.busynoggin.com/fileadmin/videos/flexform-copy-bug.mp4
Files
Updated by Ron Hall over 10 years ago
- File mcc_patches.zip mcc_patches.zip added
I am attaching an extension built by Jeff Segars that takes care of this bug. However, I believe it uses and XClass and is not intend as a permanent fix. It is just something we are using to get by until the bug is addressed in the core.
Updated by Ron Hall over 10 years ago
I have a TYPO3 Intro package with my flexform content element for testing and a testing page available for download at:
www.busynoggin.com/fileadmin/videos/t3_bugs.zip
The database is in typo3conf. BE user is admin / password.
The patches extension is also there but not installed.
Feel free to use use install to check the issue.
Updated by Tymoteusz Motylewski about 10 years ago
Hi, Thanks for the report and fix.
Can you please check if the patch https://review.typo3.org/#/c/32986/ solves this issue too?
Updated by Riccardo De Contardi about 9 years ago
- Status changed from New to Needs Feedback
- Assignee set to Ron Hall
Hi Ron, I tried to reproduce the bug on 6.2.15 using a flux-based extension, without success.
Can you share the ext you used for the test, or test it against 6.2.15 and 7 (latest master)? Thank you.
Updated by Alexander Opitz almost 9 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Ron Hall)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.