Port Birthdays module to Drupal 7

This nice module looks like orphaned/abandoned, there is no maintainer who clear issue queue for last almost 2 years...
drupal 7 port ill be available pobably only if someone of community will do it.

hi guys. It's true that David and I haven't been very active in maintaining this module. I can't speak for David as of why that is (hardly ever spoke to him after taking over his work), but for myself I can say that it had to do with some really bad stuff in my personal life followed by a full-time job.

I intended to pick up my Drupal work by now, but I have to be realistic that this won't happen anytime soon. So anyone is welcome to take over, just say the word and I'll add you to the project as a developer.

I have no specific goals with this module anymore, but there are a few things that would be nice
- D7 support, obviously
- Integration with view/cck/adv_profile (does that still work?)
- Clearing the issue-list

You're track record is fine, so I'll add you as soon as possible.

Edit:
Ok, I have no rights to alter the CVS access rights, that's up to David. Could you contact him and ask him to add you to this project?

I agree, so I sent him a message as well.

nice, will be great if the most requested feature (almost 3 years) -"using cck field instead core profile filed" could be added.

good luck and thanks ahead for your work.
Igor

I would like to help. I already posted a solution for using a CCK field instead of profile. (#173867: Integration with cck (nodeprofile, contentprofile, etc...) in D6 I didn't use the birthday module but i think it could be ported easily. Maybe clean up the issue queue first? I also think it would be a lot better to use a views based solution. This will fix block & panels integration. I never maintained a module but if i get some help i would like try it...

Thanks in advance for everyone's work on this. Work for a non profit for young people in foster care and we use the D5 version of this module. Recognizing and celebrating Birthdays is particularly important for this population. Looking to update our site to D7 at some point and would be very grateful if this module was updated.

This module deserve a D7 version, i can help for translation in french and on css development if u need !

Any updates on the project yet?
Grtz & Thx!

Subscribe.

subscribe

subscribing..

...less vague title + proper tags.

subscribing

This (http://drupal.org/project/birthdays) looks abandoned again. maartenvg, andypost, any progress?

• The last commit was on February 25, 2011 4:07
• Status is "seeking co-maintainers"

I'd like to join. I would work mostly on the Drupal 7 port (or almost rewrite, because of the new field/entity API).

Thank you David for giving me commit access. I'll coordinate with Andy and get the Drupal 7 port/rewrite forward :)

..and the crowd went wild!

:)

Btw: I suppose you wrote that after #20 and before #21 and accedantly changed that tags. But feel free to change it back to "offering to maintain/co-maintain Birthday module", if you want to.

Great news! Finally.

@#23 - We must've posted at the same time? I posted after #20, didn't change tags (intentionally, anyways). Regardless, very happy you are jumping in to help, look forward to testing this for you.

Some random thoughts.

As andypost said:

My plans for D7:
- introduce field for user entity (I have something basic ready and will push it to a development branch once I talked with Andy.)
- make customizable formatter for this field like #812688: Organize image formatters around settings
- prepare upgrade path from D6

- Add Views integration
- Replace page and block with views
- Tokens for the mails

As for the date dependency: I think we should use a custom birthday field type. Date module doesn't support leaving out years and we don't need any of the timezone support, because it's just days we're dealing with.
As for the profile module dependency: I think we shouldn't do that. We can add a field directly to the user entity. However I do think we should add good support or integration for profile2.
You can see what I did so far in the branch 7.x-1.x-niklasf, but everything is up for discussion. We can drop or refactor it at any point.

@andypost: Thank you for your mail. Let me know when you're back.

I'll try to post regular updates on the TODOs for the next time. I'll also try and push often to 7.x-1.x.

• Provide birthday field type
• Support per field instance admin mails
• Add trigger integration. I.e. send user mails on their birthday
• Provide token support
• Move old utility functions to new utility class
• Views integration: Display fields with human readable names
• Views integration: Sort by time to birthday
• Views integration: Filter by birthday in the next N days, note leap years
• Reasonable defaults: Have a birthday view as a page and a block
• Reasonable defaults: Attach a birthday field to the user entity
• Reasonable defaults: Have a "Send congratilations mail" action
• Reasonable defaults: Explain on installation
• More advanced field display: Support starsigns
• More advanced field display: Support displaying the age
• More advanced field display: Support special display for birthday
• Allow user to opt out of triggers (i.e. user email)
• Update hook_help(), README.txt and INSTALL.txt
• Upgrade path

Hi
Are you planning to migrate changes for 6.x version too?
if it will be based on cck field (d7) it can be maybe simply used in drupal 6 + cck, instead basic profile fields...
thanks

@igorik: Not as of now. Maybe I'll backport some of that after a D7 release. However that makes things more complicated regarding upgrade paths and will cost a lot of time.

6.x-1.x    ------- required until 6.x-2.x --------> 7.x-1.x
    \                                              ^
  upgrade to 6.x-2.x                              /
       \                                         /
     6x-2.x ------ new upgrade path needed -----

A linear upgrade path like
6.x-1.x -------> 6.x-2.x ----------> 7.x-1.x
would be better. Unfortunately to do that, 6.x-2.x must be done first.

Of all the TODOs of the Drupal 7 port, I wanted to do the upgrade path last. So maybe maybe we could do 6.x-2.x before that one to keep things linear. But I don't think I have enough time to do that all on my own. andypost might join at some time, or/and someone else.
So probably: If we don't find someone who has time to work on 6.x-2.x it won't happen.

thanks for the info. I understand this.

I moved some time ago from birthday module to cck date field + cck computed field, because I wanted disable profile module (I am using content profile) , it was easy to migrate data from db, however, but I would welcome general solution (sending emails) to people who has the birthday today.

Have a nice day

Thank you :) I am not sure if something like that could be done with CCK Date field + CCK computed field + Rules / Trigger / Action. I've not used Rules often, so I am not sure. Have you tried it? Of course, though, a Birthdays 6.x-2.x that would be specifically made for it will always perform better, have less overhead, be easier to configure, and so on.

