1.8 rc3 upgraded from 1.7.1.1
windows
iis
Search for "search words". Result:
Warning: error: Can't find FULLTEXT index matching the
column list in query:
SELECT COUNT(*) FROM tiki_pages WHERE 1 AND
MATCH(pageName,data) AGAINST ('search words')
in C:\tikiwiki-1.8.RC3\lib\tikidblib.php on line 125
Values:
$result is false
$result is empty
Terris Linenbach
2004-01-05
Logged In: YES
user_id=155319
Here is the fix:
Alter lib/searchlib.php
Find:
'search' => array('pageName', 'data'),
Replace with:
'search' => array('pageName', 'description', 'data'),
Philippe Cloutier
2004-01-05
Logged In: YES
user_id=738765
See ReleaseProcess18, reopen if not working, I don't know
what's with your fix...is redflo's one the same?
Philippe Cloutier
2004-01-05
Philippe Cloutier
2004-01-05
Logged In: YES
user_id=738765
The bug you reported may have been fixed. Please get the latest
version from
http://sourceforge.net/project/showfiles.php?group_id=64258 , or
from CVS http://sourceforge.net/cvs/?group_id=64258 , and retest
the issue.
If the problem persists then please add a comment with
more details to the same bug item.
If the problem is gone then please close the bug.
Nobody/Anonymous
2004-02-10
Logged In: NO
The fix for me was to create a second full text index for
just 'data'. The create table script below creates a full text
index for data and title.
CREATE TABLE tiki_blog_posts (
postId int(8) NOT NULL auto_increment,
blogId int(8) NOT NULL default '0',
data text,
data_size int(11) unsigned NOT NULL default '0',
created int(14) default NULL,
user varchar(200) default NULL,
trackbacks_to text,
trackbacks_from text,
title varchar(80) default NULL,
PRIMARY KEY (postId),
KEY data (data(255)),
KEY blogId (blogId),
KEY created (created),
FULLTEXT KEY ft (data,title)
) TYPE=MyISAM AUTO_INCREMENT=1 ;
2
-- C --
Philippe Cloutier
2004-03-16
Philippe Cloutier
2004-03-16
Logged In: YES
user_id=738765
This was reported fixed by hsaelens with this change :
search' => array('p.data'),
to
'search' => array('p.data','p.title'),
line 332
and it works for me. However I red 2 or 3 people saying they
had 1.8.1 but this bug too.
Philippe Cloutier
2004-03-16
Logged In: YES
user_id=738765
terris' fix was applied on BRANCH-1-8 by wolff_borg on
20040109 and went in release 1.8.0. Something else must be
causing it.
Reading lib/searchlib.php's log, two commits pretend to fix
this bug but it seems it still happens.
Paul Sue
2004-04-11
Logged In: YES
user_id=848660
I'm running 1.8.1 and I get the same problem ...
Well, I decided to use the search_new module instead.
With search_new I no longer get any error message .. but
unfortunately, I also don't get any search results!! Doesn't
matter if the setting is Entire Site, Wiki pages, blogs,
etc., I always get 0 results back no matter what I try!
This is a serious showstopper and I'll have to revert back
to 1.7.x if this isn't fixed!!
Paul Sue
2004-04-18
Logged In: YES
user_id=848660
I tested search_new on my friend's 1.8RC3 and it works fine!
So what has changed from 1.8RC3 to 1.8.1 that causes
search_new to not work (at least for me). Did something go
awry in my upgrade from 1.7.1.1 -> 1.7.4 -> 1.8.1 ???
Augh!!!!!!