Feature #83338
closed
Move scheduler tasks from serialized data to JSON
0%
Description
Serializing is not clean at all and can potentially have security-implications. If we just want to store data we should use JSON for that. It would also make accessing/reading/... that data manually or by other scripts easier.
As a migration-path let's create new columns for the json-data then and create a migration-script.
Updated by Stephan Großberndt over 6 years ago
- Subject changed from Move from tasks from serialized data to JSON to Move scheduler tasks from serialized data to JSON
Updated by Susanne Moog almost 6 years ago
- Related to Task #84717: Reconsider serialized array for Linkvalidator added
Updated by Dan Kleine (Untenzu) over 5 years ago
This feature would also solve the issue, that it is not possible to migrate scheduler task with plain SQL commands -> see #55548
Updated by Dan Kleine (Untenzu) over 5 years ago
- Related to Bug #55548: Scheduler: Invalid task uid after Database duplication added
Updated by Georg Ringer about 4 years ago
- Related to Feature #4387: Provide a way to automatically install / set up a task upon installation of an extension added
Updated by Georg Ringer about 4 years ago
- Status changed from New to Closed
I am closing this issue in favor of #4387. json can't be used in that case because the whole class is getting serialized to be waken up again.
This all needs a rewrite of scheduler extension which should be done with version 11. However you can already use https://github.com/helhum/typo3-crontab which works fine in 9