Version 5

Please try the current HEAD release http://drupal.org/node/96398 and report back if it works. If it works I can make a release, I currently don't have a test setup myself.

When testing og2list 5.x-HEAD, please also test the following 3 patches. All need to be tested and committed before we have a bug-free version of og2list to release:

manage subscription fix: http://drupal.org/node/161393

og/og2list notification fixes:
http://drupal.org/node/165299 (og2list) and
http://drupal.org/node/162307 (og)

thanks in advance for any testing help you can provide. Please let me know if you are stuck on testing any of these and I can hopefully provide some support.

Hi, I've installed the HEAD version of og2list, I'm very keen to see this function.
So, I installed it, I go to a particular OG's homepage, and see the new menu item "unpublished comments" appearing. when clicking this, I get the following error message: "warning: Illegal offset type in .../modules/og2list/og2list.module on line 756." and the colors of my admin interface start to flicker threateningly. bizarre, bizarre, I have no idea what the problem may be (I'm a newbie), but was wondering wether progress has been made on the development of this module.

kind regards,

Joris

Hi,

Is development stalled on this? I'm trying to make a decision about which integrated mailing list solution to go with, and it must be compatible with 5.x.

Thanks,
Jay

subscribe

@squidbe, which others are you looking at? I'm just starting to look for a solution.

The code in CVS works for 5 is you apply a few patches for it. I do also have a private, improved 5.x version to release, I've just been really busy the last couple months at a new job and didn't have the time I'd hoped to work on this.

But I want to get back to it, I know a lot of people are interested in the module and I'd really like to see an actual 1.0 release made because the CVS code does work. Then I can work on getting the stuff from the private one back in, hopefully as a 5.x-2.0 version.

