a4slind

Hey David, thanks for the insight. I appreciate you taking the time. I’d have responded sooner, but never got the heads-up there was follow-up on this issue.

That said, I disagree that the premise is incorrect. You presumed I was trying to fix UD. I do agree that it was likely an issue deeper in the system. In fact, knowing where UD is pulling the parameters it passes to wp_mail() would have been valuable in tracking down the potential source of system information.

Water under the bridge though… We had a pretty major hiccup and had to build a new instance to restore to. The issue is not occurring there. I’m assuming there were some data artifacts in the previous stack and closing the ticket.

Bryle,

Thank you for looking into this for me. The latest log (this morning) can be viewed here.

Appears to be remedied sometime before 2.8.29.

Will be looking for an alternative due to lack of response to support inquiry.

Shabti, do you have any thoughts on this yet?

Note the page in question does not currently exhibit the problem behavior. It is production and being held back to the previous version to preserve functionality.

That makes sense.

Thank you again!

Good morning Alan,

The development version you supplied does address, or at least suppress, the error messages filling up the log.

I used it to view several folders/contents in WP, then checked several pages of the website that have a lot of products in their archive. No errors or issues.

I appreciate the quick turnaround on the fix.

Would there be any value to you if I let you know when I get my host to move to a newer version of PHP? I’d be happy to test without the error suppression so you can try to identify the underlying cause.

Regards,
Drew