Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.this is strange, it used to work well and I'm not sure what triggered it.
if i search some words like "mysql", "linux" the results are that lots of posts are hit, most of the nodes/posts do not actually contain the keyword. if I search some different keywords such as "locale", or "aptitude", only the posts/nodes containing the keyword are shown.
i saw this on drupal6.6, after a upgrade to 6.8, it does not go away.
Comments
Comment #1
Anonymous (not verified) commentedi did re-run the cron manually and re-index 100% of my site, still the problem stays.
Comment #2
Anonymous (not verified) commentedComment #3
Anonymous (not verified) commentedif i disable pagination module, searching "mysql" works fine. if i enable it again, searching "mysql" will show _all_ my nodes. additionally, when pagination is enabled, search "php" will not hit all the posts. other keywords i tried work well though. "mysql" and "php" is what drupal uses, so maybe pagination somehow caused a leak for those keywords into search module?
Comment #4
mundanity commentedHi Xxiao,
That is really odd, pagination doesn't hook into anything that I can imagine would affect search. I'll take a closer look tomorrow and see if I can isolate the issue. What other modules (beyond the base install) do you have enabled?
Comment #5
Anonymous (not verified) commentedi have node_privacy, geshi filter, backup_migrate, plus pagination. nothing else.
disable pagination and enable it again will show "mysql", also when I search "php", not all nodes with "php" keywords are shown up if i enable pagination, while "mysql" will bring up all nodes as a "hit" by the search. i tried to use both manually paging and auto-paging under pagination module, no change on the results.
thanks for looking into this. i really like your pagination module as some of my posts are too long to stay in one page.
Comment #6
boringkid commentedI'm getting pretty much the same, have a clean install, cck, views and panels installed, plus this module, created a new cck node type and added about 10 articles. Do a search for any keyword with pagination on and all of the articles will be returned in results with 'teaser' underneath article title showing 'teaser' from article which actually contains the keyword.
Turn pagination off and you only get the article with the keyword displayed.
Shame because this works really well in every other way.... Does anyone have any solutions would be grateful.
Comment #7
Anonymous (not verified) commenteddid more tests with pagination module. when enabled for auto-paging, it will break in the middle of some html pairs (e.g. < code > ... < / code >) and some browser output will be blank because of that, some of my pages are full source code between "code" pairs so they just disappear when i tried to display them with pagination auto-paging on.
Comment #8
mundanity commented@boringkid
Would it be possible to provide a URL for me to take a look? I'm unable to reproduce this issue using my test environment. Also just as a data point, what version of Drupal 6 are you using?
@xxiao
Hmm, auto-pagination uses Drupal's teaser functionality, so theoretically there shouldn't be an issue. I've used it with a decent sized code block without issue, can you provide a link to a broken example for me?
Comment #9
Anonymous (not verified) commentedi had to turn off pagination to show my geshifilter coding pages when auto-paging is on. i'm using 6.8. for now i have to disable pagination to make my site "reliable".
Comment #10
mundanity commentedHi there,
I don't think there's a lot I can do with geshifilter as it's server side, and places piles of tags everywhere. I'll continue to look for a solution but I'm not really that keen on implementing a full fledged tag scanner to avoid situations like this. If I can think of a more elegant solution though I'll definitely see if I can make pagination play nice with things like geshifilter.
Comment #11
mundanity commented@boringkid
Sorry for the delay on this fix, the dev version will fix search issues. However, previous affected nodes (ie, already indexed) will have to be rebuilt. This can be done by updating the affected nodes with a trivial edit, or changing the reindex field in the search_dataset table for affected nodes to 1 (if you feel comfortable working at the DB level).