There is one outstanding bugfix that needs to be backported from my private version, so that og2list will not always send the first revision of nodes (if you make a node but don't publish it, then edit it later, then publish it, og2list sends out the first revision not the final one. Oops!)

I will really really try to get going this weekend. Meanwhile, other than that rare case, the HEAD version in CVS will work for you if you have a simple solution, but it's not so hot on the big bad outside internet on a public site.

BUT it is just fine for evaluating og2list if you are thinking about really running it. Later you can upgrade to the post carbon private version if you find you want the extra functionality (MIME email support, proper attachment handling, bouncing spam and unsubbed user mail, stripping of email addresses, multiple domains, support for Cc: to lists and cross posting, configurable footer text and subscription management / group links at the bottom of emails, logging for mail-in.pl mail-out.pl, views and cck rendering, configurable notification types and notifications that work nicely with og, and numerous DB and PHP improvements).
Yes it all SOUNDS cool but none of it is broken up into patches so who knows if it will make it back into CVS.

Anyway first and foremost, we need to get the 5.x port of the CVS code so there is actually a release and to do that we need someone, anyone to download HEAD, install it and test the following patches and comment on the iissues with how the testing went. If things are broke with the patches we need to fiox those, then get them RTBC, then committed by killes or me added as a co-maintaner so I can commit them myself, then we can roll a 5.x-1.0 release! A whole lot of steps I know...

But afterwards I willi be happy to share the enhanced version even if I can't get it back into CVS :)

Anyway please download and install HEAD and test the outstanding patches. I can't mark them RTBC myself, someone else has to test them and agree they work or help fix them. If we can agree these bugs are all fixed and happy now then there is no reason we shouldn't make a 5.x-1.0 release of what's in CVS... but other people have to try it and test it first.

The patches that need testing are:

http://drupal.org/node/148713 <-- this one is REALLY easy to test :) Just a documentation update

http://drupal.org/node/165299 and http://drupal.org/node/161393 which fix problems in the "my subscription" page and og notification. The og patch to match this got committed already and so it's harder to test these. If someone can just verify that it doesn't break the areas that are changed that would even help. They are just sitting there.

http://drupal.org/node/188403 is the node revisions problem I was describing. I will update the patch for this one soon (this weekend hopefully). The patch that's in the issue is totally broken, don't test that one yet.

But those top 3, all should work fine and be reasonably easy to test against a HEAD og2list.

Once I fix the bottom one you would have a bug-free og2list as far as I know if you just apply those 4 patches, and in making our private version I have tested and modified that code for a year in production with a fairly wide user base.

The one thing I haven't tested is the EXIM mail server under Drupal 5. If either of you are using that it would be very helpful to verify that it still works after the 4.7 -> 5 port. (which is where CVS is at, the 5 port + bugfixes but no new functionality).

og2list also still has some problems.... The worst of which is dealing with people lazily replying to list mails without stripping the old forwards and replies before from their e-mail. It all ends up in the post, and it also creates a hellish nightmare for stripping out old subscription links and footer text with our private version. E-Mail clients mangle the HTML differently and then you get combinations of them after it gets forwarded more than once and you end up with these barbarically long drupal posts with 15 forwards and the entire conversation in the bottom of each one. Yahoo groups handles this extremely cleverly by snipping this stuff out... but I think it is probably a very complicated algorithm and doing it right involves a LOT of testing with all the different email clients etc etc etc. Another problem is the complexity of how things go in and out of PHP and the perl scripts. Another is that it takes two crontab runs on your postfix box for mail-out.pl to send mail (it should happen in one). Another is that you can't configure the frequency of digests... you can run mail-out.pl -d (digest mode) at whatever cron frequency you want - hourly, daily, monday mornings, ... but user's can't configure their own schedules. Also, digests are a hellish nightmare when there is 15 forwarded / replied emails in each node body, but finding a way to get rid of old forwarded code etc would fix that. Hmm, what else... I know there are more, I have just mentally blocked them out.

But when you do get it working properly, this module is totally magic.

Of course setting it up is challenging enough, you need a working Postfix installation (preferably one not hosting anyone else's e-mail) and permissions to edit the postfix configuration files and re-create the transport map hash file. It's not for the faint of heart! But I can help if you get stuck.

may the force be with you!

Yes it all SOUNDS cool but none of it is broken up into patches so who knows if it will make it back into CVS.

When I became co-maintainer of og_forum, version 2.0 (or was it 1.5?) was from my personal copy without incremental patches, so I don't see why you couldn't do the same here.

I'll download HEAD and get to the patches in the next few days. I like what you describe and it sounds like what I need.

What is the EXIM mail server? Drupal module? 3rd party software?

Argh, I haven't used Postfix. That's another thing to look into...

I'm very new to Drupal but seem to have it installed and running. However, I can't tell from the back and forth above whether or not I can expect to install on my small, limited use site (fewer than 50 users) running Drupal v. 5 and expect it to run. Would someone be kind enough to recap whether or not it is usable for v5 if you just download the snapshot off of the project home page?

Ok, reading through again I think this will work for me, but I've not had to do patches before. Can someone point me to the right resource so that I can apply the patches? I assume I need to patch my local system in some way and then upload the affected modules to my remote site, yes?

http://drupal.org/search/node/apply+patches

Sorry, I get "access denied" even when I'm logged in on the site where this info is hosted.

Sorry, when you say:

"http://drupal.org/node/165299 and http://drupal.org/node/161393 which fix problems in the "my subscription" page and og notification. The og patch to match this got committed already and so it's harder to test these. If someone can just verify that it doesn't break the areas that are changed that would even help. They are just sitting there."

What do you mean? Do you mean these patches have already been applied to the latest Og2List module, so the patches need not be applied? I ask because I'm getting failures attempting the 165299 patch against the latest og2list.module, so it leads me to believe the patch is out of date.

Hi,
I'm quite a beginner in Drupal, i'd like to use OG2list but i have installed and build the website on Drupal 5. Is there a D5 version of this module availalbe somewhere which wouldn't imply playing with patches and this kind of stuff (because i have no idea how to do that and i'm a bit affraid to break everything ;-) ) Otherwise is there some other similar module for D5 ?
Thanks a lot for the update.