Can you please comment if you have plans for a drupal 5 version of this module? If yes, do you have a timeframe to implementation for drupal 5?
Thanks.

Comments

jeremy’s picture

Title: Timeframe for drupal 5 version » Get module working with Drupal 5
Category: support » feature

I do not have any near term plans to port this module to Drupal 5 as my website is running Drupal 4.7. The module is not yet feature complete, and I'm not interested in maintaining two branches at this time -- I have limited enough time as is. That said, I would accept quality patches aimed at getting the module working with Drupal 5.

Renaming issue and leaving open for whenever the push is made to get the module working with Drupal 5.

jeremy’s picture

There is now a DRUPAL-5 branch of the module and effort being made to get the module fully working with Drupal 5.x, thanks to Morbus Iff.

bestknight’s picture

Version: » 5.x-1.x-dev

Thanks to both of you for the effort.

jeremy’s picture

Note that the effort to port the module to Drupal 5 is not a priority, and there is no ETA for when it will be ready for testing. Of course, patches to get us toward that goal are always appreciated. Bug reports are not useful at this time.

morbus iff’s picture

Assigned: Unassigned » morbus iff
morbus iff’s picture

Status: Active » Reviewed & tested by the community

Jeremy - DRUPAL-5 is ready to be released. Best bet would be to probably wait for you to do a beta8 release of DRUPAL-4-7, forward port those changes, then release 'em together. Or, alternatively, release DRUPAL-5-beta75 or something (since I've forwarded ported your in-progress changes from DRUPAL-4-7).

jeremy’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for all your work on this, Morbus! I'm now maintaining fixes in both branches, and hope to get the ad_notify work done this week at which time I'll roll an official 5.x beta. Until then, people can test with the latest development snapshot.

Anonymous’s picture

Status: Fixed » Closed (fixed)