Category: Installer (profiles, upgrades and server-related issues)

I installed a tiki3.3 on a server ( pangea.org ) with no remarkable issues, and the tikis seem to work fine:
http://d-recerca.org


However, I attempted to install a spare tiki4.0 for testing on the same server, and I can't install it:
http://xavidp.pangea.org/tiki40/

I guess the server doesn't have pdo installed. I added the line in local.php to force tiki to use adodb instead (copied from tw.o forums, message from sylvie). With this change I can bo a bit further, but I cannot finish the installation proces. After the sql are run, I'm sent to the authentication page of tiki-install.php, instead of to the step of locking the installer and proceeding to tiki.

I went to the tiki-index.php then. and i could see it, and changed password for admin. But I can't login after that step neither with admin admin or with new admin pass..

This error was seen when using PHP4

Tiki should detect and provide better error message

Good:

Since Tiki4, in tiki-admin_include_sefurl.php, Tiki detects if .htaccess is there and if contains tiki-index.php?page=$1

But:
If Tiki is upgraded, by installing over, there may be issues because Tiki is still using the old .htaccess without informing tiki admin


Proposal:
Have Tiki version number in _htaccess (and thus updated as part of the release procedure)
Test on this, and inform users when they forgot to upgrade their .htaccess file.

The install script says to run the 1.8to1.9 SQL upgrade when upgrading from a 1.9.x to another 1.9.x release.

I have and error in that script while creating the tiki_score table, which is normal because it already exists. Then, I have a bunch of errors in the following INSERT statements because the category column is missing (along ith the desription and ordd columns). Here is the output of the failed statements:

CREATE TABLE tiki_score (
event varchar(40) NOT NULL default '',
score int(11) NOT NULL default '0',
expiration int(11) NOT NULL default '0',
category text NOT NULL,
description text NOT NULL,
ord int(11) NOT NULL default '0',
PRIMARY KEY (event),
KEY ord (ord)
) TYPE=MyISAM
Message: Table 'tiki_score' already exists


Command: INSERT INTO tiki_score (event,score,expiration,category,description,ord) VALUES ('login',1,0,'General','Login',1)
Message: Unknown column 'category' in 'field list'

.... other similar failed INSERT


Here is the tiki_score table definition that is currently in my 1.9.1 database (extracted from a mysqldump):
CREATE TABLE tiki_score (
event varchar(40) NOT NULL default '',
score int(11) NOT NULL default '0',
expiration int(11) NOT NULL default '0',
PRIMARY KEY (event)
) TYPE=MyISAM;

Upgrading a previous 1.10 site with current cvs code (from August 1st, 2007) I get, while using
tiki_1.9to1.10.sql with -f param from command line:

^
(...)
ERROR 1071 at line 561: Specified key was too long. Max key length is 500
ERROR 1071 at line 585: Specified key was too long. Max key length is 500
(...)
ERROR 1074 at line 620: Too big column length for column 'value' (max = 255). Use BLOB instead
ERROR 1074 at line 627: Too big column length for column 'fieldname' (max = 255). Use BLOB instead
(...)
^

Plus some:
{CODE(wrap=>1)}
(...)
ERROR 1064 at line 497: 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 'user(100),serverId,groupName(100))' at line 1
ERROR 1064 at line 500: 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 'user(150),pageName(100))' at line 1
ERROR 1064 at line 506: 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 'user(100),id(100))' at line 1
ERROR 1064 at line 509: 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 'user(100),event,object(50))' at line 1
ERROR 1064 at line 513: 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 'user(120),friend(120))' at line 1
(...)
ERROR 1064 at line 597: 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 'user(120))' at line 1
(...)
ERROR 1064 at line 638: 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 `fieldId` FROM `tiki_webmail_contacts_fields` WHERE `fie
(...)
{CODE}

Sylvieg, if you review this, you can see it your own at ourproject.org server, uniwiki project, updating uniwiki2 database (the one for http://uniwiki.ourproject.org ).

If Trackers had the "tracker template" feature, it would allow for better pre-made extended features for Tiki at install time.
In tw.o forums, some people requested like: address books (imagine with the same basic fields as Mozilla Thunderbird & Evolution, etc. address books, ... Export from you local program (through csv), and import to your address book in Tiki (through csv).

The same for "Offers & Demands (linked or linkable)", that many people/communities would like to use like "out of the box" feature. I do have that kind of trackers made (basic, but working for production already: http://valldelcorb.org/trackers - http://valldelcorb.org/Comparteix (1.9.x) or http://intercanvis.net (1.10.x) using tracker plugins in a general Wiki page).

Since duplicate tracker is already coded in 1.10, and templates concept already exists in Tiki, Tracker templates would be a nice MUST in the MID and LONG run.

Tracker templates should be selectable at install time (in the new installer devs. are thinking/designing -> ((Install)) ), or at a later stage through Mods, maybe?

This script does not work with http servers that run under UNcommon user ID/GID. There is one good http server example in the Debian repos called yaws where the script becomes a problem. yaws runs under user ID/GID yaws/yaws. If one attempts to run setup.sh with a yaws http server, the script does not work.

1.Clicking on "Admin mods" after installation returns this error.
You need to run setup.sh :
./setup.sh $APACHEUSER all
Common Apache users are www-data, apache or nobody

2. Going to the command line and running setup.sh yaws all (because the username/gid is yaws, not the usual) returns no messages when in fact the script has already decided that the user will be www-data because I'm on Debian. About line 27 of the script. if [ -f /etc/debian_version]; ....

There's no message that says how the ownership has been changed after running the script. There's no message saying the user has been chosen for me because I'm on Debian either. In both cases, I'd still have problems because the userID/GID needs to be yaws/yaws in order to make tikiwiki work right.

Perhaps another way to address the problem is to check and see who owns the server process with an lsof -p :portNumber?

Contributors