Textpattern Forum

You are not logged in. Register | Login | Help

#1 2007-08-28 16:48:57

Trismegistus
New Member
Registered: 2005-10-22
Posts: 6

Tag Error after upgrade to 4.0.5

Hi there!

After the upgrade from 4.0.4 to 4.0.5 I found that everything was working just fine (as always with Textpattern) – except my search-section.

For some reason I now get the following tag error (while searching for the keyword “information” for example):

Tag error:  <txp:article searchall="1" /> ->  Textpattern Warning: 
select *, unix_timestamp(Posted) as uPosted, match (Title,Body) against ('information') as score from textpattern where 1 and Status = 4 and Posted <= now() and (Title rlike 'information' or Body rlike 'information') and Section != 'search' and Section != 'info' and Section != 'missing' and Section != 'shop' and Section != 'tag' order by score desc limit 0, 10  on line 84

The funny part is that the search itself seems to work. The txp:page_url tag displays the keyword as normal, and the txp:search_result_count tag displays the correct number of hits. But then the article-tag fail to show the results.

/ Peter

Offline

#2 2007-08-28 16:55:05

ruud
Developer emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 4,571
Website

Re: Tag Error after upgrade to 4.0.5

Is that the complete error message?

Offline

#3 2007-08-28 17:18:57

Trismegistus
New Member
Registered: 2005-10-22
Posts: 6

Re: Tag Error after upgrade to 4.0.5

Yes, it’s the complete error message in testing-mode. In debugging-mode the results-page is completely blank – a zero-byte file.

/ Peter

Offline

#4 2007-08-28 17:25:37

ruud
Developer emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 4,571
Website

Re: Tag Error after upgrade to 4.0.5

Please post your diagnostics (admin -> diagnostics)

Offline

#5 2007-08-28 18:26:44

Trismegistus
New Member
Registered: 2005-10-22
Posts: 6

Re: Tag Error after upgrade to 4.0.5

Textpattern version: 4.0.5 (r2466)
Last Update: 2007-08-23 10:52:34/1970-01-01 00:00:00
Document root: /home/web27151/domains/trismegistus.se/public_html
$path_to_site: /home/web27151/domains/trismegistus.se/public_html/propaganda
Textpattern path: /home/web27151/domains/trismegistus.se/public_html/propaganda/textpattern
Permanent link mode: section_id_title
Temporary directory path: /home/web27151/domains/trismegistus.se/public_html/propaganda/textpattern/tmp
Site URL: www.trismegistus.se/propaganda
PHP version: 5.2.1
Register globals: 1
GD Image Library: bundled (2.0.28 compatible); supported formats: GIF, JPG, PNG.
Server Local Time: 2007-08-28 19:26:01
MySQL: 5.0.27
Locale: en_GB.ISO_8859-1
Server: Apache/1.3.37 (Unix) mod_gzip/1.3.26.1a mod_fastcgi/2.4.2 FrontPage/5.0.2.2623 PHP/5.2.1 with Suhosin-Patch mod_ssl/2.8.28 OpenSSL/0.9.7e-p1
Apache version: Apache/1.3.37 (Unix) mod_gzip/1.3.26.1a mod_fastcgi/2.4.2 FrontPage/5.0.2.2623 PHP/5.2.1 with Suhosin-Patch mod_ssl/2.8.28 OpenSSL/0.9.7e-p1
PHP Server API: apache
RFC 2616 headers:
Server OS: FreeBSD 6.2-PRERELEASE
Active plugins: chh_if_data-0.10,, ob1_modified-0.51, ob1_googlenav-2.0m, wet_slimpattern-0.4.1, smd_lib-0.21a, smd_slimbox-0.24, rss_admin_show_adv_opts-0.1, ied_replacer-0.1m, tru_tags-2.3, csb_if_newer_than-1.0, zem_contact_reborn-4.0.3.18, zem_contact_lang-4.0.3.5m

Pre-flight check:
————————————
.htaccess file is missing
Some Textpattern files have been modified: /include/txp_article.php, /publish.php
————————————

The modified files are for the “10 more custom fields”-hack (txp_article.php) and for expanding the search to custom fields (publish.php). Unfortunately, the error already existed before I modified the two files.

You can see the error “live” here

Last edited by Trismegistus (2007-08-28 18:32:37)

Offline

#6 2007-08-28 20:44:13

ruud
Developer emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 4,571
Website

Re: Tag Error after upgrade to 4.0.5

The error shown there uses a query that does not search custom fields.

What happens without those hacks and plugins (clean 4.0.5 install).

Although probably not related to this problem, you have a prerelease FreeBSD version installed (6.2 final was released in january)

Offline

#7 2007-08-29 16:02:07

Trismegistus
New Member
Registered: 2005-10-22
Posts: 6

Re: Tag Error after upgrade to 4.0.5

Now I tried with a clean install, without any hacks and with all plugins deactivated – but I get the same Tag-error. Now with the addition “ Textpattern Warning: Can’t find FULLTEXT index matching the column list” :

Tag error: <txp:article searchall=“1” /> -> Textpattern Warning: Can’t find FULLTEXT index matching the column list
select *, unix_timestamp(Posted) as uPosted, match (Title,Body) against (‘information’) as score from textpattern where 1 and Status = 4 and Posted <= now() and (Title rlike ‘information’ or Body rlike ‘information’) and Section != ‘search’ and Section != ‘info’ and Section != ‘tag’ order by score desc limit 0, 10 on line 84

It seems like the problem is in the database…

Offline

#8 2007-08-29 16:20:24

ruud
Developer emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 4,571
Website

Re: Tag Error after upgrade to 4.0.5

Indeed. You’re missing a FULLTEXT index for ‘Title, Body’ on the textpattern table. Easy to fix with phpmyadmin.

Offline

#9 2007-08-29 16:29:06

Trismegistus
New Member
Registered: 2005-10-22
Posts: 6

Re: Tag Error after upgrade to 4.0.5

After viewing the table-structure In phpMyAdmin I found the following warnings:

txt_form: PRIMARY and INDEX keys should not both be set for column `name`

txp_lang: UNIQUE and INDEX keys should not both be set for column `lang`

txp_page: PRIMARY and INDEX keys should not both be set for column `name`

txp_plugin : UNIQUE and INDEX keys should not both be set for column `name`

txp_section; PRIMARY and INDEX keys should not both be set for column `name`

Maybe it’s also related to the problem?

Thanks
Peter

Offline

#10 2007-08-29 17:14:29

ruud
Developer emeritus
From: a galaxy far far away
Registered: 2006-06-04
Posts: 4,571
Website

Re: Tag Error after upgrade to 4.0.5

Nope, you wouldn’t see the missing FULLTEXT index as a warning in phpmyadmin. It simply isn’t there.

Offline

Board footer

Powered by FluxBB