Update: Install / uninstall working with default fields and actions during installation. I added a detailed roadmap to the module page. As always, help is welcome on any of the points or new ones.

Great! I think we should close this one then and perhaps file separate issues for each TODO left and any possible bugs we might find along the way. I mean, this issue here was about an initial d7 port after all.

Would it help if I broke down the roadmap to separate issues? This way, patches for each feature added or TODO being done can be applied and tested individually.

@klonos: That would be great. Maybe tag those as "D7 release blocker" or something.

On to it then... I'll just leave the detailed issue summary up to you or anybody else more qualified when I'm not 100% sure of what needs to be done ...since we do have editable issue summaries and all now I mean ;)

...there's a "D7 stable release blocker" tag available already. Using that one.

...and here's the list of the separate issues:

#1277020: Add trigger integration (i.e. send users mails on their birthdays) - D7 release blocker
#1277044: Move old utility functions to the new utility class. - D7 release blocker
#1277046: More advanced field display. - D7 release blocker
#1277048: Update documentation and hook_help(). - D7 release blocker
#1277050: Create an upgrade path from 6.x-1.x - D7 release blocker
#1277052: Views integration. - D7 release blocker

Let me know if they need to be broken down further, because I only filed issues for the main tasks and not for each sub-task in the list. They are simply placeholders and need better descriptions, but I'm not qualified to do that.

I've left these two tasks out:

Create a Drupal 7 development release, with no guaranteed upgrade path to the next release for testing.

We do have a dev. Perhaps just make it available from the downloads section in the project's page is all that's left to be done with regards to that task.

Create a Drupal 7 alpha release. Port is done. What follows are seperate issues, seperate bugs or seperate feature request.

This is part of the process towards the 7.x stable release and I guess we'll release an alpha as soon as we fell it is ready(ish). - btw, those three misspelled instances of "seperate" in the above task need to be "separate" instead ;)

Thank you so much. I loved the list making it easy to copy it over to the module page.

As for the "Release X", you're right: We will know when and what to release or promote when were there, so I removed those.

No problem Niklas. I thank YOU for all your time and effort spent to "revive" this project. I wish I could do more.

Except for documentation and the upgrade path it looks like the basic features are working. I promoted the dev release to the front page. Please test it and file any issues you have, to help getting towards a stable release.

Thanx. This was about an initial port to d7 and since we do have one with basic functionality in place, lets just close this one and file separate issues for problems we come across from now on.

Of course, I just wanted to reach all the people subscribed to this issue ;)

(Again, but this might be my last comment on this issue ...)

I am happy to announce that all release blockers are fixed and a first Drupal 7 version is released. It includes an upgrade path from 6.x. It should be pretty stable, but if you find bugs, have questions or intresting feature ideas, you are welcome to file an issue.