Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I have no idea why this would be happening, although I haven't looked at the code. It seems really strange to me...
With this module installed, the 'date' field created with profile.module for use with birthdays.module has no "blank" option. Normally, i.e. when editing the profile at /user/UID/edit/CATEGORY, users can choose not to specify their birthday. The date field is made up of three drop-down lists (day, month, year) and the first option is usually indicated by two dashes (--); but the option for the two dashes simply isn't there at /profilesetup/CATEGORY.
I suppose it's possible that the problem is actually due to birthdays.module assuming that the birthdays field will only appear on pages with relative URLs /user/UID/edit/... so if that's the case feel free to switch the project this issue is for.
Comments
Comment #1
deverman commentedI have seen this same problem.
Comment #2
thomjjames commentedIt's down to the form_alter hook in the birthday module, as it only alters the form if it's the user_register or user_edit forms.
I can get round this so i'll add support for the birthday module.
Tom
Comment #3
icecreamyou commentedThe commit message for November 27 says:
Now, the "blank" option shows up, but if the user saves the information on the page, the value shows up on the profile as
00/00/. That also produces an error in the log:Line 1234 is in the map_month() function... anyway the error isn't really relevant to the problem, just a result of it. I haven't looked at the code to figure out why this is happening but I would guess that there's no check to test if the user actually put a value in the form element before it gets saved.
Comment #4
thomjjames commentedshould be fixed in 5.x-4.x-dev release