ezUserManager v1.3 (21. mar 2005)
-------------------
ezUserManager homepage: http://php.reinsveien.com/ezUserManager/

CONTENTS:
---------
1. System requirements
2. Copyright/license
3. Language files
4. Installation
5. How to protect files/folders
6. Revision history


1. SYSTEM REQIREMENTS
---------------------
PHP4
MySQL
Access to give writting permission on files.


2. COPYRIGHT/LICENSE
--------------------

Copyright 2004-2005 Sven-Ove Bjerkan. All rights reserved.

You are free to use this script for free i non-commercial use as long as you keep the "Powered By ezUserManager"-messages.

Use of this script by companies or on commercial web site requires a commercial
license. For commercial license details and costs, please visit: http://php.reinsveien.com/ezUserManager/donate.php

This script may be edited/changed as long as you don't remove any copyright
statements and "Powered By ezUserManager" messages. By using this script you agree to
take full responsibility for it. Sven-Ove Bjerkan will take no responibility for any
damage caused.

Reselling or distributing this code without prior written consent is expressly
forbidden.


3. LANGUAGE FILES
------------------
Look in "language-support.txt".


4. INSTALLATION
---------------

New installation:
	1. CHMOD the following files to 777 so that the script has writing-permission for it:
		a) Your .htpasswd-file
		b) config/form.config.php
		c) config/mysql.config.php
		d) config/general.config.php
	2. Create the table using ezUserManager.sql (remember to set table-name in it if you don't want to use 			   "ezusermanager")
	3. Add any extra field(s) you want in the table (remember the field-names, you'll need them later).
	4. Run admin/config.php in your browser and enter default password (letmein).
	5. Follow the configuration-wizard.
	6. See the "ezusermanager_update.php"-file located in the members-folder (preferably place it in a folder protected by 	.htaccess) and edit "$ezUserManager_Path" at the top of the script.
	This file makes it possible for users to update their registered info.

Then you are ready to go! :)

Upgrade from earlier version of ezUserManager:
It is advised to take a backup of all files first, just to be on the safe-side.
	1. CHMOD the following files to 777 so that the script has writing-permission for it:
		a) config/form.config.php
		b) config/mysql.config.php
		c) config/general.config.php
	2. Rename the admin/upgrade_1x_13_rename.php to admin/upgrade_1x_13.php.
	3. Run admin/upgrade_1x_13.php in your browser.
	4. Delete admin/upgrade_1x_13.php and ezusermanager_config.inc.php.
	5. Run admin/config.php in your browser and enter your password.
	6. Follow the configuration-wizard.

Then you are ready to go! :)

If you want to change the style/apperance of ezUserManager you may edit the "stylesheet.css"-file in the ezUserManager-folder.


5. HOW TO PROTECT FILES/FOLDERS
-------------------------------

a) Folders:
See if there is a file called .htaccess in the directory you want to protect. If it is append the following to it, if not create a new one containing the following: 
AuthUserFile /complete/path/to/ezusermanager/.htpasswd
AuthGroupFile /dev/null
AuthName "ezUserManager"
AuthType Basic

require valid-user

<Files .htaccess>
    order allow,deny
    deny from all
</Files>

Remember to replace the "/complete/path/to/ezusermanager/" with the correct path. Your host have this info.


b) Single files:
See if there is a file called .htaccess in the directory where the file you want to protect is located. If it is append the following to it, if not create a new one containing the following: 
<Files .htaccess>
    order allow,deny
    deny from all
</Files>

<Files filename.htm>
  AuthUserFile /complete/path/to/ezusermanager/.htpasswd
  AuthGroupFile /dev/null
  AuthName "ezUserManager"
  AuthType Basic

  require valid-user
</Files>

Remember to replace the "/complete/path/to/ezusermanager/" with the correct path. Your host have this info and the "filename.htm" with the filename you want to protect. 


6. REVISION HISTORY
-------------------
1.3     -   21th March, 2005
        -   See changelog.txt for details

1.2     -   10th January, 2005
        -   See changelog.txt for details

1.1     -   1th January, 2005
        -   See changelog.txt for details

1.0     -   14th December, 2004
        -   First release