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

The "enter tiki" buttons overlap now, after installing Tiki.

{img fileId="1343" thumb="box"}

{img fileId="1865" thumb="box"}

The label Database username + the placeholder Database username are redundant, we should keep only the placeholder. (same for Database password).

I installed a brand new Tiki24 from : 6188b548 · [REL] Closing 24.0 beta release · 16 hours ago
During the installation I set the name of my database as follow "bernardsfez_tiki24Debug"
In result I had the following error:

{img fileId="1729" thumb="box"}

I changed for "bernardsfez_tiki24debug" and it worked.

It is not stated in the online tooltip or in the installation that the database name MUST be lowercases only.
https://doc.tiki.org/Installation

I create a new Tiki 24 from git 6188b548 · [REL] Closing 24.0 beta release · 16 hours ago from scratch.
I created a duplicate database to install it with previous data.
Tiki successfully detect the database connection.
The installer didn't proposed me the usual choice (update or create).
I continued to check and ended with a database emptied and reseted.

This is a critical as new admin may not understand there is a problem here and proceed.

See the video here: {file type="gallery" fileId="1730" showicon="y"}

I retried with a different database and it was the same.

See second video here: {file type="gallery" fileId="1731" showicon="y"}

{syntax type="tiki" editor="plain"}
When I try to install on kop.bz hosted at unoeuro.com

I got the error below

Warning: tempnam() [function.tempnam]: Unable to access in /var/www/kop.bz/public_html/pjs/lib/init/initlib.php on line 135

Then I have this information
As a security precaution, the Tiki Installer has been disabled. To re-enable the installer:

There is no problem to install Tiki at my localhost

--------------------------
More information
PHP Version 5.2.13PHP Version 5.2.13


mysql

MySQL Support enabled
Active Persistent Links 0
Active Links 0
Client API version 4.1.18
MYSQL_MODULE_TYPE external
MYSQL_SOCKET /var/lib/mysql/mysql.sock
MYSQL_INCLUDE -I/usr/include/mysql
MYSQL_LIBS -L/usr/lib -lmysqlclient

Directive Local Value Master Value
mysql.allow_persistent On On
mysql.connect_timeout 60 60
mysql.default_host no value no value
mysql.default_password no value no value
mysql.default_port no value no value
mysql.default_socket no value no value
mysql.default_user no value no value
mysql.max_links Unlimited Unlimited
mysql.max_persistent Unlimited Unlimited
mysql.trace_mode Off Off

mysqli

MysqlI Support enabled
Client API library version 4.1.18
Client API header version 4.1.18
MYSQLI_SOCKET /var/lib/mysql/mysql.sock

Directive Local Value Master Value
mysqli.default_host no value no value
mysqli.default_port 3306 3306
mysqli.default_pw no value no value
mysqli.default_socket no value no value
mysqli.default_user no value no value
mysqli.max_links Unlimited Unlimited
mysqli.reconnect Off Off

Just installed fresh site, set the site title in installer but it didn't work and site displays default "Tiki 3.0" instead.

When doing a fresh install of branches/19.x via tiki-install.php UI: if the user selects MyISAM as the database engine of his choice instead of the default InnoDB, then after the last step where user chooses to lock the installer there is a system error instead of the screen to change the admin login on the -+tiki-change_password.php?user=admin&oldpass=admin&newuser=y+- (which is really a shame):
{CODE()}
An error occurred while performing the request.

Things to check:

Did you complete the Tiki Installer?

Is your database corrupt? Please see how to repair your database

Are your database settings accurate? (username, schema name, etc in db/local.php)

Please see the documentation for more information.
{CODE}

See https://screenshots.firefox.com/AZAjqNbyHSzadvdJ/demo.luciash.eu

With InnoDB the same process works nicely and the user is welcomed with the admin login password change.

__Did anybody test this? How come the unit tests did not catch it?__

THE PROBLEM
Tiki15 Beta installer fails, stating:

__Zend\I18n\Filter component requires the intl PHP extension__

