It looks like the Drupal 5 version of the module is actually comprised of the Drupal 6 version's code.

This happened when I did my first Drupal 5 release (5.x-1.1-beta1). I could have sworn I had corrected the issue, but apparently not. If you are having trouble with the Drupal 5 version of the module, this is the problem.

I will work on addressing this problem soon (I'm at work right now, but the code's at home). Suffice it to say that this is my first time working with the CVS versioning system and I'm finding it rather difficult to work with.

I apologize for any confusion this problem may have caused.

Comments

Garrett Albright’s picture

Garrett Albright commented

Replying to this issue just to "bump" it back up to the top of the issue queue.

Garrett Albright’s picture

Garrett Albright commented

Okay, the D5 version of this module should now have the D5 code in it. I corrected the regular expression used to find paths a bit too (#247474). Once again, I apologize to everyone for my dumbness, and hope you can give this module another try.

Garrett Albright’s picture

Garrett Albright commented
Status: Active » Fixed
Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.