search for strings with decimal points e.g.: 1.2

[graiffa]

if you search for e.g.: 1.2 then you get search results. when the search results are several pages, the "next" button doesn't work and you will stuck on the page 1, doesn't matt how aften you hit "next" or another page.

[James Aylett]

Are you using omega? It looks like you might be. Can you confirm version number of xapian-core, omega as well?

[graiffa]

Sorry the stupid question. How to find out which version I have ? (OS: Linux redhat4)

[James Aylett]

If you installed it as packages, the Redhat package manager (either graphical or the command line rpm tool) will be able to tell you. If not, then you'll need to figure out who installed from source, or find the source code (which generally has the version number in the director name).

[graiffa]

I didn't install this server, but i was searching the whole thing for version.h. please find the file xapian-v.txt attached.

[Olly Betts]

xapian-v.txt shows sources for several xapian versions are present, ranging from 0.9.9 to 1.2.2, so isn't much help.

You can find out the version you are actually running using --version - e.g. (though the path to your CGI directory may be different):

/usr/lib/cgi-bin/omega --version

The $version omegascript command can be added to the query template to report the version there.

I can't reproduce this with current trunk or 1.1.3, which are the two versions I happen to have to hand.

Does this really only happen for strings with decimal points? If it happened for any query, I'd suspect your query template was missing xP or something like that.

[Olly Betts]

Actually, check it with a different query with multiple words in - that might be a factor...

[graiffa]

Here the version output:

08:09:21:GRAIFFA@wiki:/var/www/cgi-bin$ omega --version omega - xapian-omega 1.0.14a (compiled Jul 28 2009 11:12:57)

it only happens with decimal points e.g. "indicom 1.2" indicom 1.5 1.6 indicom

not with other queries. it also doesn't happen if i search without trailing digits e.g.

indicom 1.

could you reproduce this issue with the latest versions ?

i guess you'll recommend an upgrade - where can i read how to do this ?

[Olly Betts]

Your find output suggests you've been using omega since pre-1.0.0 versions. If you started before 0.9.7, then maybe your query template builds the xP CGI parameter using periods as separators rather than tabs - that would explain the issue you're seeing (which is bug #87). I'd look if you have something like this:

$list{$queryterms,<INPUT TYPE=hidden NAME=xP VALUE=",.,.">}

and if so, replace it with this:

$if{$queryterms,<INPUT TYPE=hidden NAME=xP VALUE="$html{$queryterms}">}

But the 1.0 release series is essentially obsolete now, so I'd recommend upgrading. And (as I said above) I can't reproduce this issue with more recent versions.

One thing to be cautious of though is that we never made a "1.0.14a" release, so it looks like someone may have patched the install you are currently using.

I'm not sure how you are installing Xapian, which rather affects how you'd upgrade. If you're using a Linux distro, then they'll likely have packages of recent versions of xapian-core and omega (or xapian-omega), and you should be able to upgrade via the package manager. If you're installing from source, then download a newer release and follow the instructions in INSTALL.

There are notes on deprecated and removed features here, which it's useful to review, especially when upgrading to a newer release series:

​http://xapian.org/docs/deprecation

[Olly Betts]

No feedback from submitter for 4 weeks, but I'm confident that this is the same issue as #87, and the fix is to update the xP generation in the query template, so closing this ticket as a duplicate. If you disagree, please comment explaining why.