I realize that, and I have personally and publicly thanked you for your contribution (http://www.dnnsoftware.com/forums/for...) . But, when we play the “volunteer card” as a way to deflect fixing something that should have never been issue in the first place we send the wrong message to new folks looking to adopt the platform. 

@Peter: Its not because it's simply "not there" it's because there are a range of dates in every month, except Feb, where an event cannot be scheduled to recur monthly. And unlike a feature (e.g. like associating multiple location with a event) the user expects to have a "fifth" option. When I explained to the client the lack of a fifth option was an unsupported feature there response (paraphrased)  was: "only a programmer would think that".

@Ernst:

I never said you were.

Neither have I and subsequently never took note of the omission. I have been using the events module for a decade too.

I'm not either, simply want to get the issue addressed, but your "perspective" is clearly it at the core of the issue and perspectives can be flawed. As a comparison... Being able to associate multiple locations with a single event (many-to-one) would be a “feature” since it requires normalization to the 4th to support. Omitting support for a valid domain value is not. It is functionality inconsistent with the intent of the “feature” which is support for monthly recurrence.

I thought you wanted to be called "Peter" because it part of your avatar. I actually go by "Allen", my middle name, so I'm well aware. Sorry I offended you, simply trying to be sensitive about the whole names thing. I guess no good deed (or intent) goes unpunished.