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.Now we have imploded log messages without any space.
So final log message looks like:
Some message1Some message2Some message3
It would be better to explode them with
for example.
Some message1
Some message2
Some meesage3
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | ultimate_cron-separate_log_messages-2919000-5.patch | 448 bytes | codebymikey |
Comments
Comment #2
kalistos CreditAttribution: kalistos at Adyax commentedComment #3
kalistos CreditAttribution: kalistos at Adyax commentedComment #5
codebymikey CreditAttribution: codebymikey at Zodiac Media commentedRerolled in order to test with the latest version of the module.
As well as ensure that the line break is as memory-efficient as possible.
Comment #6
codebymikey CreditAttribution: codebymikey at Zodiac Media commentedComment #7
mortona2k CreditAttribution: mortona2k as a volunteer commentedThis patch is working great for me, I have a cron hook that runs multiple migrations and the log messages appear on their own lines.
The code change is very simple, it adds a line break to the beginning of each message after the first.
Comment #8
BerdirWhy not I suppose ;)