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

CommentFileSizeAuthor
#5 ultimate_cron-separate_log_messages-2919000-5.patch448 bytescodebymikey
#2 ultimate_cron-separate_log_messages-2919000-2.patch449 byteskalistos

Comments

kalistos created an issue. See original summary.

kalistos’s picture

kalistos commented
StatusFileSize
new ultimate_cron-separate_log_messages-2919000-2.patch449 bytes
kalistos’s picture

kalistos commented
Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, 2: ultimate_cron-separate_log_messages-2919000-2.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

codebymikey’s picture

codebymikey commented
StatusFileSize
new ultimate_cron-separate_log_messages-2919000-5.patch448 bytes

Rerolled 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.

codebymikey’s picture

codebymikey commented
Status: Needs work » Needs review
mortona2k’s picture

mortona2k commented
Status: Needs review » Reviewed & tested by the community

This 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.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Reviewed & tested by the community » Fixed

Why not I suppose ;)

  • Berdir committed 04da6f84 on 8.x-2.x authored by kalistos 
    Issue #2919000 by kalistos, codebymikey: Seprate log messages with...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.