Features / Usability

Features / Usability

Blog-Entry search problem

posts: 22 Switzerland

I use TikiWiki 1.8.4 (I updatet it from

And now when I search trough the blog-entrys I get the error:

Warning: mysql error: Can't find FULLTEXT index matching the column list in query:

SELECT COUNT(*) FROM tiki_blog_posts p LEFT JOIN tiki_blogs b ON b.blogId = p.blogId WHERE b.use_find = "y" AND MATCH(p.data,p.title) AGAINST ('test')
in /srv/www/htdocs/tiki184public/lib/tikidblib.php on line 133

Warning: Invalid argument supplied for foreach() in /srv/www/htdocs/tiki184public/lib/tikidblib.php on line 143

Fatal error: Call to a member function on a non-object in /srv/www/htdocs/tiki184public/lib/tikidblib.php on line 151

This only happens when I search trough the whole page (even when I shout down the blog feature???) and when I search trough the blog-entrys.

I think it have to do something with my entrys, so I deletet all the blogs! but it does not help.. I also went to the db and compared it with another db from a working TikiWiki.. badly im not realy good with mysql syntax, perhabs someone can give me a hint.

posts: 1092

looks like you database is not updated correctly
Can you check if you have a fulltext index in tiki_blog_posts and in tiki_blogs
Perhaps you can try to create a new database, run tiki.sql to load the tables and load you data

posts: 32 Greece

There is a full text index on table tiki_blog_posts by the name ft. If this index contains only data column you must drop it and build a new one full text too, containing data and title columns.

Your problem will be resovled.

posts: 22 Switzerland

Hm, im kinda afraid about doing that..
I did it once, with a Database I updatet some times before.. and because of that it seems like the tables are not in the same order as before.. and so the wrong data went into the wrong field..

and hmm, no I don't have an fulltext index in on of these tables, but as I said, I compaire two dbs togethere which are the same version, and one is working and one not.. both seems to be equal..

hmm I'll do the test with the tiki.sql

posts: 22 Switzerland

Okey.. I did what you said, and it worked! I just hope that there are no wrong data in a wrong table..

eam.. I made a file with diff from the struct of the bad db and the good db :-) so that you can see what went wrong.. perhabs someone of you can look at it and try to find out what went wrong with the updates...

I used a Tikiwiki for the old side, and updatet it to 1.8.4
as far as I remember is that database never updatet before.

I did the Update like this:

1. tiki_1.7to1.8.sql - this is the main upgrade script, it can be re-run as often as needed.

2. comments_fix_1.7to1.8.sql - only run this once on a 1.7 database, then never again
3. structure_fix_1.7to1.8.sql (or point your browser to db/structure_fix_1.7to1.8.php) - run this only once on a 1.7 database, then never again.

4. tiki_1.7to1.8.sql - rerun to fix forums

And here is the diff file: differences.txt

Eam.. to Updatet I needet to load tiki.sql then extract just the structure, delete the database and reinstert just the struct.. so I had a real plain db (because with tiki.sql there are already data inside) after that I insert the data I dumped from the "damaged" db.. and it works.

thanks a lot sylvie..

posts: 22 Switzerland

oha.. I forgot something..
here are the two files which belongs to the differences.txt! of course you need that to see what went wrong..

posts: 956

Hi Sylvie, matz, ...

I already posted this sort of problem as a comment on the tiki1.7->1.8 page, last December 4th, 2004 (and got no answer there).

Thanks for your hints Sylvie. But it brings to my mind a question that I've been posting several times and in several places:

  • What's happening with the update proces information and sql scripts from 1.7 to 1.8 ("the stable" version of Tiki)?

  • Could somebody update this bug info at UpgradeTo18 page, and the related sql scripts?

Thanks again for all your work, Sylvie, coding, answering people in forums, lists, etc.


posts: 956

I found out 2 differences regarding blogs, from a brand new 1.8.4 tiki installation compared to a updated 1.7.x updated to 1.8.4 with the provided scripts so far (with 1.8.4):

1. On table "tiki_blog_posts", column "data_size" seems to be wrong.
Line copied from a brand new 1.8.4 installation):

`data_size` int(11) unsigned NOT NULL default '0',

Line from a updated 1.7 to 1.8 with update sql scripts:

`data_size` int(10) unsigned default '0',

(I wonder if this may be important or not, but the fact is there).

2. On table "tiki_blog_posts", full text key info is uncomplete:

Brand new 1.8.4:

FULLTEXT KEY `ft` (`data`,`title`)

Updated 1.7.x to 1.8.4:

FULLTEXT KEY `ft` (`data`)

I'll post this also at the sf.net bugs, and I hope it is updated for the new 1.8.5 to be relased soon, due to the security whole, etc.
Cheers, Xavi

posts: 1092

I fixed this in 1.8cvs and 1.9 cvs . thanks

(Sorry - I re-post this message to check if the bug my post was appearing 2 times is still there .... forums are buggy)

posts: 1092

Just a reminder...

When you upgrade from 1.7.1 to 1.8.n, you are supposed First to upgrade 1.7.1 to the latest 1.7 (= running tiki_1.6to1.7.sql) and then you can upgrade to 1.8
Look at the bottom of this page UpgradeTo18

Perhaps it is not the problem. It is just a reminder

posts: 956

I had no idea before that I was supposed to update previously the ddbb with the 1.6 to 1.7sql ....rolleyes (I had missed this info wherever it was writen, if anywhere). However, it was not intuitive, I think (personal opinion).
Thanks once more, Sylvie, for your support. Xavi

posts: 22 Switzerland

Eam.. shame on me redface.. your actualy right.. this is the problem.. I didn't upgrade the version to the new 1.7! I didn't recognice the line at the page (or I didn't understand it right).

when I upgade my to the new one and then to 1.8(.4) it works just fine!
thanks again..

posts: 1092

I fixed this in 1.8cvs and 1.9 cvs . thanks

(Sorry - I re-post this message to check if the bug my post was appearing 2 times is still there .... forums are buggy)