Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
i made some small changes but like killes, i'm not using it on my sites so it's low priority. the change to using the $node->content array should make it possible to remove quite a bit of code though.
This is the only module I'm waiting on before I can update my sites, and I don't think I can wait much longer. If the module isn't a priority for the maintainer, it can't really be a priority for me.
Is there anyway to un-install this module without screwing up the structure of the nodes that use it? or should I just delete those nodes?
hey dude, it's open source, your cost for the module: $0 so don't act like we owe you something. you're welcome to submit patches or hire someone to do so if it is that important to you.
I'm not acting like you or anyone else in the Drupal community owes me anything. If anything, I owe the Drupal community!
If I knew how to submit patches, I would do it. If I knew how to update the module to be 5.0 compatible, I would be more than happy to do it so everyone else can use this module.
There's no need to look down on me just because I'm less proficient at module development than you or anyone else involved with maintaining this or any other module. I came here just to find out if there were any efforts being made to make this module 5.0 compatible, and was of course, disappointed when I realized there wasn't simply because "it's not important".
I think this is a great module, and would have used it on majority of the sites that I build. So dude, I mean NO disrespect to you, nor anyone else involved in the maintenance of this or any module.
Maybe if the module development learning curve wasn't so big, anyone and everyone would be able to come in and submit patches. Would you be willing to sit down with me and teach me how to do it?? Chances are you're not willing to do that because it doesn't improve your quality of life, and more than likely, you don't have the time. If you ever do, I'm right here and willing to learn.
Sorry for any disrespect you or anyone else may have felt by my previous comment.
i'm sorry i was so gruff but the tone of your post really rubbed me the wrong way. i'd love to show you how to roll a patch but i really don't have the time. i can offer you two resources though: http://drupal.org/patch http://groups.drupal.org/drupal-dojo
Comments
Comment #1
killes@www.drop.org commentedSince I currently don't use the module myself it isn't high on the to-do list. I'd review patches, though.
Comment #2
drewish commentedi made some small changes but like killes, i'm not using it on my sites so it's low priority. the change to using the $node->content array should make it possible to remove quite a bit of code though.
Comment #3
jswaby commentedThis is the only module I'm waiting on before I can update my sites, and I don't think I can wait much longer. If the module isn't a priority for the maintainer, it can't really be a priority for me.
Is there anyway to un-install this module without screwing up the structure of the nodes that use it? or should I just delete those nodes?
Comment #4
drewish commentedhey dude, it's open source, your cost for the module: $0 so don't act like we owe you something. you're welcome to submit patches or hire someone to do so if it is that important to you.
Comment #5
killes@www.drop.org commentedI don't think there would be a problem with simply disabling the module. Just give it a try.
Comment #6
jswaby commentedI'm not acting like you or anyone else in the Drupal community owes me anything. If anything, I owe the Drupal community!
If I knew how to submit patches, I would do it. If I knew how to update the module to be 5.0 compatible, I would be more than happy to do it so everyone else can use this module.
There's no need to look down on me just because I'm less proficient at module development than you or anyone else involved with maintaining this or any other module. I came here just to find out if there were any efforts being made to make this module 5.0 compatible, and was of course, disappointed when I realized there wasn't simply because "it's not important".
I think this is a great module, and would have used it on majority of the sites that I build. So dude, I mean NO disrespect to you, nor anyone else involved in the maintenance of this or any module.
Maybe if the module development learning curve wasn't so big, anyone and everyone would be able to come in and submit patches. Would you be willing to sit down with me and teach me how to do it?? Chances are you're not willing to do that because it doesn't improve your quality of life, and more than likely, you don't have the time. If you ever do, I'm right here and willing to learn.
Sorry for any disrespect you or anyone else may have felt by my previous comment.
Comment #7
drewish commentedi'm sorry i was so gruff but the tone of your post really rubbed me the wrong way. i'd love to show you how to roll a patch but i really don't have the time. i can offer you two resources though:
http://drupal.org/patch
http://groups.drupal.org/drupal-dojo
Comment #8
killes@www.drop.org commentedI've ported the module, a test release for D5 should be available later today at http://drupal.org/node/128653
Please create new issues for errors you should discover.
Comment #9
(not verified) commented