Category: Database MySQL (MyISAM)

if some person goes on a vandalism spree it would be great to have one button to undo all their edits

I am monitoring the dev.tw.o tracker and changed my e-mail adress to get the new tracker items to another mailbox.

Well, that didn't happen! ;)
And after re-subscribing to the tracker, now I get them twice - in both accounts.

I guess I'll have to change my mail-adress back and forth to unsubscribe..

amette update: just checked 1.9.x checkbox - more update: changing e-mail back and unsubscribing works flawlessly

{syntax type="tiki" editor="plain"}
On updating Tiki 5.2 and earlier to 6 errors occur during installation.

^Cannot execute queries while other unbuffered queries are active. Consider using PDOStatement
fetchAll(). Alternatively, if your code is only ever going to run against mysql, you may enable query buffering by setting the PDO MYSQL_ATTR_USE_BUFFERED_QUERY attribute.^

The problem is discussed [http://tiki.org/tiki-view_forum_thread.php?comments_parentId=39458&topics_offset=5&topics_sort_mode=lastPost_desc&forumId=6|over here]

--
Chealer:
This does not happen upgrading from a clean install of 5.3 to 6.0. But it happens when upgrading from 5.0 to 6.0. The most problematic script appears to be 20100927_better_column_fix_tiki. The first query (getOne() on information_schema) seems to be the sticky unbuffered query sometimes, since the following, second query fails. I tried but couldn't find how to confirm what query is stuck. It's odd that this problem only happens in the installer. getOne() just like query() use fetchAll() so we shouldn't see this problem. Setting MYSQL_ATTR_USE_BUFFERED_QUERY doesn't seem to help. After some 10 hours of debugging I'm under the impression this is a PDO bug. This looks like http://bugs.php.net/bug.php?id=44081 If anyone wants to try fixing, I recommend speaking to me first. The PDO documentation is very poor, making this really difficult.
20100927_better_column_fix_tiki was introduced in 5.3.

I found upgrades would work with PDO in certain environments. I had the bug on PHP 5.2.13 but upgrading to 5.3.3 fixed. PHP 5.3 can use mysqlnd, which I suspect doesn't have this problem. The upgrade worked for me on vanilla PHP 5.3.3 or PHP 5.3.3 from EasyPHP, both with mysqlnd. I have no clue why this problem seems to only affect Windows, but I saw reports of similar problems on Debian etch, so it may not be completely Windows-specific. Anyone who experiences this problem, please report your PHP version, and if you use PHP 5.3, indicate whether you use libmysql or mysqlnd.

{syntax type="tiki" editor="plain"}
Error when trying to start the Tiki after Upgrade from 3.1 to 4.1. The installation and upgrade during installation reported "Success":

"System error.
The following error message was returned:

Champ 'version_minor' inconnu dans field listThe query was:

SELECT `page_id`, `pageName`, `hits`, `description`, `lastModif`, `comment`, `version`, `version_minor`, `user`, `ip`, `flag`, `points`, `votes`, `wiki_cache`, `cache_timestamp`, `pageRank`, `creator`, `page_size`, `lang`, `lockedby`, `is_html`, `created`, `wysiwyg`, `wiki_authors_style`, `comments_enabled` FROM `tiki_pages` WHERE `pageName`=?
Values:

1.UserPageadmin
The built query was likely:

SELECT `page_id`, `pageName`, `hits`, `description`, `lastModif`, `comment`, `version`, `version_minor`, `user`, `ip`, `flag`, `points`, `votes`, `wiki_cache`, `cache_timestamp`, `pageRank`, `creator`, `page_size`, `lang`, `lockedby`, `is_html`, `created`, `wysiwyg`, `wiki_authors_style`, `comments_enabled` FROM `tiki_pages` WHERE `pageName`='UserPageadmin'
"

Using latest tikitrunk_svn from today (Jan. 24th, 2009)

I had a tiki site based on trunk from several weeks ago.
I added today another tiki site (using the same tiki files on server, thus using multitiki on subfolders)

Once the 2nd tiki site was up & running, I wanted to check the 1st tiki site, and it was complaining about mysql table missing, etc. So I went to run the "automatic database upgrade" ((doc:Tikiwiki 3)).
It needs to go through tiki-install.php, therefore so I did.
I had an (extracttoppath) issue, so that I attempted to go to tiki-admin.php from site one. The problem then was that tiki-index.php was complaining about:
^
The directory '/home/httpd/tikitrunk/modules/cache/javaoptics' does not exist.
The directory '/home/httpd/tikitrunk/templates_c/javaoptics' does not exist.
^

They seemed to have been deleted by the tiki-install.php script, since they were there a minute ago.
I tried also the other tiki site, and it happened the same, both folders were missing (deleted)

__Is this that tiki-install.php is not multitiki ready?__

---
duplicated bug report (by my mistake :-) ) with [bug2736]

