Will this module be ported to Drupal 6.0?
lsiden - August 25, 2008 - 18:44
| Project: | OG Contact |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
From a cursory look at the documentation for Organic Groups as well as the "live demos" page, Organic Groups does not seem to include this feature 6.0. Please correct me if I'm wrong. Therefore, I would like to know whether anyone is planning to migrate this module to D6.0? Thank you.

#1
I do plan on upgrading this module to Drupal 6, though I have not yet started this process for two reasons.
One. There is not yet a stable release of Organic Groups for Drupal 6, and I wanted to wait until there was a stable code base to build on.
Two. I simply have not had the time to do so. When I begin upgrading, I will be going back through contact.module to see if there have been any major changes to how contact works (code wise) in D6, that should be reflected in OG Contact. I also want to check if OG has any new or improved functions that I can use to replace some of the functions I have written into OG Contact.
I am happy to accept any patches or work towards the upgrade.
If you need this module for a site with funding, I can discuss working on the upgrade for a bounty; which would enable me to make the time to work on this.
Either way, this module will make it to D6 eventually.
#2
Thank you for clearing that up. I'll discuss your response with my client.
#3
subscribing...
(This is a great module - keep up the good work.)
#4
subscribing
#5
Subscribing - thanks!
#6
Subscribing
#7
Bump! Easy for me to say, but I'm guessin this isn;t the most complicated module in the world. Anyone else want to take a stab at updating/reinventing OG Contact for D6?
#8
I am happy to work with anyone who feels they have the time to upgrade this. smazsyr is correct, it is not the most complex of modules. The basics of it comes from the Contact module. The complexity in upgrade comes from bringing new code in from the Contact (if there is any relevant new code), and new hooks and functions that might be available in OG itself. There is probably some duplication of functionality between OG and OG Contact, and I would rather be using the OG functions, and remove my own, since there is already a hard dependency there.
I also want to include auto replies for groups, requested here, because I think its an important feature to add to the module; though again it adds a level of complexity to the upgrade (I will also backport this feature to 5.x-3.x).
Given that the US holiday season is coming, I will hopefully have a good chunk of time to dedicate to this, but again, if anyone wants to join in and help me push it forward, I am more than happy to collaborate!
#9
I'm something of a coding ameteur, but I have a real interest in moving this project along, and I'll help in any way I can!
#10
I have started to work on the upgrade though it is far from complete.
Within the next few days I should have something checked in to CVS with a D6 branch. The first round of checked in code will not have any of the new features that are planned for the D6 (and 5) release, but will be a basic refactor of the code, and necessary API changes. It will probably be another week or two before I create a dev release for D6, as some major things need to happen between now and then:
If anyone is up for taking on any part of the to do list, please feel free. Let me know what you are working on, I am happy to help plan and review any code you write. This of course is dependent on me actually getting the D6 code into CVS, and giving you a realistic starting point. The D5 and D6 versions of this module are turning out to be quite differently laid out, so it would make no sense to have anyone work on D6 features with any currently available code.
I'll do my best to keep this issue up to date with the current status, as so many people are looking forward to seeing this module released for 6.
#11
I couldn't be happier! Way to go gnat!
#12
Just to update the thread. I've gotten a lot further in this, but have yet to check anything in to CVS.
The module is mostly working, and I have added the custom intro text. I am actively working on adding contact form recipients by user name, that's been a little held up by some AHAH troubles that I have been having (if anyone is good with AHAH stuff I would appreciate help).
I also haven't even begun to think about the upgrade path yet, but I wanted all of the changes to the database to be settled before I start setting that up.
I'm hoping to push this through this week, but it depends on how long it takes to finish up the adding of users.
#13
Sounds like great progress! Keep going, man. You can do it, and we'll be grateful.
#14
After giving it some thought, and listening to feeedback from the original feature request, I've decided to change the "adding contact form recipients by user name" feature to something more like sending responses to all group members with "receive contact form submission" permissions. I explain more of my reasoning on the original thread.
I need to update the code I'm working on to reflect this change in direction, but it should actually be more simple to implement than what I was going for before. Hopefully much more simple.
#15
Hi. Would it be possible to have this integrate with the notification module since OG is using it moving forward. that way we could take advantage of the various messaging methods like sms.
Chris
#16
subscribing... i need that feature too! :)
#17
The first "-dev" version of OG Contact is now available for D6! Check out the release notes to read about new features and grab a copy.
There is not yet an upgrade path. I'm working on it, but wanted to get this out there so that anyone interested can give it a try.
Enjoy.
#18
Anxiously awaited, gnat, thanks so much!
#19
There is now a basic upgrade path. You will need to upgrade to the "5.x-4.x-dev" version packaged on or after 2009-Mar-12. This will give your database the needed fields for the new features in the D6 version. If you attempt to upgrade without first doing this, you will get limited functionality and errors everywhere. The reason for having to do it this way, is so that I can work on backporting the new features in the D6 branch to the D5 branch, without breaking those user's future hope of upgrade.
NOTE: I have done very limited testing on this so far. Every attempt that I have made has worked, but I am not yet fully endorsing this as working. Give it a try though.
#20
There is a new dev version out today that fixes a few bugs in the previous dev version. It also removes some cruft, and rearranges the settings page.
I have dedicated some time to finally get an official D6 release of this module out.Though a few things remain to be completed first:
Thankfully, I have yet to receive a bug report about people have trouble with the upgrade path. Thus far it has worked when I have tested it. I would at this point consider the upgrade to be safe.