Not sure if I'm in the right place, and I consider myself a smart man, but I am thoroughly confused.
I went looking for the phpBB integration module for Drupal 5.x and I cannot find it? I see the project and appropriate tags in the cvs tree, I can retrieve it from there, but there are no releases on the Drupal project page. Also, it seems that there needs to be some clarification as it seems there is possibly some duplication, why are there two projects that claim to do the same thing:
http://drupal.org/project/phpbb
page edited about one and a half months ago
I believe this is the project I was looking for, but it has no releases, is not listed on the modules pages, and the last cvs commit was 8 months ago.
http://drupal.org/project/phpbbforum
page edited about 2 weeks ago
A new project with no official releases
FYI: I have an old dev version, phpbb 5.x-1.x-dev (2007-Jun-08), on one of my sites that is actually more current than any of the ones found on this page:
http://drupal.org/node/32818/release
What is going on?
Comments
This group is created for
This group is created for that module (see the front page).
Using Drupal's CVS and release system is too Drupal centric, it only lets you tag Drupal versions (and CVS is a pain anyway). You can find the latest version next to the instructions, let me know if you need any of the old stuff (NOT updated for phpBB 2.0.23).
Edit: Wrong front page link
Too Drupal centric?
I can only assume that you are referring the different releases of phpBB, and that they are so different that you need to have a different branch for each combination of drupal version to phpBB version, and the cvs setup does not allow for this.
The problem with having no releases on your project page is that it appears not to exist, there is no issue queue ...etc
If you agree this is a problem:
Solution 1:
It seems that you could have 3 releases, one for each supported drupal version, and that these would only be compatible with a certain version of phpBB. Of course then adding a note that the other versions would be available on your website.
Solution 2:
Allow for the different phpBB versions in your module (overly simplistic: include a different .inc file depending on the version present)
Any comments on the recent addition of the seemingly duplicate module phpbbforum?
I agree it is less than
I agree it is less than ideal, I'd like to do everything in one place, but also keep the discussion etc. on a drupal.org domain. Don't forget the target audience is developers, not regular end users. I expect people to take this code for what it is and have their way with it. If anyone manages to develop it into something user friendly before phpBB provides a proper API, power to them, I'd probably use their version too.
I removed the bug trackers because people kept on repeating the same questions, and for good reason. It's a pain to search tickets that have been closed, or even have a proper discussion. Lots of people posted straight into the forum on drupal.org and I randomly found it months later, when it was of no use to them. I think these groups have worked much better than the issue system ever did.
Solution 1 is too simplified because phpBB and Drupal have actually made big changes to session management in minor versions. So you need one for phpBB 2.0.14 to 2.0.18, one for 2.0.19, one for 2.0.20 - 21... and the same thing on the Drupal side, one for 4.5, one for 4.6 to 4.7. In the end you get a matrix with a lot of holes in it, because you don't want to start supporting .21 in Drupal 4.5
Solution 2 creates a maintenance headache I am not willing to carry (feel free), nor do I think it is wise because these "branches" have in the past been necessitated by security issues. People should upgrade.
uglier than first glance
Ok, so it seems that there isn't a sollution to the different revisions between the two packages, what about the project page on d.o? I assume that the phpBB module won't show on the modules page unless there is a release? This seems like a problem to me. I also think that the duplicated projects is a problem.
Yeah, I agree, it should
Yeah, I agree, it should show up there. Thanks for pointing it out, I hadn't thought about it.
I think most modules of this sort drop the old version when the maintainer moves on, which arguably is what is happening here too. Problem is I will be staying with Drupal 5.x for a while, so 6.x is still a bit off since my todo-stack is much higher that I would like it to be.
Tried convince two clients to support the switch to phpBB 3.x and thereby the upgrade to 6.x, but no go.
Me too
I'll be with 5.x for some time as well, always give the newest release a while for the modules to be updated etc.. that is another reason why I'm still stuck on phpBB 2.0.23. Is there anyway for me to get a copy of the closest version of the module to 5.7 and 2.0.23?
My interest revolves around getting one of my modules(http://drupal.org/project/phpbbPostNode) to work well with yours. I believe that the session handling is a more effective, secure, and quicker way of accessing a phpBB installation as compared to CURL which is what my module uses.
Closest is 5.3 and 2.0.21,
Closest is 5.3 and 2.0.21, junk included and all: http://kepp.net/drupal-5.1/modules/phpbb.tar.gz
I was actually thinking of using cURL for those that want complete integration (including thematic). It's expensive for sure, but for low volume sites it could work. Anyway, it looks like the next ice age will come around before I get to it, so don't worry about that ;)