Haven't fully tested the ramifications yet, but I commented out lines 241-243 from date/date/date_admin.inc and the content type accepted my Month & Day granularity (no year). I wonder if this test is simply to make sure that SOME granularity is selected, it might not necessarily need to be "year". I'll test it and if it continues to work I'll rewrite the lines to test for at least one selection of any level in the $granularity.

If someone more familiar with the Dates Module could look at those lines and let me know if there is something I am missing. Thanks.

@cyberskier, Indefinitely is not a concept computers tend to grasp too well...

First off, you'd just define it as repeating event ending in say, 2015 (even further if you think someone's going to browse your calendar that far, and you know the event actually will likely still be happening in a decade)

2nd - there's a small module - #298334: Repeating dates in separate nodes - that's been started adding the option of generated individual nodes for each of the repeating events, instead of storing the repeating dates in one node. It's still in early development

Thank you very much for the reply, and sorry for the lack of specificity. Poor choice of words on my part to say "indefinitely." My site is a gaming site for a particular PC game, where players from all time zones, most of whom who host a weekly game, list when their regularly hosted games typically take place (such as Tuesdays at 9:00 pm). I have one CCK field that allows the user/player to pick a day or days of the week that the game is normally held on. I'm then looking for another field where they can then enter the time that the game typically takes place. Repeating dates aren't ideal, because while someone might generally have games on Tuesdays at 9 pm as a general practice, they don't know for sure that they'll always be playing each and ever week. All I'm using the date/time fields for is to say "we usually play Tuesdays at 9:00, when we do play." I'm just generating a master list so players who look for games can quickly scan it to find a gaming group that typically meets at a time that is good for them. So it isn't really a schedule per se, but more of a notice. CCK Time, which is still only Drupal 5, worked somewhat, but it really was just a text field, and didn't account for user timezones.

Ah so it's the timezones - otherwise I'd just say - put a textbox for the day, and one for the time! Yeah I was looking at CCK Time for that sort of thing before - I think that's where the answer'd be - #263116: CCK Time for D6 talks about the D6 port - steve.m said he was going to work on it in December but haven't heard since. Seems like it could even be part of the Date module set - really what it needs to do is handle the timezone factor and not worry about dates except the current date for determining things like daylight savings.

@szy: That's not exactly the use case here. I needed to leave off the year because I'm using the date field for a birthday. In may case my users would never fill in the field if the year was on there even if I promised not to display in on the profile. But, without the year the organization can still keep track of everyone's birthday and the users don't have issues with filling in the information.

As an update to my post from Dec 08. I've been using the module with those lines commented out without any dire consequences. It seems to be a safe hack.

"I needed to leave off the year because I'm using the date field for a birthday. In may case my users would never fill in the field if the year was on there even if I promised not to display in on the profile. But, without the year the organization can still keep track of everyone's birthday and the users don't have issues with filling in the information."

I am having the same problem. I would use Birthday but it's not compatible with Advanced Profile Kit, only the standard Profile which I am not using.

Is there anyway I can allow them to leave Year off? Currently fields without year do not get registered by the system.

IMO, a date should NOT be entered without the year. Birthdays DID happen at a specific point in time and on a specific year.
Rather, we need a way to filter dates, ignoring the year (so our filter could say on this day in history, for example).

After looking at the other issue, I don't think this is actually a duplicate. The other thread addresses how views filters parts of the date. This request is for the ability to actually create a "time" field or other date component that is independent of a year. In my case, I would like to use the date module to create times for an office hour multigroup. CCK time isn't released for Drupal 6 and the current work on it has not made it compatible with multigroups. Feel free to say I am wrong and return this to duplicate status.

I see no reason this issue should not be a duplicate of one of the two issues above:

#104287: Time without a date feature
This would allow dates without years. And this sort of exists already with the time duration module. But I think it needs work to integrate with date & calendar module.

"Things like birthdays & anniversaries DID occur on a specific date WITH a specific year."

Not true. A birthdate (or date of birth) is a specific day on a specific year, but people generally refer to birthdays as an annual event celebrating that date. They happen EVERY year, not in ONE year. Same with anniversaries. They occur every year, not in one specific year. The event they celebrate is the only thing that had a specific year.

@23:
Yes, exactly. Birthdays & anniversaries DID happen at a single point in time with a year.
However, those events are recognized or celebrated annually.

IMO, those dates should include year. But, there should be some sort of setting or option to allow certain 'events' like birthdays and anniversaries to be displayed on the calendar regardless of its year. That is what #313498 is all about.

It is possible to create a date field with only month and date. In Drupal 7 you just have to choose "Date entry Options" -> "Custom format" and then type 'm-d' in the "Custom Input Format" field. This way you get the date with no year, with only month and day (see attached image). Problem is that when you submit the form these values are not being added to the node and no date is displayed on the node's view.

1) Create a date field with separate drop-down lists for month, day and year.
2) Set a default date (current)
3) Hide a 'year' drop-down list via CSSdiv.date-year {display:none}
4) Create a custom date format as explained herehttp://www.leveltendesign.com/blog/dustin-currie/format-dates-drupal
Users don't see any year field, although current year value is being entered in the database.
When you set custom date format you can set to display in the node only month and day and ignore the year. For example 'F, j' would display 'October, 13'.

Limitations
Doesn't really use the time zone, although 1900 - 2038 should save the UTC timestamp with the offset added.
Doesn't do date validation 31 Feb allowed atm
Doesn't integrate with the PHP date() formatting options, rather it provides 3 field formatters with theme functions for each formatter.

All components are optional and there are no date limitations.

@date maintainers
I'd love to move some of the logic into the date api. (or let me know if this already exists) This includes month english suffixes, month tables, leap year calculations, and maybe even the extended timestamp calculation (this generates a integer or float for any date from 999999999999BC to 999999999999AD). See the module for this code. Most is based on the Zend_date class with some important performance enhancements like not calculating seconds per year before 0AD and after 3999AD, rather falling back to a constant number seconds per year.