Hey @pedrofsergio ,
Thank you for reaching out. The var_dump entries you’re seeing are not error logs. The not tutor order message is logged when the order being processed is not a Tutor LMS order, and this is part of the plugin’s normal workflow for checking and handling order-related events.
You do not need to remove these entries.
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?
Hey @pedrofsergio ,
Thank you for the additional details. Although this should not normally happen, could you please share the relevant log with us so we can verify the entries from our end?
[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.
Hey @pedrofsergio ,
Thank you for sharing the details and the log entries. We’ll share this with our team for further review and investigation.
Thank you for your cooperation.
