Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
So, I assume that this would - on the Drigg module end - only require a port to the Drupal 6 verison of the Voting API and friends? Then we'd have to put together a new theme, right? Otherwise, it seems like Drigg would be ready to go.
I don't know if the theming system has changed between 5 and 6. I hope not!
Other than that yes, the only real dependencies are the Voting API, Tagadelic (but that's cosmetic) and that's it.
I will have to port Drigg, user_karma and extra_voting_forms. *hopefully* I will be able to get some help.
But as I said, I am focussing on implementing new features right now. When all of the important features are done, I will start thinking about D6.
An external voting button is MUCH more important, I think, than a D6 port.
Obviously. The most improvements in Drupal 6 are OpenID, jQuery, and updates; all of which are provided by modules. The only codebase changes are some optimizations. I imagine that it would be much easier to keep updates going on the Drupal 5 side of Drigg, and then port to Drupal 6 as the main system. You have a good plan.
I personally can't wait to port Drigg to Drupal 6 JUST so that I can stop telling people "You're using the wrong version of JQuery, please follow the instructions"...
Nice! I wasnt aware that you were planning/working on an external vote button. I think this would greatly help in the general adoption of our drigg sites, as well as be extremely helpful with promotion.
We need to split the module first. It's too big at the moment.
This should happen next week.
The budget... well, to be totally honest, I am not sure. It would make a lot more sense if the main Drigg users chipped in, since everybody will benefit.
I would also love a D6 release and am happy to help test it extensively. D6 has such a nicer interface, especially the way menus are treated and some specific modules I think Drigg would be a worthy addition to the D6 module pool. I am happy to help test it on an active site (100 new posts per day) we're seeking to migrate from Pligg to Drigg, the sooner the better.
That's quite reasonable. Please keep us updated on the progress. I'm going to be releasing the third installment of my website in a month and would like to know the status of this project as much as possible.
OK. All I know right now is that extra_voting_form has been ported.
I don't think anything else has yet, but somebody is doing just that full time. So, it's just a matter of time.
The port to Drupal 7 will be a different story. I am gonna branch out NOW, and will apply the changes slowly.
The biggest pain will be porting the themes, for existing sites.
For those subscribed: the porting is happening right now.
The company CMS Website Services, LLC has taken over the task of porting the module. The port is happening this week, and will be released shortly afterwards.
It's harder than expected.
user_karma + extra_voting_forms + drigg all together are about 13000 lines of code (thirteen-hundred).
They finished extra_voting_forms, finished and testing user_karma... and after that, they will start working on Drigg.
Drigg is really, really, really big. It's 25% the size of Drupal (!). So... it takes time. Things will be better once all of the requests happening in Drigg are finally done. If you are able to put some bounty money towards some of them, please do so.
Uplooking, everybody else: CMS Web Services has just finished porting User Karma, a very important module for Drigg and for Drupal in general.
They are now working on Drigg... which is absolutely huge.
Can't wait. subscribed.
In the meantime, would You recommend installing an older version, so I can test and try and learn drigg, since it is a new site, or should I just wait for the new one? Can I upgrade when this comes out?
thanks
thuanvn: right now, help would be *immensely* welcome.
The CMS Web Services guys are going to send me a big fat .tar.gz file.
Would you be able to do some initial testing and check over what they did?
The same applies for User Karma, which is a huge part of Drigg and hasn't been tested yet.
Any help would be most welcome. My brain cells (I don't have that many) have been taken over by FriendList and Activity Log, which are a _crucial_ part of ANY Drigg side, and were basically missing in Drupal (note the PAST tense...).
So much impatience, drigg is the fine wine of Drupal. It matures very well but but cannot be rushed or quality is affected ;)
I imagine Drigg 4 Drupal 6 will be ready whenever it's ready the more merc has to reply here takes one line of code contribution away from the project :p
Hi guys, thanks for developing that module, would like to see a Drupal 6 version of that of course, Any infos on the development need to be done for that or any timeframe.. :)
I'm not involved in drigg development but I said the end of october, so that it gives everyone some date to wait for, and you see if you had waited until the end of october, then you'd have had only a maximum of 5 days wondering when it was finally going to get released since Merc now said at the maximum on 5th november :-)
I am running tests. It seem to work fine! I have already fixed a couple of kinks... I am gonna mark this as "fixed". However, I will definitely need help in terms of testing, because Drigg is huge and it needs people with semi-established sites to do some real testing.
I hope the custom_url_rewriting will be released very soon, do you plan on releasing an express-install Drigg package and updating the download and install page on drigg-code.org soon?
Thank you for the release, that's much appreciated, I hope to be able to test it quickly with a new site I'll create on purpose (I'm not updating my existing Drigg site yet)
The url rewrite is done. Yes, I am planning on releasing a drigg_distr -- in fact, I am planning on concentrating all the development on D6, since D5 is now nearly a year old.
This is great news! I'm going to test it with a template recently built for 5.x, but that has not been launched and will report back.
It will be nice to have the custom_url_rewrite mod before everything else, because that will cause less problems with indexing and Search Engine rankings.
I mean tag the CVS branch something like DRUPAL_6--1-alpha1 and then add a new release to go with it.
The main reason why I prefer this is the development snapshot can change frequently, I think they repackage the dev packages every 12 hours with latest cvs updates. an official release, even if it is just an alpha release, will always be there if we want to view all releases.
Last month I was talking with another Drupaler about a module and he told me he had it on a production site in D6, well, I went to the project page and the only release for D6 was the dev snapshot, which didn't work. Because the dev snapshot is replaced every 12 hours when there are changes I couldn't just look at the history and find previous releases.
No stable version exists just yet -- I am waiting for people to confirm that it's 1000% OK. I am also gonna split Drigg into different smaller files, since D6 allows that to save memory.
You mentioned earlier that you are "also gonna split Drigg into different smaller files."
I am in the process of theming Drigg for a new website (base on the default theme for D6). Is there any chance that this might break or affect the theme in some way?
In other words, is it wise to start theming for D6 at this point or would it be better to wait for a while?
Psycs: No, it should be totally fine to do theming now. The "splitting up" is something that D6 allows, but it won't affect any of the "normal" things going on with Drigg.
Just want to point out that we should all thank copiously the GOOD guys at CMS Web Services Inc. who basically did the port. There will be proper thanks in the project's home page. They were fantastic!
ihead, I have had unexpected events lately that have reduced the number of hours I spend on Drigg. It's temporary, but it might go on for 2 more weeks.
Ihead, is there any way for you to become the official maintainer of the "express drigg"?
Why joking, this was a great module, shame nobody picks it up....I am not a good enough programmer, but would love this functionality...
greetings, Martijn
Comments
Comment #1
mercmobily commentedHi,
Absolutely.
However, I will wait till Drupal 6 is actually *finished*!
(I know we are close).
I will leave this bug open till the port is done. Drigg is actually huge, and any help with porting it will be _most_ welcome!
Bye,
Merc.
Comment #2
vm commentedwith the rise of cristical issues for D6 back up to 18, there is still a ways to go yet : )
Comment #3
mercmobily commentedHi,
I know...! I am sure the list will shorten soon :-D
Bye,
Merc.
Comment #4
mercmobily commentedHi,
Drupal 6 is out.
I will port Drigg to D6 only when there are no outstanding Feature requests.
I think it will take approximately 3 months. At that point, we will probably have D6.1 which will be a bonus.
I hope the migration to 6 will be easy...
Merc.
Comment #5
zwaldowski commentedSo, I assume that this would - on the Drigg module end - only require a port to the Drupal 6 verison of the Voting API and friends? Then we'd have to put together a new theme, right? Otherwise, it seems like Drigg would be ready to go.
Comment #6
mercmobily commentedHi,
I don't know if the theming system has changed between 5 and 6. I hope not!
Other than that yes, the only real dependencies are the Voting API, Tagadelic (but that's cosmetic) and that's it.
I will have to port Drigg, user_karma and extra_voting_forms. *hopefully* I will be able to get some help.
But as I said, I am focussing on implementing new features right now. When all of the important features are done, I will start thinking about D6.
An external voting button is MUCH more important, I think, than a D6 port.
Merc.
Comment #7
zwaldowski commentedObviously. The most improvements in Drupal 6 are OpenID, jQuery, and updates; all of which are provided by modules. The only codebase changes are some optimizations. I imagine that it would be much easier to keep updates going on the Drupal 5 side of Drigg, and then port to Drupal 6 as the main system. You have a good plan.
Comment #8
mercmobily commentedHi,
I personally can't wait to port Drigg to Drupal 6 JUST so that I can stop telling people "You're using the wrong version of JQuery, please follow the instructions"...
:(
Merc.
Comment #9
silvanov commentedNice! I wasnt aware that you were planning/working on an external vote button. I think this would greatly help in the general adoption of our drigg sites, as well as be extremely helpful with promotion.
Comment #10
BostonDave commentedCan't wait until you get it over to 6 - I wish I could help but my skills are bit lacking...
Comment #11
mercmobily commentedHi,
BostonDave: please don't hold your breath.
If you have the means to sponsor the porting, please let us know.
(It might not be me doing it!)
Merc.
Comment #12
dorien commentedAny direction you can give us regarding required budget?
Comment #13
mercmobily commentedHi,
We need to split the module first. It's too big at the moment.
This should happen next week.
The budget... well, to be totally honest, I am not sure. It would make a lot more sense if the main Drigg users chipped in, since everybody will benefit.
What were you thinking about?
Merc.
Comment #14
philbar commentedHow's the port coming? The last update to this issue was in April.
Comment #15
mercmobily commentedHi,
Sicjoy...?
Merc.
Comment #16
zhte commentedI would also love a D6 release and am happy to help test it extensively. D6 has such a nicer interface, especially the way menus are treated and some specific modules I think Drigg would be a worthy addition to the D6 module pool. I am happy to help test it on an active site (100 new posts per day) we're seeking to migrate from Pligg to Drigg, the sooner the better.
Comment #17
philbar commentedAny update?
Comment #18
mercmobily commentedHi
I have an offer from a company that has a couple of paying customers who want the Drupal upgrade. They told me they would start sometime this week.
Bye,
Merc.
Comment #19
gausarts commentedHi Tony, I'll keep my fingers cross. Newton III law will take effect on your highest good. Thanks for all the great work.
Comment #20
mercmobily commentedHi,
The offer went through. Drigg is about to enter code freeze and will be ported to D6.
Yuppy!
Merc.
Comment #21
philbar commentedGreat! Is there any time frame determined for the port yet?
Comment #22
mercmobily commentedHi,
"as long as it needs".
I guess 2 weeks.
It's thirteen THOUSAND lines of code. So...
Merc.
Comment #23
spiffyd commentedSubscribed!
Comment #24
philbar commentedThat's quite reasonable. Please keep us updated on the progress. I'm going to be releasing the third installment of my website in a month and would like to know the status of this project as much as possible.
Comment #25
mercmobily commentedHi,
OK. All I know right now is that extra_voting_form has been ported.
I don't think anything else has yet, but somebody is doing just that full time. So, it's just a matter of time.
The port to Drupal 7 will be a different story. I am gonna branch out NOW, and will apply the changes slowly.
The biggest pain will be porting the themes, for existing sites.
Bye,
Merc.
Comment #26
mercmobily commentedHi,
For those subscribed: the porting is happening right now.
The company CMS Website Services, LLC has taken over the task of porting the module. The port is happening this week, and will be released shortly afterwards.
Bye,
Merc.
Comment #27
sikjoy commentedHi Merc:
Shall I create the DRUPAL-6--1 branch now?
--sicjoy
Comment #28
mercmobily commentedHi,
Not just yet. They will send us a .tgz with everything in it -- it might make more sense to create the branch with those files already.
Bye!
Merc.
Comment #29
philbar commentedStatus update?
Comment #30
mercmobily commentedHi,
It's harder than expected.
user_karma + extra_voting_forms + drigg all together are about 13000 lines of code (thirteen-hundred).
They finished extra_voting_forms, finished and testing user_karma... and after that, they will start working on Drigg.
Drigg is really, really, really big. It's 25% the size of Drupal (!). So... it takes time. Things will be better once all of the requests happening in Drigg are finally done. If you are able to put some bounty money towards some of them, please do so.
Bye,
Merc.
Comment #31
PGiro commentedtracking
Comment #32
mercmobily commentedHi,
Uplooking, everybody else: CMS Web Services has just finished porting User Karma, a very important module for Drigg and for Drupal in general.
They are now working on Drigg... which is absolutely huge.
Will keep you posted,
Merc.
Comment #33
virtualdrupal commentedtracking..
You guys rock.
Comment #34
mercmobily commentedHi,
Right now I am only rocking under the weight of 13000 lines of code that need to be tested and ported and tested and ported and...
:-D
Merc.
Comment #35
gausarts commentedJust hang on something, Tony:)
Can't wait to see this mammoth module rock drupal 6 world myself. Thanks
Comment #36
alliax commentedsubscribing to this issue so that I can follow.
cafetiere expresso
Comment #37
mracarpenter commentedSubscribed! Can't wait!
Comment #38
pvtsales commentedSubscribed... Drupal 6 has lots of features!!
Comment #39
kec commentedCan't wait. subscribed.
In the meantime, would You recommend installing an older version, so I can test and try and learn drigg, since it is a new site, or should I just wait for the new one? Can I upgrade when this comes out?
thanks
Comment #40
mercmobily commentedHi,
Upgrading should be relatively painless... The 6 port is happening as we speak, but it might take 2 or 3 more weeks.
Merc.
Comment #41
jdclarke commentedSubscribing
Comment #42
thuanvn commentedI want to join this to get a chance if I could help you smt in Drigg 6 porting.
Comment #43
mercmobily commentedHI,
thuanvn: right now, help would be *immensely* welcome.
The CMS Web Services guys are going to send me a big fat .tar.gz file.
Would you be able to do some initial testing and check over what they did?
The same applies for User Karma, which is a huge part of Drigg and hasn't been tested yet.
Any help would be most welcome. My brain cells (I don't have that many) have been taken over by FriendList and Activity Log, which are a _crucial_ part of ANY Drigg side, and were basically missing in Drupal (note the PAST tense...).
Thanks a lot,
Merc.
Comment #44
thuanvn commentedOkay Merc, send me the file.
to vungocthuan@gmail.com please
Comment #45
chassler commentedHappy october,
What's it lookin' like merc?
Chad
Comment #46
mercmobily commentedHi,
We had a few problems with the Drupal 6 routing, which has a big that affected Drigg (ugh!).
We *seem* to be managing OK though. It should be out soon.
It _was_ 12000 lines... it's a lot of work.
Merc.
Comment #47
thompson commentedhi,
i would like to have the d6 version too.
thanks for developing that mod.
i there a timehorizont for d6 ?
Comment #48
mercmobily commentedHi,
"when it's ready"
Merc.
Comment #49
alliax commentedI would say definitively before the end of october :-)
Comment #50
stuartduff commentedSo much impatience, drigg is the fine wine of Drupal. It matures very well but but cannot be rushed or quality is affected ;)
I imagine Drigg 4 Drupal 6 will be ready whenever it's ready the more merc has to reply here takes one line of code contribution away from the project :p
Patience is a virtue.
Comment #51
samuel lavoie commentedHi guys, thanks for developing that module, would like to see a Drupal 6 version of that of course, Any infos on the development need to be done for that or any timeframe.. :)
Comment #52
Testering commentedYeah, I can't wait for Drigg 6 to come out. My feeling is that there is going to be a boom of sites once it comes out.
Merc, you rule! Keep on the good work...
Comment #53
playfulwolf commentedyou are more than right...
Comment #54
philbar commentedCan we have a status update?
Alliax wrote earlier that it will be ready "definitively before the end of october". That time is fast approaching.
Thanks.
Comment #55
mercmobily commentedHi,
I should have a working version of Drigg V6 by the 5th of November.
Merc.
Comment #56
alliax commentedI'm not involved in drigg development but I said the end of october, so that it gives everyone some date to wait for, and you see if you had waited until the end of october, then you'd have had only a maximum of 5 days wondering when it was finally going to get released since Merc now said at the maximum on 5th november :-)
Comment #57
pushkar commented@mercmobily
Thanks. Will donations help - may be a week's worth of coffee :)
Comment #58
mercmobily commentedHi,
Donations are always welcome. However, porting Drigg -- for a number of reasons -- is a lot of hard work... sorry about the delay.
merc.
Comment #59
PGiro commentedJust wondering if you will be moving feed aggregation to FeedAPI or staying with the old "News Aggregator" ?
Comment #60
mercmobily commentedHi,
Old "news aggregation" for now.
I am only piggy backing on it in order to get RSS entries.
Merc.
Comment #61
j2m commentedHi
we are now the 5th of november.
where do we get from all these expectations?
any news?
thanks in advance. I can't wait.
J2M
Comment #62
pushkar commented@Mercmoblility
Do let me know - do you have a paypal A/C ?
Comment #63
alliax commentedDon't blame merc, he said 5th november but never said of which year, so hopefully it shall be 2009 :-)
Comment #64
iahead commented@ PUSHKAR
pay@freesoftwaremagazine.com this is the paypal id
yeah even i am waiting for D6 desperately
Comment #65
George2 commentedlooking down this thread, i think to myself what a lot of ungreatful people, almost demanding to know where the release is.
rather than asking where it is, either help out coding, donate, or look for the release on the module page.
Comment #66
iahead commented@George2 we are not demanding the release but we are curious about it .we have helped drigg in all possible ways.
So mind what you are talking about
Comment #67
mercmobily commentedHi,
guys, chill. Drigg D6 is here :-D
NOW PLEASE TEST IT!!!
(uploading it to CVS as we speak)
Merc.
Comment #68
mercmobily commentedHi,
Note: the custom_url_rewrite function is not there yet... so, the pretty aliasing won't happen just yet.
Merc,
Comment #69
mercmobily commentedHi,
I am running tests. It seem to work fine! I have already fixed a couple of kinks... I am gonna mark this as "fixed". However, I will definitely need help in terms of testing, because Drigg is huge and it needs people with semi-established sites to do some real testing.
So, let's do it!
merc.
Comment #70
PGiro commentedChhhaaaaaaarrrrrrggggggggeeeeee :)
Will install and report back
Comment #71
mercmobily commentedHi,
:-D
Merc.
Comment #72
alliax commentedI hope the custom_url_rewriting will be released very soon, do you plan on releasing an express-install Drigg package and updating the download and install page on drigg-code.org soon?
Digg the early news about Drigg for Drupal 6 here!
Thank you for the release, that's much appreciated, I hope to be able to test it quickly with a new site I'll create on purpose (I'm not updating my existing Drigg site yet)
Comment #73
mercmobily commentedHi,
The url rewrite is done. Yes, I am planning on releasing a drigg_distr -- in fact, I am planning on concentrating all the development on D6, since D5 is now nearly a year old.
Bye,
Merc.
Comment #74
iahead commentedGood job done Congrats Merc
Comment #75
Augusto Ellacuriaga commentedThanks Merc.,
This is great news! I'm going to test it with a template recently built for 5.x, but that has not been launched and will report back.
It will be nice to have the custom_url_rewrite mod before everything else, because that will cause less problems with indexing and Search Engine rankings.
Regards,
Augusto
Comment #76
Testering commentedFirst of all, congrats to Merc! Really, thanks for all the hard work.
I look forward to contributing in some form myself, but that can only happen if I find where to download the Drupal 6 packages for Drigg! ;p
This may seem like a silly question for most of you, but could someone please point me put in the right direction?
Comment #77
virtualdrupal commentedtry clicking "view all releases" from the drigg project page, sorry no copy and paste on the iphone so I can't link you
Comment #78
Testering commentedThanks, mikenotmike... I'll feel dumb now, but I spent quite a while trying to figure it out. Guess I missed that link.
Comment #79
mercmobily commentedHi,
WOOOOOOOOOOOOOPSSSSSSS...
Added the 6.x snapshot to the project's home!
Merc.
Comment #80
wwwoliondorcom commentedHi,
Has anybody already updated it's Drigg 5 website to Drigg 6 ?
Thanks.
Comment #81
jrglasgow commentedis there a way to get a release node for D6, even just an alpha or beta?
Comment #82
mercmobily commentedHi,
Define "release node for D6"
Merc.
Comment #83
alliax commentedI think he means not a dev version.
On the module page you have Official releases (only 5.x) and Development snapshots (5.x and 6.x)
it is often said that stable version are in the official release part and that development snapshots should NOT be used on a production server
Comment #84
jrglasgow commentedI mean tag the CVS branch something like DRUPAL_6--1-alpha1 and then add a new release to go with it.
The main reason why I prefer this is the development snapshot can change frequently, I think they repackage the dev packages every 12 hours with latest cvs updates. an official release, even if it is just an alpha release, will always be there if we want to view all releases.
Last month I was talking with another Drupaler about a module and he told me he had it on a production site in D6, well, I went to the project page and the only release for D6 was the dev snapshot, which didn't work. Because the dev snapshot is replaced every 12 hours when there are changes I couldn't just look at the history and find previous releases.
Comment #85
mercmobily commentedHi,
No stable version exists just yet -- I am waiting for people to confirm that it's 1000% OK. I am also gonna split Drigg into different smaller files, since D6 allows that to save memory.
Give it a couple of weeks!
merc
Comment #86
pvtsales commentedWhy don't you put an express installation (beta) so we can try it? If there's some problem we can report it.
Comment #87
mercmobily commentedHi,
I preref it if more experienced people test it. Having an express install now will lead to lots of generic bug reports, something hard to manage..
If you want to try it, you need to be able to install it.
Bye,
Merc.
Comment #88
Testering commentedHi Merc,
You mentioned earlier that you are "also gonna split Drigg into different smaller files."
I am in the process of theming Drigg for a new website (base on the default theme for D6). Is there any chance that this might break or affect the theme in some way?
In other words, is it wise to start theming for D6 at this point or would it be better to wait for a while?
Thanks,
Psycs
Comment #89
mercmobily commentedHi,
Psycs: No, it should be totally fine to do theming now. The "splitting up" is something that D6 allows, but it won't affect any of the "normal" things going on with Drigg.
Bye!
Merc,
Comment #90
summit commentedSubscribing, waiting for stable 6 version, thanks for the hard work until now Merc!, greetings, Martijn
Comment #91
mercmobily commentedHi,
Just want to point out that we should all thank copiously the GOOD guys at CMS Web Services Inc. who basically did the port. There will be proper thanks in the project's home page. They were fantastic!
Merc.
Comment #92
iahead commentedhttp://www.drigg-code.org/node/615
Express setup Drigg 6 pack
Comment #93
mercmobily commentedHi,
ihead, I have had unexpected events lately that have reduced the number of hours I spend on Drigg. It's temporary, but it might go on for 2 more weeks.
Ihead, is there any way for you to become the official maintainer of the "express drigg"?
Bye,
Merc.
Comment #94
iahead commentedYes Merc,
I would love too take it up
and lately there is lot of spamming happening at forums ..would you mind adding me adding me as mod over there will clean things up!
Comment #95
mercmobily commentedHi,
You are a star, iahead.
Can you please email me, so that we can organise everything?
I am so grateful...
Send me an email to merc followed by mobily1.com
Love you!
Merc.
Comment #96
iahead commentedSent you the mail..
Comment #99
MakeOnlineShop commentedAnd then ? Drupal 7 ?
Joking !
Comment #100
summit commentedWhy joking, this was a great module, shame nobody picks it up....I am not a good enough programmer, but would love this functionality...
greetings, Martijn
Comment #101
MakeOnlineShop commentedBecoming who really think that we will get a D7 version when we never got a D6 ?
Yes it's a good module !