__Check tiki-check.php to ensure your system is ready for Tiki or refer to https://doc.tiki.org/Requirements for more information."__


HOW I TRIED TO RESOLVE IT
1) I followed the on screen suggestion to run tiki-check.php. This showed me that "intl" was "BAD" and that "intl extension is required for Tiki 15 onwards."

2) I then followed the on screen suggestion to read the documentation at "https://doc.tiki.org/Requirements". However this documentation gave no specific information on the difficulty I was experiencing.

^The instructions on screen told me:
With FTP access:
a) Change the permissions (chmod) of the directories to 777.
b) Create any missing directories
c) Execute the Tiki installer again (Once you have executed these commands, this message will disappear!)^

3) First I changed the permissions of the directories to 777. It was not clear which directories should be created, or where they should be created, so I skipped the second step. I then executed the Tiki installer again. However, exactly the same error was encountered.

4) I did some further searches and I finally managed to find a reference to this specific problem at: https://dev.tiki.org/zf1-to-zf2. The information provided at this location suggested various methods to make a change to "php.ini". I found this information difficult to understand.

5) After a lot of research I found that "php.ini" was located on the server. However, my server provider would not permit my request to make changes to "php.ini" since they said it would affect other users of the server.

Therefore, as I understand it, my only option to run Tiki15Beta is to:
a) setup my own server
b) use cloud hosting
c) find another service provider who will allow me shell access to "php.ini"


PROBLEM
The onscreen instructions in the Tiki15Beta installer do not provide an effective explanation of, or solution for, the problem: requiring the "intl PHP extension".

The only fix I found, located at https://dev.tiki.org/zf1-to-zf2, was:
a) hard to find the information
b) prohibitively hard to understand the information
c) required shell access to the server

I EXPECTED
a) Not to encounter the need for "intl PHP extension"
b) Clear on screen information as to how to apply any suggested fix.
c) The on screen information should provide an __effective__ fix.
d) The fix should not be restricted to those with shell access to their server.

webwoven
(Thomas)

Installer is broken on 4.1 in Windows 2008 R2 with the environment described below. At least two of us have exactly the same problem, so the issue is not local to us.

At the bottom is someone else's description as taken off the Installer forum. My experience is exactly the same, except I am running MySQL 5.1.41 instead of 5.1.42.

A third party suggested it has something to do with directory or session permissions, or PHP configs. To test this, I uninstalled tw 4.1 and installed 3.4 in the same environment. 3.4 worked just fine. Then I upgraded to 4.1 over top of it and it reverted to previous bad behavior. So I believe it is a 4.x bug.

I've given this a high priority because the software is unusable if you can't install it, so you probably losing a lot of users.

Here's the other guy's description of the problem:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I am trying to preform a fresh install of TW4.1 on Windows Server 08 R2, IIS 7.5, PHP 5.2.12 and MySQL 5.1.42. However, after filling in the page for the database information to populate the database, I reach a page entitled

__Tiki Installer Security Precaution__

You are attempting to run the Tiki Installer. For your protection, this installer can be used only by a site administrator.

To verify that you are a site administrator, enter your database credentials (database username and password) here.

If you have forgotten your database credentials, find the directory where you have unpacked your Tiki and have a look inside the db folder into the local.php file.

I enter the 'root' account information and hit 'Validate and Continue'. But it takes me back to the 'Welcome' page. Now any link I hit Takes me to the validation page and I enter the correct user (root) account info and I'm sent back to the 'Welcome' page. The install doesn't want to continue.

If you want, check out www.nerdzone.net to see the site.

This shows the World we are keeping up to date, and help with troubleshooting if a bug is discovered

* For major versions (ex.: 17.0): since last minor version of previous branch (16.3)
* For minor versions (ex.: 17.2): since previous minor version of same branch (17.1)
* Would be slick to have a chart like the following for all dependencies, like the "Package" table at https://distrowatch.com/table.php?distribution=clearos

