Loading...
 
Skip to main content

Architecture / Installation

Forum List Topic List

Forums » Architecture / Installation » Install stops after just 3 tables added
 
Thread actions
Print this page
  • Print all pages

    • Install stops after just 3 tables added

    Posted by nickfx posts: 7

    I'm attempting to install tikiwiki-2.0 on a MacG5 running leopard, but the installation comes to a halt without producing an obvious error after creating only 3 tables in the database.

    Mac G5
    OS X 10.5.5 (clean install)
    Apache 2.2.9
    Php 5.2.6
    PostgreSQL 8.3.3

    PostgreSQL, Apache and PHP were all installed from source.

    The PHP installed starts out fine.
    I get past the db authentication info to the "Welcome to the installation script!" page.
    After choosing Default installation profile, and clicking install ... the page comes back blank after only a brief time (few seconds).

    One note is that I did alter the list_tables procedure in php-install to execute "select tablename from pg_tables" since the original "show tables" command didn't work with postgres.

    After install stops, the only tables that have been added to the database are:
    tiki_dynamic_variables
    tiki_minichat
    tiki_pages_chages

    Any thoughts and/or recommendations as to how to troubleshoot and correct this?

    Thanks in advance for any ideas.

    Reads: 824
    Posted by nickfx posts: 7

    Even just suggestions as to a log file or link to a page with any kind helpful hints would be wonderful really.
    So far I haven't managed to work out where to even begin.

    Anyone know which file(s) have the scripts that build out the initial database?

    Thanks again for any attempts to help. 😊


    Posted by nickfx posts: 7

    So... just as an experiment, I went ahead and downloaded and installed tikiwiki-1.9.11
    This install ran smoothly with no errors, so I guess I'll move forward on the older version for now.
    Would be nice to know what happened to make the current rev non-functional on this setup.


    Posted by Mike posts: 28 United States

    Can you check your web site's error log or the sql log to see what it didn't like?

    The file you are looking for is db/tiki-2.0-pgsql.sql I believe.

    Mike.


    Posted by nickfx posts: 7

    Looks like the problem is that "ENGINE=MyISAM" is added to the end of almost all the CREATE TABLE commands.
    Removing this from the CREATE TABLE commands gets the install much further, all the tables seem to have been created, but the install still stops at some point after that ending in a blank page.

    Has anyone tested this install on PostgreSQL? Anyone got it working?
    Do I need to install or activate some option for PostgreSQL?

    (BTW... I've re-tried now using Tiki 2.1 .. same results)


    Posted by nickfx posts: 7

    OK ... in my initial Find/Replace I hadn't cleared out all the "ENGINE=MyISAM" instances in the pgsql.sql file.
    Still there are quite a few syntax issues in the create table commands ... most seem to be involved with how many of the keys are declared as well as some field datatype issues.

    Seems like this script has become very MySQL centric, with a number of PostgreSQL computability issues.

    Again ... has anyone else installed/tested this on PostgreSQL?
    If not ... is PostgreSQL support still something that the TikiWiki project is planning on sticking with?
    Maybe I'm just missing some options/flags/module settings in my PostgreSQL install?


    Posted by nickfx posts: 7

    An interesting note is that the code in tiki-pgsql.sql has significant changes in many places that are not being documented. The CREATE TABLE command for tiki_history for example is commented that the Last Update was in 2005 ... but in fact the code block is different than the same block from tiki v1.9.11.

    Also interesting about the changes to this particular code block is that it adds two indexes. One is properly coded for PostgreSQL (CREATE INDEX command to create an index on the "user" field) while the other index is embedded in the CREATE TABLE command as "KEY(historyid)" .... which is not compatible with PgSQL.
    Neither of these indexes were part of the code block in the 1.9 version of this file.