[support] Best way to fix a bug?

Earnie Boyd earnie at users.sourceforge.net
Thu Sep 13 13:24:36 UTC 2007


Quoting Jim Smith <jsmith at wate.com>:

> I know I was being vague. I was trying to ask the question in general
> terms so that I would know how to handle all bugs, rather than the
> specific one I'm dealing with now. Though I'd love to have help on the
> specific bug I'm dealing with, I know that only a few people might have
> knowledge about the module that has the bug. However, many people deal
> with debugging scripts everyday, and that's why I was looking for some
> strategies to best track down and fix bugs.
>

Well, you were too vague for me to even conclude this.  You stated that 
you were "not a coder" and coders are the ones that "track down and fix 
bugs".

> But to be specific about the particular bug I'm dealing with, it's in
> Yahoo Terms module.
>
> I posted a bug report on it at http://drupal.org/node/166932. As I first
> described the problem, Yahoo Terms were being applied to other content,
> like a forum post, though the Yahoo Terms module was not associated with
> that content. That was fixed with the patch supplied by douggreen at
> http://drupal.org/node/171620.
>

You used the patch; you should have provided feedback to 171620.  Doug 
Green cannot do any more than he has done until feedback is given.  If 
feedback had been given perhaps the patch could have moved forward and 
been applied.

> Since then I have upgraded the site to Drupal 5.2 and all of the
> modules. Now I'm seeing the same error on all feed nodes. The error
> happens only when the terms are applied when the node is created. It
> does not happen if the terms are re-applied to an existing node.
>

What were you using before 5.2?  I don't see a released module for 
yahoo_terms; there are only development snapshots.  A development 
snapshot is updated with every CVS update which may or may not work as 
expected.  Development snapshots are for coders to apply the test then 
recode cycle with.

> It appears that an array is not presented where the function
> array_merge() expects to see one in the argument.
>

Maybe Doug Green will jump at the chance to refresh the patch, maybe 
not.  Maybe someone else will.  I'm not interested at the moment 
because it isn't something I'm using or plan to use.

Earnie -- http://for-my-kids.com/
-- http://give-me-an-offer.com/



More information about the support mailing list