Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter pedrofsergio

    (@pedrofsergio)

    [16-Sep-2026 11:30:40 UTC] string(15) "not tutor order"

    [16-Sep-2026 11:31:35 UTC] string(15) "not tutor order"

    [16-Sep-2026 11:31:51 UTC] string(15) "not tutor order"

    [16-Sep-2026 11:32:32 UTC] string(15) "not tutor order"

    [16-Sep-2026 11:50:48 UTC] string(15) "not tutor order"

    [16-Sep-2026 11:52:39 UTC] string(15) "not tutor order"

    [16-Sep-2026 12:27:49 UTC] string(15) "not tutor order"

    [16-Sep-2026 12:40:33 UTC] string(15) "not tutor order"

    [16-Sep-2026 12:42:36 UTC] string(15) "not tutor order"

    Simples this, buts have a lot of on my log file.

    Thread Starter pedrofsergio

    (@pedrofsergio)

    I understand that the logic is correct and it isn’t an error. My point concerns the instruction used: var_dump() is a debugging function that writes to standard output, not a logging method. On my server, it generates 29 lines a day in the PHP error log—the same file I use to diagnose actual infrastructure issues. Furthermore, if that line executes during an AJAX or REST request, the output gets injected before the JSON, potentially corrupting the response. Do you think it could be removed or replaced with a log entry conditional on WP_DEBUG in a future version?

Viewing 2 replies - 1 through 2 (of 2 total)