last changed : 01/24/10

• Perl version 5.004 and higher
• Perl modul CGI ( version 2.37 and higher, see CGI.pm Revision History for platform specific information )
• Perl modul FindBin
• Perl modul File::Copy
• Perl modul File::Path
• optional Perl modul Compress::Zlib version 1.06 or higher and Perl Modul Archive::Zip version 1.01 or higher
• optional Perl module Net::SMTP

efileman 7.1 is not compatible to any former versions of efileman, you should not place the files into the same directory as any previous installation of efileman !

Use the ef_check.cgi script contained in the efileman install package to find out more information about your account eg. the installed Perl modules, and whether your account is conform to installation requirements.

To install efileman follow the instructions below:

1. Extract the downloaded package with path names, open efileman.cgi file and validate the path info in the first line of the script!
   In most cases the path on a UNIX server is "#!/usr/bin/perl". For a MS Windows server it's mostly "#!C:/perl/bin". Ask your account administrator, if you are not sure. Don't use backslashes !
   You can rename efileman.cgi after this step to a name of your choice, eg. cp.cgi without any more change inside the script.
   If you don't work with a Unix System, and if you have trouble while reading the files with unix styled new line characters, test a text editor like proton or NoteTab Light. See also the FAQ.
2. Upload now all files with the same directory structure onto your server excepting the docs directory, which is not necessary to run efileman. The images/efileman directory should be placed outside the cgi-bin, because the directory is mostly not accessible by a browser.
3. Make efileman.cgi (or the respective renamed file) executable by changing the permissions to 755. This is not necessary on a Windows server system.
4. Start the cgi file immediately, because the first user will be able to configure the script. Don't upload and forget the script.
5. You will see the admin screen of efileman. Enter global values at first and save them by click on "Save and Continue". You will have a respective help text for every value.
6. Choose "New Account Defaults" in edit field and click on "Show Values" button.
7. Enter new account defaults and save them by click on "Save and Continue".
8. Choose "New User" in edit field and click on "Show Values" button.
9. Enter now the values for the first user as supervisor and save them.

You will automatically logged out at the next script action. Login again with your first user account data and complete the installation by adding more user if you want.
Finish the installation by adding a supervisor account in every case or remove the cgi file from server up to the time you are be able to complete the installation !
Change the "New Account Defaults" to values of your choice. You should at least disable supervisor and chmod permissions even you have "Enable Register" disabled.

The efileman script creates two subdirectories, logfile and usrfiles, during first save of configuration data, so you could have the following directory structure after installation (by default).

cgi-bin/efileman/efileman.cgi
cgi-bin/efileman/efileman_config.pm

cgi-bin/efileman/lang/english.pm

cgi-bin/efileman/module/admin.pm
cgi-bin/efileman/module/validate.pm
cgi-bin/efileman/module/manager.pm
cgi-bin/efileman/module/....pm

cgi-bin/efileman/skins/default/admin.skin
cgi-bin/efileman/skins/default/login.skin
cgi-bin/efileman/skins/default/manager.skin
cgi-bin/efileman/skins/default/.....skin

cgi-bin/efileman/logfile/

cgi-bin/efileman/usrfiles/

There should be available a "changed files only" or "cfo" archive. Download and extract this, edit and rename efileman.cgi according to your needs. This works only for the last release, compare the Release Notes in case of you are unsure. If no "cfo" file available, download the current version.
Start efileman now and disable user login by setting "Lock efileman login" in global admin security settings to Yes.
Upload all files onto your server (excepting efileman_config.pm !). You can overwrite the existing files, but there is no harm to have a second installed efileman and update the files there at first, to see whether it's still running.
Enter efileman admin mode immediately with a supervisor account, check the new parameter according release notes and save them.
Don't forget to set "Lock efileman login" back to No.

User who works under Apache::mod_perl, have to wait under some circumstances until the modules of former efileman version are unload from memory. It depends on Apache configuration. To contact the server admin could help to reduce wait time !