Just play around with it (sending a task, etc) and you will see.


Maybe it's because this site has thousands of users and on a clean install, it will be fast.

---
When adding a task from a module:
[ Execution time: 212.52 secs ] [ Memory usage: 10.13MB ] [ 143 database queries used ] [ GZIP Enabled ] [ Server load: 6.65 ]
---

The problem seems to be with the module "user_tasks" and presumably "user_tasks_public". When these modules are not assigned (activated), the task feature is fast (and quite nice/complete, I must say). It appears to be when the module cache is (re)generated.

fields defined varchar(256) fail on MySQL 4.0

db/tiki.slq lines 4868 and 4877

the last two tables added: tiki_webmail_contacts_ext and tiki_webmail_contacts_fields

I would fix it if i had check-in powers sorted out (working on it) but i'm not sure that wouldn't it break anything else (in webmail?)

Please see this page:
http://tikiwiki.org/TikiWiki

When I am anonymous:
[ 1277 database queries used ]

Yes, when I log in:
[ 155 database queries used ]

In 1.9.0 (and probably 1.8.x), it is possible to delete a calendarId (ex.:1)

When this happens, all calitemId are set to calendarId=0

Items are still in the database but inaccessible.

When I click a user, I am offered to send him a message. But then I get:

User XYZ can not receive messages
ERROR: No valid users to send the message

1: WYSIWYCA: I should not be offered to send a message if the user has disabled that. (frustrating to write such a message for nothing)

2: tiki-user_preferences.php: "Allow messages from other users" default should be yes

3: tiki-user_preferences.php: "Send me an email for messages with priority equal or greater than:" default should be "3"

tiki-admin.php?page=login
3- Users accept internal messages by default: default should be yes -> $allowmsg_by_default

4- Users can opt-out internal messages: default should be yes -> $allowmsg_is_optional


All these should be the default settings (most logical) if a Tiki site admin choose to activate inter user messages.

Related:
Easier Inter-user message management for Tiki admins:
http://dev.tikiwiki.org/tiki-view_tracker_item.php?itemId=959

Also related:
Should sender email be disclosed when receiver gets notification via email? goals: balance privacy & facilitate communication/collaboration

{syntax type="tiki" editor="plain"}
After migration from 2.3 to 4.1 the following error occurs, if i try to open the image galerys with the link http://www.kfs-hg-test.de/tiki-galleries.php?filter=topgal:

select `sortorder`,`sortdirection` from `tiki_galleries` where `galleryId`='9'

The single pictures are available in the wiki oages as befiorder, but it is not possible to list the galerys.

10 MySQL "create table" commands are not compatible w/ the 3.23.58 version of MySQL

The last 2 use tables use ENGINE=MyISAM instead of TYPE=MyISAM and have a VARCHAR field of size 256 (255 is ok to use)

Here are those queries
Command: CREATE TABLE tiki_modules (
moduleId int(8) NOT NULL auto_increment,
name varchar(200) NOT NULL default '',
position char(1) default NULL,
ord int(4) default NULL,
type char(1) default NULL,
title varchar(255) default NULL,
cache_time int(14) default NULL,
rows int(4) default NULL,
params varchar(255) default NULL,
groups text,
PRIMARY KEY (name, position, ord),
KEY positionType (position, type),
KEY moduleId (moduleId)
) TYPE=MyISAM
Message: All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead

Command: CREATE TABLE tiki_page_drafts (
user varchar(200) default '',
pageName varchar(255) NOT NULL,
data mediumtext,
description varchar(200) default NULL,
comment varchar(200) default NULL,
lastModif int(14) default NULL,
PRIMARY KEY (pageName(120), `user`(120))
) TYPE=MyISAM
Message: All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead

Command: CREATE TABLE tiki_tracker_item_fields (
itemId int(12) NOT NULL default '0',
fieldId int(12) NOT NULL default '0',
lang char(16) default NULL,
value text,
PRIMARY KEY (itemId,fieldId,lang),
FULLTEXT KEY ft (value)
) TYPE=MyISAM
Message: All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead

Command: CREATE TABLE tiki_user_assigned_modules (
name varchar(200) NOT NULL default '',
position char(1) default NULL,
ord int(4) default NULL,
type char(1) default NULL,
user varchar(200) NOT NULL default '',
PRIMARY KEY (name(30),user,position)
) TYPE=MyISAM
Message: All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead

Command: CREATE TABLE `tiki_webmail_contacts_ext` (
`contactId` int(11) NOT NULL,
`fieldId` int(10) unsigned NOT NULL,
`value` varchar(256) NOT NULL,
`hidden` tinyint(1) NOT NULL,
KEY `contactId` (`contactId`)
) ENGINE=MyISAM
Message: Too big column length for column 'value' (max = 255). Use BLOB instead

Command: CREATE TABLE `tiki_webmail_contacts_fields` (
`fieldId` int(10) unsigned NOT NULL auto_increment,
`user` VARCHAR( 200 ) NOT NULL ,
`fieldname` VARCHAR( 256 ) NOT NULL ,
`order` int(2) NOT NULL default '0',
`show` char(1) NOT NULL default 'n',
PRIMARY KEY ( `fieldId` ),
INDEX ( `user` )
) ENGINE = MyISAM
Message: Too big column length for column 'fieldname' (max = 255). Use BLOB instead

I was running 1.9.9 on a SLES 10 linux box, and we are running MySQL on Novell Netware, MySQL version 4.0.26a.

I tried an upgrade directly over the top of 1.9.9, and I got that error. So, I tried a Clean install on a new database, and I got the same error.

As a troubleshooting step, I tried creating a blank database with the name that it specifies, but then it just gives the following error message
"Unknown column 'bits.translation_bit_id' in 'field list'".

I suspect the installer script isn't creating this table and fields properly.

This error occurs anytime any Page is clicked on, including the main index page. It is a major roadblock to basic functionality.

Bug report available at
https://sourceforge.net/tracker/index.php?func=detail&aid=1174695&group_id=64258&atid=506846

This tracker item could not be found

We need to decide about ((tw:DefaultSettingsChanges)) in 1.10

Some of the new features are much better than previous ones (ex new diff engine). People upgrading their Tiki could conserve their setting. However, new installs should take advantage of the new features.

A note should be added in tiki-install.php This must be low maintenance for Tiki dev team.

I created a tracker with several fields, mainly rating, textareas, dropdown, user selector, date selector.
||
Id position name type options isMain Tbl vis Searchable Public Hidden Mandatory
291 0 Rating system -2,-1,0,1,2 - y - y - -
293 edit 20 Descricpión de la incidencia textarea 1,60,5,1000 y y y y n y remove
294 edit 21 Tipología de redacción colaborativa drop down elegir uno,documentos de ofimática solo... n y y y n y remove
295 edit 22 Comentarios textarea 1,60,5,1000 n y y y n n remove
297 edit 27 Dia jscalendar n y y y n n remove
296 edit 30 Informante user selector 1 n y y y n n remove||

Called all fields from a wiki TRACKER plugin (the data field and user selector are not shown through plugin, even if configured as "public"), and submit some data (required and visible fields).

Then I got this error:

{CODE()}
Warning: mysql error: Duplicate entry '240-296' for key 1 in query:

insert into `tiki_tracker_item_fields`(`itemId`,`fieldId`,`value`) values(?,?,?)


in /var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/tikidblib.php on line 134


Context:
File /tiki-index.php
Url /tiki-index.php?trackit=10&page=prova&refresh=1&track%5B293%5D=prueba&track%5B294%5D=Wiki&track%5B295%5D=prueba&authorfieldid=296&track%5B296%5D=Xavi&action=Envia-ho
Query:
insert into `tiki_tracker_item_fields`(`itemId`,`fieldId`,`value`) values(?,?,?)
Values:
0 240
1 296
2 Xavi
Message:
Error Message Duplicate entry '240-296' for key 1


array(6) {
[0]=>
array(6) {
["file"]=>
string(65) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/tikidblib.php"
["line"]=>
int(84)
["function"]=>
string(9) "sql_error"
["class"]=>
string(10) "trackerlib"
["type"]=>
string(2) "->"
["args"]=>
array(3) {
[0]=>
&string(80) "insert into `tiki_tracker_item_fields`(`itemId`,`fieldId`,`value`) values(?,?,?)"
[1]=>
&array(3) {
[0]=>
int(240)
[1]=>
int(296)
[2]=>
string(4) "Xavi"
}
[2]=>
&bool(false)
}
}
[1]=>
array(6) {
["file"]=>
string(75) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/trackers/trackerlib.php"
["line"]=>
int(619)
["function"]=>
string(5) "query"
["class"]=>
string(10) "trackerlib"
["type"]=>
string(2) "->"
["args"]=>
array(2) {
[0]=>
&string(80) "insert into `tiki_tracker_item_fields`(`itemId`,`fieldId`,`value`) values(?,?,?)"
[1]=>
&array(3) {
[0]=>
int(240)
[1]=>
int(296)
[2]=>
string(4) "Xavi"
}
}
}
[2]=>
array(6) {
["file"]=>
string(87) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/wiki-plugins/wikiplugin_tracker.php"
["line"]=>
int(69)
["function"]=>
string(12) "replace_item"
["class"]=>
string(10) "trackerlib"
["type"]=>
string(2) "->"
["args"]=>
array(4) {
[0]=>
&string(2) "10"
[1]=>
∫(0)
[2]=>
&array(1) {
["data"]=>
array(6) {
[0]=>
array(3) {
["fieldId"]=>
int(293)
["value"]=>
string(6) "prueba"
["type"]=>
int(1)
}
[1]=>
array(3) {
["fieldId"]=>
int(294)
["value"]=>
string(4) "Wiki"
["type"]=>
int(1)
}
[2]=>
array(3) {
["fieldId"]=>
int(295)
["value"]=>
string(6) "prueba"
["type"]=>
int(1)
}
[3]=>
array(3) {
["fieldId"]=>
int(296)
["value"]=>
string(4) "Xavi"
["type"]=>
int(1)
}
[4]=>
array(4) {
["fieldId"]=>
string(3) "296"
["value"]=>
string(4) "Xavi"
["type"]=>
string(1) "u"
["options"]=>
int(1)
}
[5]=>
array(2) {
["fieldId"]=>
bool(false)
["value"]=>
string(5) "prova"
}
}
}
[3]=>
&string(1) "o"
}
}
[3]=>
array(4) {
["file"]=>
string(63) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/tikilib.php"
["line"]=>
int(4117)
["function"]=>
string(18) "wikiplugin_tracker"
["args"]=>
array(2) {
[0]=>
&string(156) "Formulari per informar d'incidències durant la redacció colaborativa de la "Guia Erasmus", segons la tipologia de redacció colaborativa emprada"
[1]=>
&array(7) {
["trackerId"]=>
string(2) "10"
["fields"]=>
string(23) "291:293:294:295:297:296"
["action"]=>
string(8) "Envia-ho"
["showtitle"]=>
string(1) "y"
["showdesc"]=>
string(1) "y"
["showmandatory"]=>
string(1) "y"
["embedded"]=>
string(1) "y"
}
}
}
[4]=>
array(6) {
["file"]=>
string(63) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/lib/tikilib.php"
["line"]=>
int(4399)
["function"]=>
string(11) "parse_first"
["class"]=>
string(7) "tikilib"
["type"]=>
string(2) "->"
["args"]=>
array(3) {
[0]=>
&string(752) "{img src="img/wiki_up/Categories-ADMIN-001.png" }

img src="img/wiki_up/Categories-ADMIN-001.png"

{TRACKER(trackerId=>10,fields=>291:293:294:295:297:296,action=>Envia-ho,showtitle=>y,showdesc=>y,showmandatory=>y,embedded=>y)}Formulari per informar d'incidències durant la redacció colaborativa de la "Guia Erasmus", segons la tipologia de redacció colaborativa emprada{TRACKER}

{TRACKERLIST(trackerId=>10,fields=>291:293:294:295:297:296,showtitle=>y,showlinks=>y,showdesc=>y,showinitials=>y,showstatus=>n,status=>opc,sort_mode=>asc,max=>3,filterfield=>294,filtervalue=>documentos de ofimática solo acesibles en local,exactvalue=>)}Notice{TRACKERLIST}"
[1]=>
&array(2) {
["data"]=>
array(0) {
}
["key"]=>
array(0) {
}
}
[2]=>
&array(2) {
["data"]=>
array(0) {
}
["key"]=>
array(0) {
}
}
}
}
[5]=>
array(6) {
["file"]=>
string(62) "/var/lib/gforge/chroot/home/groups/gclub/htdocs/tiki-index.php"
["line"]=>
int(401)
["function"]=>
string(10) "parse_data"
["class"]=>
string(7) "tikilib"
["type"]=>
string(2) "->"
["args"]=>
array(2) {
[0]=>
&string(752) "{img src="img/wiki_up/Categories-ADMIN-001.png" }

img src="img/wiki_up/Categories-ADMIN-001.png"

{TRACKER(trackerId=>10,fields=>291:293:294:295:297:296,action=>Envia-ho,showtitle=>y,showdesc=>y,showmandatory=>y,embedded=>y)}Formulari per informar d'incidències durant la redacció colaborativa de la "Guia Erasmus", segons la tipologia de redacció colaborativa emprada{TRACKER}

{TRACKERLIST(trackerId=>10,fields=>291:293:294:295:297:296,showtitle=>y,showlinks=>y,showdesc=>y,showinitials=>y,showstatus=>n,status=>opc,sort_mode=>asc,max=>3,filterfield=>294,filtervalue=>documentos de ofimática solo acesibles en local,exactvalue=>)}Notice{TRACKERLIST}"
[1]=>
&string(1) "0"
}
}
}
{CODE}

When installing TikiWiki 3.0 into MySQL (I'm using 5.1.35 but I don't think it matters much) where the database has been created with a charset of 'utf-8' (typically because this is the server default), one table cannot be created and that command and subsequent inserts fail:

{CODE()}
CREATE TABLE `tiki_sefurl_regex_out` (
`id` int(11) NOT NULL auto_increment,
`left` varchar(256) NOT NULL,
`right` varchar(256) NULL default NULL,
`type` varchar(32) NULL default NULL,
`silent` char(1) NULL default 'n',
`feature` varchar(256) NULL default NULL,
`comment` varchar(256),
`order` int(11) NULL default 0,
PRIMARY KEY(`id`),
UNIQUE KEY `left` (`left`(256)),
INDEX `idx1` (silent, type, feature(30))
)
y was too long; max key length is 767 bytes
{CODE}

The issue is that the table key is too long when using UTF-8. See [http://bugs.mysql.com/bug.php?id=4541].

This is error message:

Context:
File /tiki-newsletters.php
Url /tiki-newsletters.php
Query:
insert into `tiki_newsletter_subscriptions`(`nlId`,`email`,`code`,`valid`,`subscribed`,`isUser`) values(?,?,?,?,?,?)
Values:
0 16
1 marclaporte
2 f5c1651f42442974d3114db487c55be4
3 n
4 1142651354
5 y
Message:
Error Message Duplicate entry '16-marclaporte-y' for key 1

{syntax type="tiki" editor="plain"}
Error

An error occured in a database query!

Context:
File tiki-adminusers.php
Url tiki-adminusers.php

Query:

select distinct up.* from `users_permissions` as up, `users_grouppermissions` as ug where ug.`groupName` in () and up.`permName`=ug.`permName`

Values:

Message:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') and up.`permName`=ug.`permName`' at line 1

Built query was probably:

select distinct up.* from `users_permissions` as up, `users_grouppermissions` as ug where ug.`groupName` in () and up.`permName`=ug.`permName`

Exporting a tracker does not work when selecting a custom default sort order field for the tracker.
Fields that do work :
itemId
Created
Lastmodif

All other fields will result in a csv file containing the error page html code.

It seems that the order by value in the SQL statement is not properly generated.


File tiki-export_tracker.php
Url tiki-export_tracker.php
Query:
select * from `tiki_tracker_items` tti where tti.`trackerId`=? order by `` desc

Values:
0 4
Message:

Built query was probably:
select * from `tiki_tracker_items` tti where tti.`trackerId`='4' order by `` desc

Yesterday I upgraded from 4.3 to 5.2, and everytying seemed to go ok (all upgrade operations were executed successfully). However, every time I try to edit or create a file gallery I get the same error message, which seems to be related to a missing field (show_lastDownload) in the tiki_file_galleries table.

I copy below one of such errors. Please, note that, according to the community forums [http://tikiwiki.org/tiki-view_forum_thread.php?comments_parentId=38578&topics_offset=2&topics_sort_mode=lastPost_desc&forumId=6|this issue was already reported for a 4.3 to 5.1 upgrade].

I think that a) somebody should check the upgrade for a possible bug, and if possible b) find a way to solve this issue for sites running tiki 5.x with this feature broken.

---

The following error message was returned:

