#105005Webhooks Exception if invalid JSON in database field additional_headers
Description
Given the following data in sys_webhook an exception is thrown upon opening the webhooks backend module:
| uid | pid | updatedon | createdon | deleted | disabled | starttime | endtime | description | name | url | method | secret | webhook_type | identifier | verify_ssl | additional_headers | | 4 | 0 | 1707312708 | 1707312708 | 0 | 0 | 0 | 0 | | | | POST | | typo3/redirect-was-hit | 012207ce-c08b-4c67-9455-1e233efbe87d | 1 | Array |
webhooks-exception-invalid-json.png
(1/2) Doctrine\DBAL\Types\Exception\ValueNotConvertible Could not convert database value to "json" as an error was triggered by the unserialization: Syntax error in /var/www/html/TYPO3.CMS/vendor/doctrine/dbal/src/Types/Exception/ValueNotConvertible.php line 42
Reviews 2
Related issues 1
History 413
-
Stefan Bürk commented <span data-processor="relativetime" data-value="2024-09-17T15:50:16+00:00" > 09/17/24, 15:50 </span>
Stefan Bürk wrote in #note-1:
> I would love to know how this value ended up in the database at all.
> Reading should be fixed, but also the writing if we find out how that
> happend.I guess that happend because of Bug #105004
-
Stefan Bürk changed assigned to Stefan Bürk <span data-processor="relativetime" data-value="2024-09-18T07:28:09+00:00" > 09/18/24, 07:28 </span>
-
Stefan Bürk changed Related to #105208 <span data-processor="relativetime" data-value="2024-10-05T21:02:53+00:00" > 10/05/24, 21:02 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 86437 status
NewUnder Review <span data-processor="relativetime" data-value="2024-10-05T21:55:44+00:00" > 10/05/24, 21:55 </span> -
Gerrit Code Review pushed patch set 2 for main to change 86437 <span data-processor="relativetime" data-value="2024-10-05T22:05:42+00:00" > 10/05/24, 22:05 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 86437 <span data-processor="relativetime" data-value="2024-10-07T07:58:59+00:00" > 10/07/24, 07:58 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 86437 <span data-processor="relativetime" data-value="2024-10-10T17:18:50+00:00" > 10/10/24, 17:18 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 86437 <span data-processor="relativetime" data-value="2024-10-10T17:19:27+00:00" > 10/10/24, 17:19 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 86437 <span data-processor="relativetime" data-value="2024-10-18T13:58:51+00:00" > 10/18/24, 13:58 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 86437 <span data-processor="relativetime" data-value="2026-04-22T06:24:56+00:00" > 04/22/26, 06:24 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 86437 <span data-processor="relativetime" data-value="2026-08-15T20:21:24+00:00" > 08/15/26, 20:21 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 86437 <span data-processor="relativetime" data-value="2026-08-15T23:17:57+00:00" > 08/15/26, 23:17 </span>
I would love to know how this value ended up in the database at all.
Reading should be fixed, but also the writing if we find out how that
happend.