BACK UP YOUR DATABASE BEFORE ANY UPGRADING!!!!!!!
BACK UP YOUR DATABASE BEFORE ANY UPGRADING!!!!!!!
BACK UP YOUR DATABASE BEFORE ANY UPGRADING!!!!!!!
BACK UP YOUR DATABASE BEFORE ANY UPGRADING!!!!!!!
BACK UP YOUR DATABASE BEFORE ANY UPGRADING!!!!!!!

Simple installation instructions (a help file for WIKINDX use is included in the system as a web page).

REQUIREMENTS:
1/  You must have the ability to create a database and grant permissions on a MySQL server.
2/  Write access to your web server's documents folder.
3/  (It is assumed you have a working MySQL database server and PHP-enabled web server.)
4/  Any operating system capable of running the above.
5/  Windows users wishing to run WIKINDX as a single user on a desktop machine, may be interested in the WAMP server which is a one-step install of Apache/PHP/MySQL.  Instructions can be found at http://wikindx.sourceforge.net/.

NB - WIKINDX will neither create the database nor grant appropriate permissions (GRANT ALL) - you must do this 
manually then edit config.php.  PHPMyAdmin users (for Windows users, this utility for managing MySQL databases comes with WAMP) can find instructions for this at http://wikindx.sourceforge.net/.

               ---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---
	       
INSTALLATION:
1/  Unpack and untar wikindx-xxxx.tar.gz or wikindx-xxxx.zip to a web server documents' folder of your choice.
	NB - It is important that the 'files/', 'attachments/' and 'styles/bibliography/' folders and the XML files within the 'styles/bibliography/xxx/' folders are writable by the web server user (usually 'nobody').  On *NIX, untar with the -p option to ensure that permissions are preserved (these permissions are 0777 to ensure that WIKINDX runs out of the box - you may wish to make them more secure).
2/  Edit config.php as per the instructions in that file.  If you have an existing v1.x database, see below and the file UPDATEWIKINDX.  If you have an existing v2.x database and wish to use that database with v3.1, then you should edit config.php to match that existing database.  The first time you run WIKINDX v3.1, the database will be automatically upgraded.  AS ALWAYS, YOU SHOULD BACK UP YOUR DATABASE FIRST.
3/  Run WIKINDX through your web browser and complete the instructions there to finish the installation.
4/  Have fun!

               ---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---

IF THINGS GO WRONG:
1/  Sometimes (usually on commercial ISPs installing over a slow network), the MySQL table creation and population scripts are not allowed to complete.  If removing the tables and attempting to run WIKINDX again does not fix it, try manually creating and populating the database tables through your favourite MySQL client (such as phpMyAdmin) by sending the MySQL server the file wikindx3/update/createMySQL.txt.

               ---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---

NOTE:
1/  If you have an existing WIKINDX v1.x database, you must install and configure WIKINDX v2.0.1 and then upgrade to and configure WIKINDX v3 as the database structure has significantly changed. If you still have such a database and wish to upgrade, please read the file UPDATEWIKINDX for important instructions.
2/  The files/ directory is used for the temporary storage of RTF, RIS, Endnote, BibTeX and other files for the user to download.  Directories are created within this folder based on the user's SESSION ID.  The scripts within WIKINDX will mark these directories and files for deletion after $WIKINDX_FILES_DELETE seconds have passed (see Admin|configure) since their last modification. This doesn't necessarily mean that they will be immediately deleted:  the files will be deleted the next time someone exports a file and empty directories the time after that.  Users of some operating systems (such as some Windows versions), should be aware of a well-known 'feature' of PHP's mkdir() function that stops the automatic deletion of such files and directories.  If this happens, WIKINDX quietly ignores any errors or warnings.  If you suspect this is happening, from time to time you should manually remove files and folders from the files/ directory.
3/  Language packs are available as separate downloads from the sourceforge site.  They act like plug-ins so simply 
extract them (with their directory structure) to the languages/ directory to make them instantly available.
4/  Bibliographic style packs are available as separate downloads from the sourceforge site.  They act like plug-ins so simply extract them (with their directory structure) to the styles/bibliography/ directory to make them instantly available.

               ---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---:::---
	       
The WIKINDX Team 2005
sirfragalot@users.sourceforge.net
