Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Little mistake in last drupal version (5.4) , in taxonomy.module, line 1271 :
$result = db_query_range($sql, 0, variable_get('feed_default_items', 10),$args);
should be
$result = db_query_range($sql, $args, 0, variable_get('feed_default_items', 10));
Comment | File | Size | Author |
---|---|---|---|
#2 | db_query_range.patch | 752 bytes | Gábor Hojtsy |
Comments
Comment #1
hannesk CreditAttribution: hannesk commentedThank You Very Much For This Solution!
I was struggling with this problem for hours now and this saved my day :)
Thank You
Best Regards
Hannes
Comment #2
Gábor HojtsyCommitted this fix to Drupal 6. Will alert Niel Drumm, the Drupal 5 maintainer. Seems like we did not test this use case well, and introduced a bug here. Attached patch is RTBC for Drupal 5.
Comment #3
killes@www.drop.org CreditAttribution: killes@www.drop.org commented4.7 is patched
Comment #4
drummCommitted to 5.x.
Comment #5
chrisschaub CreditAttribution: chrisschaub commentedOk, can somebody give the line that needs to be changed for 4.7.8? Just want to fix the broken line. Thanks.
Comment #6
jason342 CreditAttribution: jason342 commentedSo the only difference between 5.4 and 5.5 is that one line of code, and nothing else?
Comment #7
Heine CreditAttribution: Heine commentedIf you do not update, but just copy the two files, update status will no longer work for your site.
The change:
Please do not further divert this issue.
Comment #8
mercmobily CreditAttribution: mercmobily commentedHi,
Quick question. I don't have time to upgrade right now.
What do you mean by:
"If you do not update, but just copy the two files, update status will no longer work for your site."
What update status?
Merc.
Comment #9
Gábor HojtsyUpdate status is a contribtued module which helps you getting informed about available updates for your site.
Comment #10
karthik_admin CreditAttribution: karthik_admin commentedHow to run the patch?
Comment #11
mercmobily CreditAttribution: mercmobily commentedHi,
I am a Drupal developer, and yet I don't know the basics. Shame on me.
Thanks for the hint,
Merc.
Comment #12
smikey CreditAttribution: smikey commentedAny chance of a hotfix for 5.5? Not great running patches as I'm not a dev. Thanks
Comment #13
Heine CreditAttribution: Heine commented5.5 doesn't have this bug. A patch for 5.4 is on #2.
Comment #14
Heine CreditAttribution: Heine commentedRestoring the version.
Comment #15
smikey CreditAttribution: smikey commentedThanks, Heine. I checked the module out, and 5.5 seems to be using the updated code. Anyone know why my Taxonomy module no longer shows up in my module list? Everything seemed to be working until I updated to version 5.5..
Comment #16
smikey CreditAttribution: smikey commentedTo answer my own question, the module is no longer in my Drupal db. What caused this, I have no idea. Thanks for your assistance on this.. :)
Comment #17
ron_mahon CreditAttribution: ron_mahon commentedI am having trouble with the taxonomy and CCK lookup field.
These all worked before the 5.4 and then 5.5 update.
The filter selects the proper vocabulary but returns a empty data set.
It i select just a tax term it works fine except all the other vocabulary's are present also.
I installed it with version
"$Id: taxonomy.module,v 1.330.2.14 2007/12/06 18:16:38 drumm Exp $" and it works fine.
"$Id: taxonomy.module,v 1.330.2.11 2007/09/12 07:49:36 drumm Exp $" version is the one with the strange behavior.
I look for the section referenced above, it's not on line 1271
Hope you can help
Many thanks
Ron
Comment #18
(not verified) CreditAttribution: commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #19
RobRoy CreditAttribution: RobRoy commentedRestoring correct title and version.