Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When we create a job we can use 'data' to set some data in to it, so what I saw is when initially save data into the database it serialize and save, and since there is no any unserialization to the 'data' it keep serializing when job schedules starts.
So ultimately you will get a big serialize array, so ideal solution would be unserialize and re-write $job object before process.
Patch is attached.
Comment | File | Size | Author |
---|---|---|---|
#2 | job_scheduler-1423422-2.patch | 818 bytes | Dmitriy.trt |
#1 | 1423422-Data-object-keep-serializing.patch | 553 bytes | heshanlk |
Comments
Comment #1
heshanlkComment #2
Dmitriy.trt CreditAttribution: Dmitriy.trt commentedRe-rolled on top of the latest git code at the moment and fixed code formatting (tabs vs spaces).
Comment #3
Dmitriy.trt CreditAttribution: Dmitriy.trt commentedComment #4
checker CreditAttribution: checker commentedThis patch stops growing the serialize array in data for me.
Comment #5
twistor CreditAttribution: twistor commentedhttp://drupalcode.org/project/job_scheduler.git/commit/d6a0d4a
Comment #6
twistor CreditAttribution: twistor commented