Appreciate the patch, I have applied it but the problem still exists. I"m going live with the site in 48 hours and until we receive a proper patch, I'm having to hide the Birthdate field.

I will create a backup of this site and restore to our development domain if you need to review profile showing the Birthdate field but hoping you have a solid understanding of problem.

Here are 2 screenshots after applying patch, flushing cache on site, flushing browser cache

Edit Profile View

Hi,

strange... at my test site this issue has been fixed. the test site at site info at the first post at this topic is valid?
I need to turn on bithdate field at your site. I cant do it at live site, because you need to turn it off.

Regards

Yes, the info provided for test site is valid. I have applied the patch on this site and Birthdate field is not hidden from users.

For what it's worth, I configured the Birthdate field to be "Only Visible To Admins" on our main domain so you can edit either site but probably preferred to do on test site.

Thank you

Hi,

I did some test under site test. but I cant replicate this issue. not sure why, maybe I missing something?

I have created a BETA test group here in our office for this problem. I asked 10 users to modify Birthdate field and save, then verify it's correct. Several of the users had never filled in that field and when they logged in, they're directed to Edit Profile. They update other fields, forgot to enter something for Birthdate and clicked Save which throws the following error and "broken" page layout

0
DateTime::__construct(): Failed to parse time string (0NaN-NaN-NaN) at position 0 (0): Unexpected character

So it's possible the actual date is fixed, but the code patch has created another issue.

Hi,

Sorry, I cant reproduce that error at your test site.
Birthdate field as a required, so that field cannot be empty.
if saved with empty value. the Birthdate value will Jan 01 1970

Problem is back in version 4.1.2

Hi,

please try to using 4.1.3, if still same, please open new topic for that.

Regards

Hi,

I made a test at your test site, because I cant access your live site because got forbidden message 403.
I cant replicate the issue at your test site. your test site using 4.1.3:

I'm comparing what an admin views in the back-end vs. what that same admin sees on the front-end.
This is on test site running 4.1.3

Hi,

that make me more clear. this why I asked you to open new topic to prevent confusing.
because this topic for frontend issue only.

please wait for the fix. I will let you know if done.

Regards

Hi,

here the fix: