Category: Database MySQL (MyISAM)

{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.

Homework feature has been kicked out - but the permissions are still in there, when looking at

Admin -> Groups

I am running Tiki 1.9.7 with MySQL on Linux.

I have gone through the tiki_mysql.sql file and have found no reference to the column listed in the error message:

---
Context:
File tiki-galleries.php
Url tiki-galleries.php
Query:
select g.*, a.`name` as parentgalleryName from `tiki_galleries` g left join `tiki_galleries` a on g.`parentgallery` = a.`galleryId` order by `name` desc
Values:
Message:
Error Message Unknown column 'g.parentgallery' in 'on clause'
---

This appears as soon as I click on "Image Galleries" folder from the Menu module, or "Galleries".

I also get the same error message when I try and click on "Upload Image":

---
Context:
File tiki-upload_image.php
Url tiki-upload_image.php
Query:
select g.*, a.`name` as parentgalleryName from `tiki_galleries` g left join `tiki_galleries` a on g.`parentgallery` = a.`galleryId` order by `lastModif` desc
Values:
Message:
Error Message Unknown column 'g.parentgallery' in 'on clause'
---

Apparently this column needs to exist, but I have no idea what the column settings should be. This is preventing me from even using the image gallery feature.

subtitles and topline have 255 characters so why is title limited?

Default values in tiki-integrator don't work:

{CODE}
INSERT INTO tiki_integrator_rules VALUES ('1','1','1','.*<body[^>]*?>(.*?)</body.*','\1','y','n','i','y','Extract code between <body> and </body> tags');
{CODE}

The 'i' for regex options should be 'ism' to not only ignore case, but process multiline and let '.' match newlines. As is, it only works if the original page is all on one line.

Likewise the "\1" needs an extra \, and should be '\\1'. mysql is eating the first one and thinking that it is just unmagicking the '1', which didn't need it.

I would fix this, but editing the .sql files scares me. :)

Sorry if I'm either reporting this in the wrong place, or reporting a known issue. I've looked around a bit but couldn't find my problem listed. I have two TW installations that have run fine for 2 years, and I just downloaded the latest version of TW for a new application.

Created a MySQL 4 database.
Ran the automatic installation routine.

Got told there were 1000+ OK SQL statements, and 1 that failed.

When I click on "details" I get:

Command: CREATE TABLE tiki_profile_symbols (
`domain` VARCHAR(50) NOT NULL,
`profile` VARCHAR(50) NOT NULL,
`object` VARCHAR(50) NOT NULL,
`type` VARCHAR(20) NOT NULL,
`value` VARCHAR(50) NOT NULL,
`named` ENUM('y','n') NOT NULL,
`creation_date` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY( `domain`, `profile`, `object` ),
INDEX(`named`)
)
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 'CURRENT_TIMESTAMP,
PRIMARY KEY( `domain`, `profile`, `object`

I did this a second time to make sure (brand new directory on the server, and brand new SQL database). I cannot access the Admin-Modules segment in my new TW installation; I get the following error. Everything else appears to work -- new setup is at http://dev.steadfastlutherans.org .. second setup is at http://dev.steadfastlutherans.com .. I can give anyone admin access if you need it.

Pretty standard linux install, using 1and1.com servers.

Any help appreciated!




An error occured in a database query!

Context:
File tiki-admin_modules.php
Url tiki-admin_modules.php
Query:
SELECT `tc`.*, tpcd.`data`, COALESCE(`tpcf`.`future`,0) AS `future`, COALESCE(`tpca`.`actual`,?) AS `actual`, COALESCE(`tpcn`.`next`,?) AS `next`, GREATEST(0, COALESCE(`tpco`.`old`,0) - 1) AS `old` FROM (`tiki_content` AS `tc` LEFT JOIN ( SELECT `contentId`, count(*) AS `future` FROM `tiki_programmed_content` WHERE `publishDate`>? GROUP BY contentId ) AS `tpcf` ON ( `tc`.`contentId` = `tpcf`.`contentId` ) LEFT JOIN ( SELECT `contentId`, max(`publishDate`) AS `actual` FROM `tiki_programmed_content` WHERE `publishDate`<=? GROUP BY contentId ) AS `tpca` ON ( `tc`.`contentId` = `tpca`.`contentId` ) LEFT JOIN ( SELECT `contentId`, min(`publishDate`) AS `next` FROM `tiki_programmed_content` WHERE `publishDate`>=? GROUP BY contentId ) AS `tpcn` ON ( `tc`.`contentId` = `tpcn`.`contentId` ) LEFT JOIN ( SELECT `contentId`, count(*) AS `old` FROM `tiki_programmed_content` WHERE `publishDate`<? GROUP BY contentId ) AS `tpco` ON ( `tc`.`contentId` = `tpco`.`contentId` ) LEFT JOIN ( SELECT `contentId`, `data`, `publishDate` FROM `tiki_programmed_content` ) AS `tpcd` ON ( `tc`.`contentId` = `tpcd`.`contentId` AND `tpcd`.`publishDate` = `tpca`.`actual` )) ORDER BY `contentId` desc
Values:
0 1229233709
1 1229233709
2 1229233709
3 1229233709
4 1229233709
5 1229233709
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 'SELECT `contentId`, count(*) AS `future` FROM `tiki_programmed_

{syntax type="tiki" editor="plain"}
Am trying to install 1.9-BRANCH (1.9.8) on my server. 1.9.7 worked fine, 1.10 worked fine after a tweak, but this 1.9.8 install seems to barf.

Running Mysql 4.1.1, and have even copied the db/tiki-1.9-mysql.sql contents for the create table segments that failed and used phpMyAdmin without success. A full example is:
{CODE()}

Command: CREATE TABLE tiki_articles (
articleId int(8) NOT NULL auto_increment,
topline varchar(255) default NULL,
title varchar(80) default NULL,
subtitle varchar(255) default NULL,
linkto varchar(255) default NULL,
lang varchar(16) default NULL,
state char(1) default 's',
authorName varchar(60) default NULL,
topicId int(14) default NULL,
topicName varchar(40) default NULL,
size int(12) default NULL,
useImage char(1) default NULL,
image_name varchar(80) default NULL,
image_caption text default NULL,
image_type varchar(80) default NULL,
image_size int(14) default NULL,
image_x int(4) default NULL,
image_y int(4) default NULL,
image_data longblob,
publishDate int(14) default NULL,
expireDate int(14) default NULL,
created int(14) default NULL,
heading text,
body text,
hash varchar(32) default NULL,
author varchar(200) default NULL,
nbreads int(14) default NULL,
votes int(8) default NULL,
points int(14) default NULL,
type varchar(50) default NULL,
rating decimal(3,2) default NULL,
isfloat char(1) default NULL,
PRIMARY KEY (articleId),
KEY title (title),
KEY heading (heading(255)),
KEY body (body(255)),
KEY nbreads (nbreads),
KEY author (author(32)),
KEY topicId (topicId),
KEY publishDate (publishDate),
KEY expireDate (expireDate),
KEY type (type),
FULLTEXT KEY ft (title,heading,body)
) TYPE=MyISAM AUTO_INCREMENT=1
Message: Incorrect sub part key. The used key part isn't a string, the used length is longer than the key part or the storage engine doesn't support unique sub keys

and

Command: CREATE TABLE tiki_blogs (
blogId int(8) NOT NULL auto_increment,
created int(14) default NULL,
lastModif int(14) default NULL,
title varchar(200) default NULL,
description text,
user varchar(40) default NULL,
public char(1) default NULL,
posts int(8) default NULL,
maxPosts int(8) default NULL,
hits int(8) default NULL,
activity decimal(4,2) default NULL,
heading text,
use_find char(1) default NULL,
use_title char(1) default NULL,
add_date char(1) default NULL,
add_poster char(1) default NULL,
allow_comments char(1) default NULL,
show_avatar char(1) default NULL,
PRIMARY KEY (blogId),
KEY title (title),
KEY description (description(255)),
KEY hits (hits),
FULLTEXT KEY ft (title,description)
) TYPE=MyISAM AUTO_INCREMENT=1
Message: Specified key was too long. Max key length is 500

which ultimately cause:

Command: # --------------------------------------------------------
INSERT INTO tiki_modules (name,position,ord,cache_time,groups) VALUES ('login_box','r',1,0,'a:2:{i:0;s:10:"Registered";i:1;s:9:"Anonymous";}')
Message: Table 'tiki-19branch.tiki_modules' doesn't exist

because the table never gets created.
{CODE}
I'm not sure how to go about fixing this problem.

{syntax type="tiki" editor="plain"}
This follows extensive regression into InterTiki setup problems. There are 2 bugs in here, but they are likely related as they exhibit the same performance. I am unsure where the problem lies (someone familiar with the code could fix this in a heartbeat).

!Background
Both these apply to a fresh install of Tiki and getting InterTiki up and operational. I have replicated this bug on 2 different setups (2 different hosts).
# Tiki 3.0 beta 4
# Tiki 3.0 RC1

!!Server Setup Error
During initial server setup, as Tiki Admin, setting up the KnownHosts information. Typically, I would only setup one known host for demo purposes. However, in spite of tweaks, I kept seeing the InterTiki response error __Invalid Server Key__.

!!!Regression
I tracked through to code to the /remote.php validate function, around lines 58 or so. It seems like it always ended up inside the if clause (failing the validation).

Inserting
{CODE()}''print_r($prefs['known_hosts']);'' {CODE}
at the top of the validate function I received the following from the master:
{CODE()}
Array
( [0] => Array (
[name] => tiki2
[key] => mysecretkey
[ip] => 127.0.0.1
[contact] => mizraith )
)
{CODE}

!!!Explanation
No wonder it failed the test, as the if statement was indexing into "known_hosts" using the key.
{CODE()}
''!isset($prefs['known_hosts'][$key]) or $prefs['known_hosts'][$key]['ip'] != $tikilib->get_ip_address())''.
{CODE}

As you can see, the initial setup from within Tiki failed to properly key the database entry. The database entry has a key of [0].

Adding another "known_host" in the InterTiki admin shows correct behavior:
{CODE()}
Array
(
[0] => Array
(
[name] => tiki2
[key] => mysecretkey
[ip] => 127.0.0.1
[contact] => mizraith
)

[anotherkey] => Array
(
[name] => another
[key] => anotherkey
[ip] => 123.123.123.123
[contact] => mizraith
)

)
{CODE}

!!!Additional Regression
Editing that first Known Host in the InterTiki admin screen does not fix the key value. AFAIK, one has to __delete__ the first known host that is entered (throwaway). From then on, it seems to work.

!!Client Setup Error
Although I didn't recognize it at the time, I have seen this same error during client setup of InterTiki. In that process, admin must enter a Known_Server. The first server you enter in seems to go into the database with a key of [0], even though InterTiki will search on the server's key name.

{syntax type="tiki" editor="plain"}
'ziit_tikiwiki.tf.galleryId' isn't in GROUP BY

Die Abfrage war:
SELECT tab.* FROM ((SELECT 0 as `isgal`, tf.`fileId` as `id`, tf.`galleryId` as `parentId`, tf.`name`, tf.`description`, tf.`filesize` as `size`, tf.`created`, tf.`filename`, tf.`filetype` as `type`, tf.`user` as `creator`, tf.`author`, tf.`hits`, tf.`lastDownload`, tf.`votes`, tf.`points`, tf.`path`, tf.`reference_url`, tf.`is_reference`, tf.`hash`, tf.`search_data`, tf.`lastModif` as `lastModif`, tf.`lastModifUser` as `last_user`, tf.`lockedby`, tf.`comment`, tf.`deleteAfter`, tf.`maxhits`, tf.`archiveId`, '' as `visible`, '' as `public`, tf.`fileId`, tf.`galleryId`, tf.`filesize`, tf.`filetype`, tf.`user`, tf.`lastModifUser`, '' as `files`, count(tfh.`fileId`) as `nbArchives` FROM `tiki_files` as tf LEFT JOIN `tiki_files` tfh ON (tf.`fileId` = tfh.`archiveId`) WHERE tf.`archiveId`=0 AND tf.`galleryId`=? GROUP BY tf.`fileId`) UNION (SELECT 1 as `isgal`, tfg.`galleryId` as `id`, tfg.`parentId`, tfg.`name`, tfg.`description`, 0 as `size`, tfg.`created`, tfg.`name` as `filename`, tfg.`type`, tfg.`user` as `creator`, '' as `author`, tfg.`hits`, 0 as `lastDownload`, tfg.`votes`, tfg.`points`, '' as `path`, '' as `reference_url`, '' as `is_reference`, '' as `hash`, tfg.`name` as `search_data`, tfg.`lastModif` as `lastModif`, '' as `last_user`, '' as `lockedby`, '' as `comment`, '' as `deleteAfter`, '' as `maxhits`, 0 as `archiveId`, tfg.`visible`, tfg.`public`, tfg.`galleryId` as `fileId`, tfg.`parentId` as `galleryId`, 0 as `filesize`, tfg.`type` as `filetype`, tfg.`user`, '' as `lastModifUser`, count(distinct tfc.`fileId`) as `files`, 0 as `nbArchives` FROM `tiki_file_galleries` as tfg LEFT JOIN `tiki_files` tfc ON (tfg.`galleryId` = tfc.`galleryId`) WHERE 1=1 AND tfg.`parentId`=? GROUP BY tfg.`galleryId`)) as tab ORDER BY `isgal` desc

{syntax type="tiki" editor="plain"}
In tra.php (8.1) it is necessary to check if an entry exists, the function used is always "getOne".

Unfortunately the instruction used {CODE()}! $tikilib->getOne(....){CODE} seems to return always true and generated the crash.

{syntax type="tiki" editor="plain"}
(Not yet checked for trunk)

After running installer with upgrade we get the message "Invalid database run installer..."

Running installer don't changes anything to database, but the message is still displayed.
It is a consistency "deadlock by soft".

The lonely thing generated by installer is a reset which needs to reset manually the admin account and clear all caches and cookies (see #4066 admin login problem).

~~#090:!!!Going on 12/06/2011~~

I need to check the soft.

The message is sent by "installer" $installer instance of class installer in installib
It checks before the validation of patches on db using $installer->recordPatch($patch) for each one.
recordPatch function in installer records the patch into tiki_schema as done with his full date.

The concerned (got by a var_dump) patch is "20110904_shoutbox_def_tweetid_tiki"
is not into the tiki_schema table.
So the test functions, but the tiki-install failed to make this patch on another version OK, as it is defined.

__~~#F00:When it runs now (installer at 8.1 level) it don't tries to make the upgrade. This is the deadlock.
__What is done if an old patch is not there !!!__

More there is no report at all.~~__