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

Nested Grid Elements Cannot Be Copied and Pasted Correctly in Version 10.1.0 #2201

Open
rtfirst opened this issue Dec 18, 2024 · 1 comment

Comments

@rtfirst
Copy link

rtfirst commented Dec 18, 2024

I have checked that the bug exists in the dev-development branch
Yes, I get the same error.

I have checked that there are no already open issues or recently closed issues about this bug
Yes

Describe the bug
In version 10.1.0 of the FluidTYPO3 flux extension, it is not possible to correctly copy and paste nested grid elements in the TYPO3 backend. The copied nested grid elements are inserted incorrectly. This issue does not occur in version 10.0.10, where copied entries are correctly inserted during page editing. The content itself is gone.

To Reproduce
Steps to reproduce the behavior:

Go to the TYPO3 backend.
Create a grid element and nest another grid element inside it.
Copy the parent grid element and paste it elsewhere.
Observe that the nested grid elements are incorrectly inserted or not inserted at all.
Expected behavior
The copied parent grid element and its nested child grid elements should be correctly inserted in the page editing view, as is the case in version 10.0.10.

Screenshots
Screenshot 1: Shows the correct behavior in version 10.0.10.
Screenshot 2: Shows the incorrect behavior in version 10.1.0.

Additional context
This issue significantly affects page editing workflows where nested grid elements are used.

Screenshot 1
image

Screenshot 2
image

@rtfirst rtfirst changed the title BUG: foobar fails when baz Nested Grid Elements Cannot Be Copied and Pasted Correctly in Version 10.1.0 Dec 18, 2024
@rtfirst
Copy link
Author

rtfirst commented Dec 20, 2024

@NamelessCoder I'm not sure but maybe this has something to do with the Bugfix #2191

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

No branches or pull requests

1 participant