I. First install (demo)

This first install paragraph explains you how to set up aGuppY web site with some demo content, so that you can play with it.

• Download the guppy.zip file (http://www.freeguppy.org) on your PC.

• Unzip this guppy.zip file in a directory of your PC with your favorite unzipping tool (WinZip, UltimateZip...).

• EXCELLENT, GuppY is ready to run !

• If you wish to play with GuppY on your PC before putting it on the Internet, install a webserver and PHP (you may also rather install a package like EasyPHP - http://www.easyphp.org)on your PC and copy the content of the directory where you unzipped guppy.zip in the www sub directory of EasyPHP, then launch EasyPHP... and your site will be running locally on your PC. It's just as easy as that !

• If you wish to install your web site directly on the Internet, then copy all unzipped files via FTP to your site with a simple FTP client software (IE, Netscape, CuteFTP, etc...). And that's all, you now just need to input the URL of your site in your browser to find yourself on your web site.

• Wonderful, you just installed GuppY successefully!

IMPORTANT NOTICE

-If you do not plan to prepare a new clean database, delete theinstall/ directory now. Otherwise anybody could run it on yourweb site and delete all the content on your web site!

ALTERNATIVE

Youcan also download EasyGuppY on the GuppY site. EasyGuppY is apackage made of a web server, PHP and GuppY, all packaged with anautomated install program for a PC with Windows. You just cannot doeasier than that !

.CHMOD

Here is how to set upfiles rights for web servers that require it (not all of them requireit).
1. Directory admin
- File admin/mdp.php :         rights = 666. UNIX command = chmod 666 admin/mdp.php
+ Directory admin/redac :     rights = 777. UNIX command = chmod 777 admin/redac
- Files admin/redac/* :         rights = 666. UNIX command = chmod 666 admin/redac/*
2. Directory data :                 rights = 777. UNIX command = chmod 777 data
- Files data/* :                         rights = 666. UNIX command = chmod 666 data/*
+ Directory data/archive :     rights = 777. UNIX command = chmod 777 data/archive
- Files data/archive/* :          rights = 666. UNIX command = chmod 666 data/archive/*
+ Directory data/cache :      rights = 777. UNIX command = chmod 777 data/cache
- Files data/cache/* :           rights = 666. UNIX command = chmod 666 data/cache/*
+ Directory data/countmsg : rights = 777. UNIX command = chmod 777 data/countmsg
- Files data/countmsg/* :  rights = 666. UNIX command = chmod 666 data/countmsg/*
+ Directory data/usermsg : rights = 777. UNIX command = chmod 777 data/usermsg
- Files data/usermsg/* :     rights = 666. UNIX command = chmod 666 data/usermsg/*
+ Directory data/error :         rights = 777. UNIX command = chmod 777 data/error
- Files data/error/* :             rights = 666. UNIX command = chmod 666 data/error/*
3. Directory file :                  rights = 777. UNIX command = chmod 777 file
- Files file/* :                         rights = 666. UNIX command = chmod 666 file/*
4. Directory img :                 rights = 777. UNIX command = chmod 777 img
- Files img/* :                       rights = 666. UNIX command = chmod 666 img/*
5. Directory pages :             rights = 777. UNIX command = chmod 777 pages
- Files pages/* :                   rights = 666. UNIX command = chmod 666 pages/*
6. Directory photo :             rights = 777. UNIX command = chmod 777 photo
- Files photo/* :                   rights = 666. UNIX command = chmod 666 photo/*

7. For all skins directories, it should be necessary to chmod the skin configuration files:
- skin/your_skin/confskin.inc : rights = 666. UNIX command = chmod 666 skin/your_skin/confskin.inc
- skin/your_skin/style.css :       rights = 666. UNIX command = chmod 666 skin/your_skin/style.css


How can you detect that you should execute these "CHMOD" ?Well, it is pretty easy to know, it is in the case you get many errormessages of this kind :

.htaccess notice

GuppY is shipped with a.htaccess file in the root directory. This file is only usefulif your web site runs with an Apache server (this is the case most ofthe time). Here is itsstructure:
--------------------------------------
<Files ~ "^.ht">
 Order allow,deny
 Deny from all
 Satisfy All
</Files>
<Files ~ "^.*.(inc|dtb">
 Order allow,deny
 Deny from all
 Satisfy All
</Files>
ErrorDocument 400 /error.php?err=400
ErrorDocument 401 /error.php?err=401
ErrorDocument 403 /error.php?err=403
ErrorDocument 404 /error.php?err=404
ErrorDocument 500 /error.php?err=500
--------------------------------------
Thefirst 5 lines are used to protect the content of your database fromhackers and other bad people (and there are some !). Otherwise, fileslike the data/frth.dtb file for example which holds all e-mailaddresses of the people who posted a message in the forum can be readand even help to enrich a Spam file (ugly !). These 5 lines are notto be modified.

The 5 following lines are used to direct usersto the error page when ask for a non existing page or other possibleerrors. These lines might require to be adapted (with a simple texteditor like Notepad or Wordpad for example) according to where youhave put your GuppY.

If you installed GuppY at the rool ofyour site (URL = http://www.yoursite.com/) then you have nothing todo. But if you installed it in a directory of your site (URL =http://www.yoursite.com/here/ for example) then you will have tomodify these 5 lines:
-------------------------------------------
ErrorDocument 400/here/error.php?err=400
ErrorDocument 401/here/error.php?err=401
ErrorDocument 403/here/error.php?err=403
ErrorDocument 404/here/error.php?err=404
ErrorDocument 500/here/error.php?err=500
-------------------------------------------

Insome cases, you might need to modify these 5 lines as follows (for awebsite having an URL like http://www.yoursite.com/) :
-------------------------------------------------------------
ErrorDocument400 http://www.yoursite.com/error.php?err=400
ErrorDocument 401http://www.yoursite.com/error.php?err=401
ErrorDocument 403http://www.yoursite.com/error.php?err=403
ErrorDocument 404http://www.yoursite.com/error.php?err=404
ErrorDocument 500http://www.yoursite.com/error.php?err=500
-------------------------------------------------------------

Or,if installed in the here/ subdir:
------------------------------------------------------------------
ErrorDocument400 http://www.yoursite.com/here/error.php?err=400
ErrorDocument401 http://www.yoursite.com/here/error.php?err=401
ErrorDocument403 http://www.yoursite.com/here/error.php?err=403
ErrorDocument404 http://www.yoursite.com/here/error.php?err=404
ErrorDocument500http://www.yoursite.com/here/error.php?err=500
------------------------------------------------------------------

Itwould also be wise to protect your directory by a user name andpassword within the .htaccess file. As the way of doing it isusually specific to your web host, please refer to its documentationon this topic.
For further information on how to protect your website with a .htaccess file, please refer to the official Apachedocumentation.

II. Clean install

The clean install is meant for when you want to erase the democontent and start with a brand new empty GuppY site.

Thestarting point is for this clean install is anywhere between thefirst install and anything you did with the demo content. It willerase all of the content but keep the current parameters made in thedifferent &quot;Config something&quot; admin areas.

• If your web site URL is http://www.mysite.com/ input the following URL in your browser : http://www.mysite.com/install/

• Follow instructions for a &quot;Clean install&quot;;.

• Wonderful, your web site is ready to run with your content !

III. Migrating from previous versionsMiniportail 1.7 or GuppY 2.4

• Back up all of your web site before going ahead.
  
  

• Run a &quot;DB integrity check&quot;. Make sure it finds no error or run it again.

• To Config site to activate the skin &quot;no_skin&quot;.

• Go to the management pages of your plugins to take off their icons from the heigher menu bar.

• Supprimez les fichiers contenus &agrave; la racine de votre site (/) sauf guppy.ico
  Conservez pr&eacute;cieusement les 5 r&eacute;pertoires : data/ ; file/ ; img/ ; pages/ et photo/ qu'il ne faut donc surtout pas les supprimer de votre site web.
  Suprimez les autres repertoires : admin/ ; inc/ ; install/ et mobile/ et tout leurs contenus y compris leurs sous-r&eacute;pertoires.
  (mobile/ est apparu avec la version 2.3)

• Copy the new directories and files from the latest version of GuppY (that is / ; admin/ ; flash/ ; inc/ ; install/ and mobile/ ; plugins/ et skins/ . ) as well as install/ and it's content.

• Si l'URL de votre site est http://www.mysite.com/ alors saisissez le texte suivant dans la barre d'adresse de votre navigateur : http://www.mysite.com/install/migrate17.php
  puis http://www.mysite.com/install/migrate18.php si vous &ecirc;tes en version < 1.7 de miniPortail. Ou bien ex&eacute;cutez http://www.mysite.com/install/migrate18.php si vous &ecirc;tes en version 1.7 de miniPortail.

• Check if the &quot;CHMOD&quot; notice (from paragraph #2) is required for your installation. This will be the case if you had to apply it for your previous miniPortail / GuppY installs/migrations.

• If your web site URL is http://www.mysite.com/ input the following URL in your browser : http://www.mysite.com/install/

• Follow instructions for a &quot;Migration&quot;;.

• Wonderful, you have just migrated to the latest version of GuppY.

• Some modifications in the GuppY parameters require you to check for &quot;General Config&quot;, &quot;Site Config&quot;, &quot;Home Config&quot;, &quot;Sections Config&quot;, &quot;Services Config&quot; and &quot;Boxes Config&quot;. You will also have to run a &quot;DB integrity check&quot; for updating the GuppY database indexes.

• Il vous reste &agrave; installer votre skin et vos plugins en vous assurant auparavant que vous disposez de versions compatibles avec la pr&eacute;sente version.

IV. Migrer d'une versionULTERIEURE &agrave; Miniportail 1.7 ou GuppY 2.4

IMPORTANT : the migration script isfor web sites running with miniPortail version 1.8 or later / GuppYversion 2.4 or later.

• Back up all of your web site before going ahead.
  
  

• Run a &quot;DB integrity check&quot;. Make sure it finds no error or run it again.

• Disactivate the skin and the plugins you are using

• To Config site to activate the skin &quot;no_skin&quot;.

• Go to the management pages of your plugins to take off their icons from the heigher menu bar.

• Go to Config boxes to take off lateral boxes.

• Supprimez les fichiers contenus &agrave; la racine de votre site (/) sauf guppy.ico
  Conservez pr&eacute;cieusement les 5 r&eacute;pertoires : data/ ; file/ ; img/ ; pages/ et photo/ qu'il ne faut donc surtout pas les supprimer de votre site web.
  Suprimez les autres repertoires : admin/ ; inc/ ; install/ ; mobile/ ; plugins/ et skins/ et tout leurs contenus y compris leurs sous-r&eacute;pertoires.
  (mobile/ est apparu avec la version 2.3 ; plugins/ est apparu avec la version 3.0 ; flash/ et skins/ avec la version 4.6)

• Copy the new directories and files from the latest version of GuppY (that is / ; admin/ ; flash/ ; inc/ ; install/ ; mobile/ ; plugins/ et skins/ . ) as well as install/ and it's content.

• Check if the &quot;CHMOD&quot; notice (from paragraph #2) is required for your installation. This will be the case if you had to apply it for your previous miniPortail / GuppY installs/migrations.

• If your web site URL is http://www.mysite.com/ input the following URL in your browser : http://www.mysite.com/install/

• Follow instructions for a &quot;Migration&quot;.

• Wonderful, you have just migrated to the latest version of GuppY.

• Some modifications in the GuppY parameters require you to check for &quot;General Config&quot;, &quot;Site Config&quot;, &quot;Home Config&quot;, &quot;Sections Config&quot;, &quot;Services Config&quot; and &quot;Boxes Config&quot;. You will also have to run a &quot;DB integrity check&quot; for updating the GuppY database indexes.

• Il vous reste &agrave; installer votre skin et vos plugins en vous assurant auparavant que vous disposez de versions compatibles avec la pr&eacute;sente version.

V. IMPORTANT NOTICES &agrave;prendre en compte pour toute installation ou mise &agrave; jour :

• Once you have finished install or migrating, make sure that all the files in the install/ directory were deleted. Otherwise anybody could run it on your web site and delete all the content on your web site !

• If you cannot see the install/ directory anymore, then it means that everything is fine. The same conclusion applies if the install/ directory still exists but is empty (you should the delete it by FTP, as your webhoster does not allow its deletion with PHP).

• After the migration, the admin password is reset to &quot;pass&quot;.

• Si vous avez rapatri&eacute; votre site en local ou inversement, ausit&ocirc;t le transfer effectue de modifier l'url de votre site dans indiqu&eacute; dans &quot;config g&eacute;n&eacute;ral&quot;, sinon vous pourriez rencontrer quelques messages d'&eacute;rreurs lors de l'&eacute;dition d'article.