Unknown column 'show_lastDownload' in 'field list'

The query was:
insert into `tiki_file_galleries`(`name`, `description`, `created`, `user`, `lastModif`, `maxRows`, `public`, `hits`, `visible`, `show_id`, `show_icon`, `show_name`, `show_description`, `show_created`, `show_hits`, `show_lastDownload`, `max_desc`, `type`, `parentId`, `lockable`, `show_lockedby`, `archives`, `sort_mode`, `show_modified`, `show_creator`, `show_author`, `subgal_conf`, `show_last_user`, `show_comment`, `show_files`, `show_explorer`, `show_path`, `show_slideshow`, `default_view`, `quota`, `image_max_size_x`, `image_max_size_y`, `backlinkPerms`, `show_backlinks`) values (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)

Values:

1. mytestfilegallery
2.
3. 1285469672
4. jme
5. 1285469672
6. 25
7. n
8. 0
9. y
10. o
11. y
12. f
13. n
14. y
15. y
16. n
17. 1024
18. default
19. 19
20. n
21. n
22. -1
23.
24. y
25. o
26. o
27.
28. o
29. o
30. y
31. y
32. y
33.
34. list
35. 0
36. 0
37. 0
38. n
39. n

The built query was likely:
insert into `tiki_file_galleries`(`name`, `description`, `created`, `user`, `lastModif`, `maxRows`, `public`, `hits`, `visible`, `show_id`, `show_icon`, `show_name`, `show_description`, `show_created`, `show_hits`, `show_lastDownload`, `max_desc`, `type`, `parentId`, `lockable`, `show_lockedby`, `archives`, `sort_mode`, `show_modified`, `show_creator`, `show_author`, `subgal_conf`, `show_last_user`, `show_comment`, `show_files`, `show_explorer`, `show_path`, `show_slideshow`, `default_view`, `quota`, `image_max_size_x`, `image_max_size_y`, `backlinkPerms`, `show_backlinks`) values ('mytestfilegallery','','1285469672','jme','1285469672','25','n','0','y','o','y','f','n','y','y','n','1024','default','19','n','n','-1',NULL,'y','o','o',NULL,'o','o','y','y','y',NULL,'list','0','0','0','n','n')

List tracker items of dev.tw.o/tracker5
Filter them by summary for the word "group", or submitted by "xavidp" (for instance).
I get no results, when there are some (or plenty) records...

Made a new install of Tiki v3.2 on a Ubuntu 8.04.3 system as server (includes MySQL in version 5.0.51a-3ubuntu5.4).
Surfing at tiki-plugins.php produces the following error message:
{CODE(wrap="1",ln="0",ishtml="1")}<div class="cbox-data"><br>
<div class="simplebox error">
<div class="simplebox"><b>An error occured in a database query!</b></div><br>
<table class="form">
<tbody><tr class="heading"><td colspan="2">Context:</td></tr>
<tr class="formcolor"><td>File</td><td>tiki-plugins.php</td></tr>
<tr class="formcolor"><td>Url</td><td>tiki-plugins.php</td></tr>
<tr class="heading"><td colspan="2">Query:</td></tr>
<tr class="formcolor"><td colspan="2">
<tt>SELECT fingerprint, added_by, last_update, last_objectType, last_objectId FROM tiki_plugin_security WHERE status = 'pending' ORDER BY last_update DESC</tt>
</td></tr>
<tr class="heading"><td colspan="2">Values:</td></tr>
<tr class="heading"><td colspan="2">Message:</td></tr>
<tr class="formcolor"><td colspan="2"></td></tr>

<tr class="heading"><td colspan="2">Built query was probably:</td></tr>
<tr class="formcolor"><td colspan="2">SELECT fingerprint, added_by, last_update, last_objectType, last_objectId FROM tiki_plugin_security WHERE status = 'pending' ORDER BY last_update DESC</td></tr>
</tbody></table>
</div>
<br><br>
</div>
{CODE}
edit: Sorry, forgot to mention that this bug also affects the using of plugins. Using a plugin in a wiki page that needs approval produces the same error message. (Saw someone in [http://irc.tikiwiki.org/irclogger_log/tikiwiki?date=2009-10-02,Fri|the irc log] with this problem, which is also ===this=== bug, so I edit to clarify it.)

Categorisation is a social problem - different people have different words for the "same" category.

Use Google-like tags (check schtuff.com for a nice example) - this would make lots of wiki pages easier to find, IMHO.