[Bug]: CType t3sbs_button: Cut & Paste across pages causes PHP Warning / 500 error in DataHandler

[Sunusually]

TYPO3-Version

13.4.31

t3sbootstrap-Version

5.3.33

What happened?

Environment

Extension Version	5.3.33
TYPO3 Version	13.4.31
PHP Version	8.2.31

---

Description

When a content element of CType t3sbs_button is cut from a page and pasted onto another page, a 500 Internal Server Error occurs.

The error is triggered during the following AJAX request:

GET https://<host>/typo3/ajax/record/process
    ?token=...
    &CB[paste]=tt_content|2
    &CB[pad]=normal
    &CB[update][colPos]=0
    &CB[update][sys_language_uid]=0
    &CB[update][tx_container_parent]=0

Error Message

PHP Warning: Undefined array key "config" in
.../typo3/sysext/core/Classes/DataHandling/DataHandler.php line 4697

This warning is visible:

• In the browser console (network response) when using the page view
• Directly in the TYPO3 backend UI when using the list view with the clipboard

Steps to Reproduce

1. Create a content element of type t3sbs_button on any page
2. Cut the element (not copy) via the page view or list view
3. Navigate to a different page
4. Paste the element into a column
5. → 500 error occurs, element is not pasted

Expected behavior

Expected Behavior

The element should be moved to the target page without errors, consistent with how Copy & Paste works.

Actual Behavior

A PHP Warning: Undefined array key "config" is thrown in DataHandler.php at line 4697, causing a 500 response for the paste AJAX request.

Additional Notes

• Copy & Paste works correctly — only Cut & Paste is affected
• The issue is specific to t3sbs_button; other CTypes have not been tested systematically

[t3solution]

Could you please test the following for me:
Attached is a file, replace the contents of this file with t3sbootstrap\Backend\EventListener\FlexForm\FlexformEvent.
Clear the cache and run autoload.
Now test it!

FlexformEvent.php

[vmans]

The updated class works. I could cut and copy, but had no paste, and also no drag and drop at all. Now it works. Thank you.

[Sunusually]

Sorry for the late reply, I was out of office.

After replacing the file, I got an error clearing the cache — this affected both frontend and backend, even after restarting PHP:

Invalid service "T3SBS\T3sbootstrap\Backend\EventListener\FlexForm\FlexformEvent": method "__invoke()" does not exist.

The error also persisted after updating TYPO3 to 13.4.32, so it wasn't related to the TYPO3 core version.

Because of this error, I couldn't actually test the fix itself. So I went back to testing the original, unmodified extension across several instances and kept getting the same "move button" bug every time. Today I tested on a different instance (also with the original, unmodified extension) and there it worked without issues. The only difference was the PHP version. After upgrading PHP from 8.2 to 8.3 on the previously affected instances, moving the button worked there as well — again without the file change applied.

So for me the issue was resolved by the PHP upgrade alone, without needing the code fix. I haven't been able to test whether the fix in the file would also work once the "method does not exist" cache error is resolved. I can't really assess why clearing the cache and restarting PHP didn't fix that error in the first place — the PHP version upgrade is what ultimately worked for me.

[t3solution]

... OK, then let's try the next bug fix:

FlexformEvent.php

[Sunusually]

I still get the same Error:
Invalid service "T3SBS\T3sbootstrap\Backend\EventListener\FlexForm\FlexformEvent": method "__invoke()" does not exist.

[t3solution]

... here, a PHP attribute with a method parameter is set. Starting with TYPO3 v13, the __invoke() method is no longer required. The message “method __invoke() does not exist” seems strange to me.
Have you cleared all caches?

[t3solution]

Here's an example using the “__invoke()” method:

FlexformEvent.php

[Sunusually]

Just to sum up where I stand: for me, this issue is resolved by upgrading PHP — I don't need the code fix to consider this closed on my end.

That said, I did try a bit more to help narrow down the remaining method "__invoke()" does not exist cache error, in case it's useful. I uploaded the new file again, cleared all caches, and emptied typo3temp. I also forced a print_r() output to check what's actually being loaded (see screenshot).

I honestly can't explain the error from there — this goes beyond what I can debug. I'm an integrator, not a developer, so I'll have to leave the deeper analysis to you, but only if others run into the same problem.

I feel like I'm not able to contribute much further from this point. Thanks a lot for the effort you've put into this already — really appreciate it!