I think what's needed is a Gallery of "Tiki Sites in a Box". In other words, Tiki sites that are preconfigured to meet a particular kind of needs. The needs should be defined not in terms of features, but in terms of GOALS of the end user or organisation.

This could be a list of descriptions like this:

- I want a site to enable collaboration inside my organisation.
- I want a site to broadcast my ideas to the world and allow people to add to them and comment on them.
- I want a site that will act as an open knowledge base on a particular topic.
- etc...

Each of these could point to an example which would be a "fake" site that could act as a sandbox. People could go to this fake site, play around with it (but not reconfigure it), to see if it's what they are looking for.

This would allow easy single click configuration of Tiki. The user would simply click on one of the items in the Gallery, and the Tiki site would be configured accordingly.

One issue is: what happens if the user choose wrong and later wants to switch to a different model? I guess if no content has been created in the site it's fine, but what if content has already been created and that content is somewhat incompatible with the new model that the user is choosing?


Related:
*[tiki-view_tracker_item.php?itemId=1513|OpenSourceCMS type demo to test/develop and show off profiles]
*[http://info.tikiwiki.org/Use+Cases|Use Cases]

__Moving discussion of this wish to ((Profile Manager))__

I tried to install a Tiki21.x from git.
I could complete the composer installation on local and remote.

Both stop at the same point (waiting and pressing enter didn't help this time ?)

{CODE()}
-n Your choice [c]?
c
Local PHP version 74 >= to required PHP version 72 - good
You are running composer as "root", while "/Users/bernardsfez/.composer" is owned by "bernardsfez"
Warning: You forced the install of 1.10.26 via --1, but 2.5.4 is the latest stable version. Updating to it via composer self-update --stable is recommended.
You are already using composer version 1.10.26 (1.x channel).
Do not run Composer as root/super user! See https://getcomposer.org/root for details
You are using Composer 1 which is deprecated. You should upgrade to Composer 2, see https://blog.packagist.com/deprecating-composer-1-support/
Could not scan for classes inside "vendor/h5p/h5p-core" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/h5p/h5p-editor" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/pear/xml_rpc" which does not appear to be a file nor a folder
Could not scan for classes inside "vendor/smarty/smarty/libs/sysplugins/smarty_security.php" which does not appear to be a file nor a folder
Gathering patches from patch file.
Removing package adodb/adodb-php so that it can be re-installed and re-patched.
- Removing adodb/adodb-php (v5.22.2)
> Tiki\Composer\RestoreVendors::restore
> Tiki\Composer\CleanVendorAfterVendorBundledMigration::cleanLinks
Loading composer repositories with package information
Installing dependencies from lock file
Package operations: 203 installs, 0 updates, 0 removals
Gathering patches from patch file.
Gathering patches for dependencies. This might take a minute.
- Installing adodb/adodb-php (v5.22.2): Downloading (100%)
- Applying patches for adodb/adodb-php
../installer/composer-patches/adodb-php__remove_references_to_adodb_extension.patch (Remove references to ADOdb Extension)

{CODE}

I upgraded a Tiki from 24 to 25 after completing the installation I landed on the homepage with errors displayed :
-+Field searchable does not exist in the current index. If this is a tracker field, the proper syntax is tracker_field_searchable.+-
And many -+No results for query.+-

While this is normal, as I didn't ran the index:rebuild command, this is not very elegant and can be improved;

First, in such case a message with a link should be displayed about completing an action and not a page full of errors as that doesn't look good.

When the unified-index doesn't exist a modal warning over the page "Tiki detected that..." with an invitation to action "for your Tiki to work properly you must run rebuild command". If you have a small database you can run it from here else please use console.php.
A option to close the modal (admin choice to continue) and display the page.

Ideally the installer should automatically do such operation.
One difficulty is that we don't want run from the HTML the index:rebuild command to run on a large database as there are chances of timeout.

Tiki could suggest at the end of the installation process;
"You upgraded, before entering your new/upgraded Tiki you must run the index:rebuild command"

If possible a database size detection and offering suggestion;
"The Tiki installer script detected that your database size is: nnn"
We recommend:
* Small database => rebuild the index now
* Medium database => rebuild the index now
* Large database => rebuild the index using console.php

If the database size detection is not possible or too complicate (it may depend of server OS ?) we can simply give recommendation and offer to run the command for the user or suggest him to do it using console.php.

I installed a Tiki24 Alpha and it showed in the admin control panel the right VCS version (24.0 Alpha)
I then use the same installation with an existing database (update from a Tiki23) and now it show now VCS 23.2.

The version information should be updated accordingly to the Tiki version used.
{img fileId="1716" thumb="box"}
{img fileId="1715" thumb="box"}

tiki-install.php reports that memory_limit is not set, when in fact it is set incorrectly

Problem observed on platform: SuSE 10.0, PHP 4.4.0, Apache 2.0.52 (installed with OS)

Steps to re-create:
1. Leave memory_limit at the default value, 8M. in /etc/php.ini
2. Run phpinfo(), verify that memory limit is set to 8m
3. Run the following script, verify that memory_limit is set to 8M.
<?
echo 'memory_limit='.ini_get('memory_limit');
?>

4. Run tiki-install.php. Memory Limit check will report "green" and state that memory limit has not been set.

http://sourceforge.net/p/tikiwiki/code/47487/
was reverted by:
http://sourceforge.net/p/tikiwiki/code/48265/

But we would want this in Tiki Check standalone

The installer supports a hardcoded maximum of 16 characters for the database username, while the database name itself is unrestricted in length.

This causes trouble in some when not most environments, especially hosting.
Most panels use a prefix for database user & name so a restriction in length can fastly cause trouble.

For example my company uses plesk and we have resellers that set the prefix of database-name / -user to a string with more than 16 characters, leaving no place for the actual "name". Also some customers set their "name" part to some lengthy strings. This already causes troubles on installation with tikiwiki through the installer.

There is text in tiki-install.php that is in english without tag or option to translate it.

{CODE()} $title = 'Tiki Installer Security Precaution';
$content = '
<p style="margin-top: 24px;">You are attempting to run the Tiki Installer. For your protection, this installer can be used only by a site administrator.</p>
<p>To verify that you are a site administrator, enter your <strong><em>database</em></strong> credentials (database username and password) here.</p>
<p>If you have forgotten your database credentials, find the directory where you have unpacked your Tiki and have a look inside the <strong><code>db</code></strong> folder into the <strong><code>local.php</code></strong> file.</p>
{CODE}

Would be nice to have this working as the rest of Tiki

Using tiki 2.1
I login to tiki-install.php as admin, and I see this error message:

Fatal error: Cannot redeclare extracttoppath() (previously declared in /home/httpd/tiki110/db/local.php:64) in /home/httpd/tiki110/db/local.php on line 67


We are using a multitiki in subdirectories
Example:
http://moviments.net/cursos

&

http://moviments.net/ilp

share the same multitiki installation

This occured during ReleaseProcess192
Check and fix, if real - perhaps dependant on ./setup.sh

If install script fails (for some reason), we should at least let user proceed with manual installation.

tiki-install.php spits out many "variable undefined" errors (they are not critical; Tiki will install and work fine).



note: someone please confirm with more details on this.

Like many web applications, to install TikiWiki, you need to have already created your database (via phpMyAdmin or cPanel).

Maybe TikiWiki could handle this task using the mysql root/super user account?


Otherwise, maybe try via cPanel API if available (TRIM as well could try this)

Below is an example in 11.x but problem remains in 12.x No need to fix in 11.x, only 12.x and trunk (which should happen via auto-merge).

This section should be kept for upgrades of course :-)
{img fileId="659"}

Using a fresh checkout of r15460, and a clean database, install script reports:

Success Installation operations executed successfully: 1164 SQL queries.

Operations failed: 1 SQL queries.

SELECT patch_name FROM tiki_schema
Table 'tikiwiki3.tiki_schema' doesn't exist