Possible date parsing bug in ARMember Zoho CRM Add-On when WordPress date format is mm/dd/YYYY

Hi,

I believe I found a reproducible Date parsing issue in the ARMember Zoho CRM Add-On when the WordPress/ARMember date format is set to the U.S. format m/d/Y.

My WordPress date setting is:

m/d/Y

ARMember also stores the date user-meta values in that format. For example:

09/02/1968
06/19/1976

However, while troubleshooting incorrect date values being sent to Zoho CRM, I found that the Zoho integration code appears to parse the value using:

$date = DateTime::createFromFormat('d/m/Y', $array['Date_of_Birth']);
$format_date = $date->format('Y-m-d');

This interprets an ARMember MM/DD/YYYY value as DD/MM/YYYY.

For example:

ARMember value: 09/02/1968
Intended DOB:   September 2, 1968
Correct ISO:    1968-09-02

Parsed as d/m/Y:
Result sent to Zoho: 1968-02-09

I also found a more serious variation when the actual day is greater than 12. PHP's DateTime::createFromFormat() can normalize the invalid month rather than simply rejecting it.

For example:

ARMember value: 06/19/1976
Intended DOB:   June 19, 1976

Parsed as d/m/Y:
day   = 06
month = 19
year  = 1976

PHP normalizes this to:
1977-07-06

I was able to reproduce these transformed dates against records that had previously been synchronized to Zoho CRM, so this appears to be the source of the incorrect DOBs.

Would you please check whether the Zoho CRM Add-On is hard-coding d/m/Y when converting the ARMember DOB field?

Ideally, I think the add-on should respect the configured ARMember/WordPress date format rather than assuming d/m/Y, and then normalize the DOB to Zoho's Y-m-d format.

Something source-aware would be safer, for example using the configured WordPress date format or otherwise explicitly handling ARMember's supported date formats before sending the value to Zoho.

I can provide additional technical details or test results privately if that would help.

Thank you.