From: Chris Hastie (no email)
Date: Wed Aug 07 2002 - 13:13:47 EDT
Hi
I've just upgraded from 1.2.7 to 1.2.10, one reason for doing so was so
the fix of the date range limiting bug.
Having installed 1.2.10 I cleared the index completely, renamed cache to
rescache and re-indexed.
Following reindexing none of the date range functions appeared to work
at all (ie not dt=er, dt=back or dt=range). However, stopping and
restarting searchd seemed to sort this out, and the log gives a clue as
to why:
before re-indexing:
Starting search daemon from ASPseek v.1.2.10
Loaded 22016 values from lastmod file v.232
Loaded 22019 values from ranks file v.239
Started accepting queries on port 12345
after re-indexing:
Starting search daemon from ASPseek v.1.2.10
Loaded 10859 values from lastmod file v.1
Loaded 10863 values from ranks file v.1
Started accepting queries on port 12345
But I'm now finding it doesn't work again. Using dt=er seems to go back
only 1 day, irrespective of the value of dp, and all other values for dt
have the same effect. The one exception I can find it dt=er&dp=0
I've tried stopping and restarting searchd again, but without effect.
Any ideas what's going on?
The other problem I'm seeing is aspseek not honouring <meta
name="robots" content="follow, noindex"> tags.
-- Chris Hastie
|
|
|