It seems that the query is failing because MySQL doesn't understand the _utf8 bit in the query on line 649 of the search_functions.php file. MySQL 4.1.7+ should be able to understand the query, so you might want to recheck your MySQL version. When using PhpDig 1.8.8 RC1, see the following in the config file:
Code:
// you may have to change this constant depending on the page encoding, for instance...
// define('DETECT_ORDER','UTF-8,ISO-8859-7,ASCII'); // or
// define('DETECT_ORDER','UTF-8,Windows-1251,ASCII'); // or
// define('DETECT_ORDER','UTF-8,BIG-5,ASCII'); // or
// define('DETECT_ORDER','UTF-8,JIS,KOI8-R,EUC-KR,EUC-JP,SJIS,BIG-5'); // etcetera
// the first non UTF-8 encoding in the constant that 'matches' the page is used in conversion to UTF-8.
// note that some pages can match multiple encodings even though only one encoding displays correctly.
// for example, if you do a search and see chinese characters in german text, the order is not correct.
// you may need to set/reset this constant, as there is no perfect ordering for all pages.
// furthermore, some encodings have multiple names (e.g., CP1251 like Windows-1251).
// if needed, edit the function phpdigMakeUTF8 in robot_functions.php to account for multiple names.
define('DETECT_ORDER','UTF-8,KOI8-R,JIS,SJIS,CP936,BIG-5,EUC-CN,EUC-TW,EUC-KR,EUC-JP');
If you are using PhpDig 1.8.8 RC1 and indexing ISO-8859-1 content, try the following for DETECT_ORDER and check out the comments about DETECT_ORDER in the config file:
Code:
define('DETECT_ORDER','ISO-8859-1,ASCII');