############################################################################
#
# filechucker_prefs.cgi - user preferences file for FileChucker.
# Edit the settings in this file to customize FileChucker for your needs.
#
############################################################################
#
# PREFs Table of Contents:
#
# PREFs Section 01: Debugging.
# PREFs Section 02: Paths and Directories.
#
#   *Note: stop here and get the script running before customizing anything else.
#
# PREFs Section 03: Security.
# PREFs Section 04: User-directories.
# PREFs Section 05: Subdirectories.
#
#   *Note: User-directories and subdirectories are two separate things.
#
# PREFs Section 06: Email Notification.
# PREFs Section 07: Upload Form Configuration.
# PREFs Section 08: Upload Restrictions.
# PREFs Section 09: Processing Uploads.
# PREFs Section 10: Post-Upload.
# PREFs Section 11: File-List Configuration.
# PREFs Section 12: Database Setup.
# PREFs Section Z:  Misc Settings Not Usually Needed.
#
############################################################################








# PREFs Section 01: Debugging.
############################################################################
# The enable_debug PREF prints some debugging output in an HTML comment at
# the bottom of the page, if you pass "debug" as the query-string.  And the
# show_errors_in_browser PREF causes any fatal errors to be printed right in
# the browser, in addition to in your server's error log.  Enable both of
# these until you get FileChucker working properly, then disable them.
#
$PREF{enable_debug}					= 'no';
$PREF{show_errors_in_browser}				= 'yes';









# PREFs Section 02: Paths and Directories.
############################################################################
# We'll detect your server's document-root automatically, but on some
# servers you may need to uncomment this and specify it manually.  IIS users
# may need to set it like this:
#
#	$PREF{DOCROOT} = 'c:\inetpub\wwwroot';
#
#$PREF{DOCROOT}						= $ENV{DOCUMENT_ROOT};



# PREFs Section 02: Paths and Directories.
############################################################################
# This is where the uploaded files will go.  It must be world-readable
# and world-writable, aka "chmod a+rwx" or "chmod 0777".
#
# On most servers this will be in the DOCROOT, in which case we'll prepend
# your DOCROOT to whatever you set uploaded_files_dir to.  If for some
# reason you want to specify it with an absolute path, or a path that's
# relative to the current directory instead of the DOCROOT, then set the 
# _is_in_docroot PREF to no.
#
# And by default you should put the images (file/folder icons, logos, some
# rounded corners, etc, from filechucker-images.zip on the FileChucker web
# page) in the /upload/ directory, but you can adjust that too.
#
$PREF{uploaded_files_dir}				= '/upload/files';
$PREF{uploaded_files_dir_is_in_docroot}			= 'yes';
$PREF{path_to_filelist_images}				= '/upload/';



# PREFs Section 02: Paths and Directories.
############################################################################
# If you set uploaded_files_dir to a path outside your webspace, then we 
# won't be able to directly link to the files from your website, because
# they aren't in the DOCROOT.  If you're doing something like manually
# moving the files to somewhere else within your DOCROOT afterwards, then 
# enter that path here.  Otherwise just leave this commented out.  Note:
# don't include an ending slash on this.
#
#$PREF{uploaded_files_urlpath}				= '';



# PREFs Section 02: Paths and Directories.
############################################################################
# This is where datafiles (which are temporary: only needed while a given
# upload is in progress) are stored.  This must be world-readable and
# world-writable.  By default, we set its _in_docroot PREF to 'no' because
# by default the data directory gets placed at the same location as the
# filechucker.cgi script itself, so we don't need to prepend the value of
# DOCROOT onto it; we can access it directly since it's in the same dir
# we're running in.  The default settings are:
#
#	$PREF{datadir}			= 'fcdata';
#	$PREF{datadir_is_in_docroot}	= 'no';
#
# Alternatively you can set it with an absolute path, like this:
#
#	$PREF{datadir}			= '/var/www/mysite.com/cgi-bin/fcdata';
#	$PREF{datadir_is_in_docroot}	= 'no';
#
# Or this:
#
#	$PREF{datadir}			= 'c:\inetpub\wwwroot\cgi-bin\fcdata';
#	$PREF{datadir_is_in_docroot}	= 'no';
#
$PREF{datadir}						= 'fcdata';
$PREF{datadir_is_in_docroot}				= 'no';



# PREFs Section 02: Paths and Directories.
############################################################################
# The logfiles are just used during each upload, to keep track of how much 
# data has been sent, how much time has elapsed, etc.  They aren't used at 
# all after an upload has completed, so you probably want them deleted right
# away.  Note that these are different from the info-files which contain a
# permanent record of the upload including info like who uploaded what, the
# uploader's IP, date/time, etc.
#
$PREF{delete_logfiles_immediately}			= 'yes';



# PREFs Section 02: Paths and Directories.
############################################################################
# If you want to access FileChucker at a short URL like yoursite.com/upload/
# instead of yoursite.com/cgi-bin/filechucker.cgi, then you can do the 
# following:
#
# If you're using SSI (Apache and IIS both support this), then put the 
# following line into /upload/index.shtml on your server:
#
#	<!--#include virtual="/cgi-bin/filechucker.cgi?$QUERY_STRING" -->
#
# Or if your server runs PHP, you can put the following line into 
# /upload/index.php on your server:
#
#	<?PHP virtual("/cgi-bin/filechucker.cgi"); ?>
#
# Then set the 'here_' PREFs like this:
#
#	$PREF{here_uploader} = '/upload/';
#	$PREF{here_filelist} = '/upload/';
#	...
#
# Otherwise leave these set to $ENV{SCRIPT_NAME}.
#
# Note that in most cases these should all be set to the same value, i.e.
# unless you've actually set up multiple short URLs to point to the CGI
# script.  And if you only set the single $PREF{here} value, then the
# others will automatically be set to that value.
#
$PREF{here}						= $ENV{SCRIPT_NAME};
#$PREF{here_uploader}					= $ENV{SCRIPT_NAME};
#$PREF{here_uploadcomplete}				= $ENV{SCRIPT_NAME};
#$PREF{here_filelist}					= $ENV{SCRIPT_NAME};
#$PREF{here_login}					= $ENV{SCRIPT_NAME};
#$PREF{here_errorpage}					= $ENV{SCRIPT_NAME};









# PREFs Section 03: Security.
############################################################################
# Password Protection, Option 1 of 4 (simple; no usernames):
#
# If you want to require just a password (without a username) for
# access to the uploader and/or the list of uploaded files, then you
# can set these hashes.  Go to:
#
#	yoursite.com/cgi-bin/filechucker.cgi?newpw
#
# ...enter the password you want to use into that page, and it
# will generate a "hash" of the password, which is a string that
# looks something like this:
#
#	cdfc81932491375c34c842bcebc7dc15
#
# Copy and paste the hash into one of the following preferences.
# Then when you want to log in, enter the password, not the hash.
# (This is so that we don't store the actual password on disk, which
# would be very insecure.)
#
# We specify two possible user-levels (or "groups"): member and admin.
# (Actually, there are three, including "public" which obviously has no
# password.)  If you want, you can use just one of them, and have a
# single password for both uploading and viewing the file-list.  Or you
# can specify both, and set the "groups_allowed_to" preferences
# accordingly, so that only the admin can view the uploaded files.  Or
# vice-versa.  Or you could require no password to view the file-list,
# but require one to upload.  Etc, etc.  Just set the prefs accordingly.
#
# Note that the admin is automatically a "member" too, so someone 
# with the admin password automatically has access to anything that
# requires the member password.
#
$PREF{member_password_hash}				= '';
$PREF{admin_password_hash}				= '1ba86cf7548z891f32db68c362c544b1';



# PREFs Section 03: Security.
############################################################################
# Password Protection, Option 2 of 4 (full-featured; unlimited usernames):
#
# If you need a full-featured login system (with unlimited usernames, each 
# having its own password, and unlimited groups), instead of FileChucker's
# simple built-in password system which has just 2 passwords and no
# usernames, then you may want to use our UserBase application:
#
#	http://encodable.com/userbase/
#
# FileChucker integrates fully with UserBase, and if you set the PREF
# "enable_userdirs" below, then each of your users will have their own 
# private upload subdirectory.
#
# To use FileChucker with UserBase, you must configure FileChucker's
# database settings in PREFs Section 12.
#
# You must specify the URLs to UserBase on your server.  Note that these
# are not full filesystem paths; they are within your server's DOCROOT.
# The default values are:
#
#	$PREF{logout_url}	= '/cgi-bin/userbase.cgi?logout';
#	$PREF{login_url}	= '/login/';
#
# If you don't have the nice short /login/ URL set up on your server
# (see UserBase homepage for instructions), then just set the login_url
# value to the full path to the userbase.cgi file.
#
$PREF{integrate_with_userbase}				= 'no';
$PREF{logout_url}					= '/cgi-bin/userbase.cgi?logout';
$PREF{userbase_login_error_title}			= "Authentication Required";
$PREF{userbase_login_error_message}			= "Please %%login_link%% first.";
# The rest of these must be set to the same values as in userbase.cgi:
$PREF{user_table_name}					= 'ub_users_trl';
$PREF{group_table_name}					= 'ub_groups_trl';
$PREF{login_url}					= '/cgi-bin/userbase.cgi';
$PREF{max_username_length}				= 30;
$PREF{max_groupname_length}				= 30;
$PREF{max_hashedpw_length}				= 50;
$PREF{public_group_name}				= 'public';
$PREF{member_group_name}				= 'member';
$PREF{admin_group_name}					= 'admin';
$PREF{idle_timeout}					= 0; # in seconds; zero to disable.
$PREF{enable_ip_address_restriction}			= 'yes';
$PREF{force_ip_address_restriction}			= 'no';



# PREFs Section 03: Security.
############################################################################
# Password Protection, Option 3 of 4 (use your site's existing login system):
#
# If your site already has a cookie-based login system, then you can set
# these PREFs to make FileChucker integrate with it.  FileChucker will use
# the existence of the cookies specified here as confirmation that a user is
# logged in to your site.  Note that this option is mutually exclusive with
# the integrate_with_userbase option.
#
$PREF{integrate_with_existing_login_system}		= 'no';
$PREF{login_error_title}				= "Error: not logged in";
$PREF{login_error_message}				= qq`Perhaps you need to <a href="/">go home</a> and log in first?`;
$PREF{member_username_cookie_name}			= 'member_username';
$PREF{admin_username_cookie_name}			= 'admin_username';
#$PREF{logout_url}					= '/logout/';
#$PREF{login_url}					= '/login/';



# PREFs Section 03: Security.
############################################################################
# (Pseudo-)Password Protection, Option 4 of 4 (automatic private directories):
#
# You can enable this serial_is_userdir option to get much of the benefit
# of usernames & passwords without actually having to use usernames or
# passwords.  When configured this way, FileChucker will automatically put
# each new upload into a new unique private subdirectory, something like:
#
#	yoursite.com/upload/?userdir=11832920981234098203458234098123
#
# This is primarily meant to facilitate single-use uploads, for instance
# where a person just wants to share one file one time; however by using
# the link provided at the end of the upload and in the notification email,
# the user can actually reuse the same uploads folder for as long as he wishes.
#
# In order to configure FileChucker this way, in addition to setting this
# serial_is_userdir PREF, you should also find & set the following:
#
#	$PREF{keep_userdir_on_url}		= 'yes';
#	$PREF{enable_userdir_on_url}		= 'yes';
#	$PREF{enable_userdirs}			= 'yes';
#	$PREF{auto_create_userdirs}		= 'yes';
#	$PREF{groups_allowed_to_upload}		= 'public';
#	$PREF{groups_allowed_to_list_files}	= 'public';
#	$PREF{groups_allowed_to_download}	= 'public';
#	$PREF{groups_allowed_to_delete_items}	= 'public';
#	$PREF{hide_path_to_uploads_dir}		= 'yes';
#	$PREF{enable_subdirs}			= 'no';
#
#	$PREF{send_email_notifications}		= 'yes';
#	$PREF{email_notification_recipient_1}	= 'webmaster@yoursite.com';
#	$PREF{sender_email_address}		= 'filechucker@yoursite.com';
#	$PREF{email_subject}			= 'New upload on yoursite.com';
#
#	$PREF{formfield_01}			= 'Sender Email Address:';
#	$PREF{formfield_01_email}		= 'yes';
#
#	$PREF{formfield_02}			= 'Recipient Email Address:';
#	$PREF{formfield_02_email}		= 'yes';
#
# If you'd rather not go through all the PREFs trying to find those, you
# may want to just set them in a separate PREFs file as explained at the
# top of the PREFs section.
#
$PREF{serial_is_userdir}				= 'no';



# PREFs Section 03: Security.
############################################################################
# Whether you're using UserBase or FileChucker's built-in password system,
# the following "groups_allowed_to_*" PREFs control who can access what.
# Each item must be set to a comma-separated list of group names.  If you're
# not using UserBase, then the only possible groupnames are public, member,
# and admin.  Note that public includes member and admin (i.e. members and
# administrators are also members of the public), and member includes admin
# (i.e. administrators are also members).
#
# If you are customizing FileChucker by modifying its internal code, and you
# want to add your own restricted actions here, see the user_is_allowed_to()
# function, and search the script for calls to that function, to see how the
# system works.
#
$PREF{groups_allowed_to_upload}				= 'public';
$PREF{groups_allowed_to_list_files}			= 'public';
$PREF{groups_allowed_to_download}			= 'public';
$PREF{groups_allowed_to_view_upload_info}		= 'public';
$PREF{groups_allowed_to_move_items}			= 'public';
$PREF{groups_allowed_to_delete_items}			= 'public';
$PREF{groups_allowed_to_replace_existing_files}		= 'public';
$PREF{groups_allowed_to_reprocess_existing_files}	= 'public';
$PREF{groups_allowed_to_order_items}			= 'public';
$PREF{groups_allowed_to_force_update_of_thumbs_cache}	= 'public';
$PREF{groups_allowed_to_create_folders_during_upload}	= 'public';
$PREF{groups_allowed_to_create_folders_thru_filelist}	= 'public';
$PREF{groups_allowed_to_rotate_images}			= 'public';



# PREFs Section 03: Security.
############################################################################
# Once you allow someone to download a file from your uploads area,
# they will know the path to all your uploads.  If you don't want
# them to be able to see all the other files by just visiting that
# directory's address, you'll need to put a .htaccess file in that
# directory with the line "Options -Indexes" (without quotes).
# However, as long as they know the address, they can still try to
# guess filenames that might be in there.  As an extra security
# precaution, you can set serialize_all_uploads, which adds a long
# pseudo-random number to each filename, making it virtually
# impossible that someone could guess the name of a file in the
# directory.
#
$PREF{serialize_all_uploads}				= 'no';



# PREFs Section 03: Security.
############################################################################
# Choose whether the script should display a link to the list of
# uploaded files.  Note that "members" includes "admins", and
# "strangers" includes everyone (i.e. members and admins too).
#
$PREF{show_link_to_uploads_for_strangers}		= 'yes';
$PREF{show_link_to_uploads_for_members}			= 'yes';
$PREF{show_link_to_uploads_for_admins}			= 'yes';



# PREFs Section 03: Security.
############################################################################
# When an upload finishes, we display an "Upload Complete" page, which
# lists the names of the files that were uploaded, along with their
# sizes, and some other information.  On this page, each filename is a
# link to download that file, unless you set these to 'no'.
#
$PREF{upload_complete_page_links_to_files_for_strangers}= 'yes';
$PREF{upload_complete_page_links_to_files_for_members}	= 'yes';
$PREF{upload_complete_page_links_to_files_for_admins}	= 'yes';



# PREFs Section 03: Security.
############################################################################
# Whether to display the login link in the footer-links at the bottom of
# the page.  If you don't want to display it, then you log in by either
# trying to access a page you don't have access to (which will print the
# login link in the error message), or by passing ?login to the script.
# Of course if you're not configuring your FileChucker with any of the
# password PREFs then this is irrelevant.
#
$PREF{show_login_link}					= 'yes';



# PREFs Section 03: Security.
############################################################################
# In various places -- the upload subdirectory drop-down box, the move-item
# page, etc -- we need to show the user a path to the uploaded files.  The
# beginning of this path will be the value of your uploaded_files_dir if
# that's in your docroot, or else it'll be the value you set for
# uploaded_files_urlpath.  But if you want that beginning part of the path
# to be hidden from your users, then enable this PREF.  Note that the user
# can still see this part of the path whenever they actually download a
# file, since naturally we need to go through the whole path to get to the
# file.
#
$PREF{hide_path_to_uploads_dir}				= 'no';



# PREFs Section 03: Security.
############################################################################
# FileChucker supports custom folder permissions, allowing you to specify 
# which user-levels (public, member, or admin) have read-only (RO) or
# read-write (RW) access (or no access) on a per-folder basis.  If you're
# also using UserBase, then you can create unlimited user-levels (i.e. 
# groups) and you can also specify permissions per individual user.
#
# If you don't specify any permissions for a given folder, then it inherits 
# the permissions from its parent folder; if no permissions have been set 
# for a folder or its parents, then the default rights specified here take
# effect.
#
# The $PREF{permissions_required_to_view_permissions} setting allows you to 
# control whether users can see what permission levels are set (only for
# folders that they can see).  Only admins can set/change permissions, 
# unless you are using UserBase and you have set the $PREF{enable_userdirs}
# setting, in which can you can allow users to adjust the permissions within
# their own userdir by setting the $PREF{users_can_change_perms_in_own_userdir}
# option.  By default this only allows the user to adjust whether the generic
# "public" and "members" groups have access to their folders, because in many
# cases you would not want your users to be able to see the other groups and
# usernames in your system.  But you can adjust this behavior as well using the
# users_changing_userdir_perms_can_see_other_groups/users settings.
#
# The $PREF{user_perms_override_group_perms_for_same_folder} setting (which 
# only applies when using UserBase, since without UserBase there are no
# individual users, only groups aka user-levels) specifies whether user or
# group permissions have higher priority when both are set for the same 
# folder.  When both are set but at different levels, the perms closest to 
# the folder in question are the ones that take effect.  For example, given
# folders foo, bar, and baz with these permissions set:
#
#	foo		-> set to RO for user "bob"
#	|--bar		-> set to RW for group "sales" (where bob is a member)
#	   |--baz	-> no perms set
#
# The effective permissions for bob are RO for foo, RW for bar, and RW for
# baz.
#
# Note that this feature requires a database, which you must configure
# in PREFs Section 12, and your database user must have these MySQL 
# privileges: Select, Insert, Update, Delete, Create.  Or if you want to
# manually create the table yourself, then the user does not need the Create
# privilege.
#
$PREF{enable_custom_folder_permissions}			= 'no';
$PREF{perms_table_name}					= 'folderpermstrl';
$PREF{default_folder_rights}				= 'none'; # none, ro, rw; admins always have rw.
$PREF{permissions_required_to_view_permissions}		= 'rw';	  # none, ro, rw, or admin.
$PREF{user_perms_override_group_perms_for_same_folder}	= 'yes';  # requires UserBase.
$PREF{users_can_change_perms_in_own_userdir}		= 'yes';  # requires UserBase & $PREF{enable_userdirs}.
$PREF{users_changing_userdir_perms_can_see_other_groups}= 'no';
$PREF{users_changing_userdir_perms_can_see_other_users}	= 'no';



# PREFs Section 03: Security.
############################################################################
# These should virtually always be 777; on a small number of servers you may
# be able to get away with using the less-permissive 755 instead.
#
$PREF{writable_dir_perms_as_string}			= '0777';	# quotes required. default is '0777'.
$PREF{writable_dir_perms_as_octal}			= 0777;		# no quotes. default is 0777.
$PREF{writable_dir_perms_mask_as_octal}			= 07777;	# no quotes. default is 07777.










# PREFs Section 04: User-directories.
############################################################################
# Only allow each user to access their own upload directory.  The user's
# directory is determined by the preferences you set below; it will either
# come from ?userdir=foo on the URL, or from a username cookie that's set
# by your site's existing login framework.  If you don't want any kind of
# username-based directories, and you want all users to be able to upload
# to wherever they want, then don't set this.  Finally note that even when
# this is set, administrators can still upload to and view any folder.
#
$PREF{enable_userdirs}					= 'no';
$PREF{userdir_folder_name}				= 'home';
$PREF{error_if_userdir_not_supplied}			= 'no';



# PREFs Section 04: User-directories.
############################################################################
# If you're dropping FileChucker into an existing system with lots of
# users, you may not want to manually create a user subdirectory for each
# one.  In that case you can enable this, and then anyone who visits with
# ?userdir=foo or with foo in their username cookie will cause the username
# directory to be created automatically.
#
$PREF{auto_create_userdirs}				= 'yes';



# PREFs Section 04: User-directories.
############################################################################
# Enable ?userdir=username (or ?userdir=whatever) on the URL to automatically
# select the upload subdirectory.  Note that this is probably insecure and
# you should use enable_userdir_from_cookie instead.
#
$PREF{enable_userdir_on_url}				= 'no';



# PREFs Section 04: User-directories.
############################################################################
# If you're using enable_userdir_on_url, then you probably also want to set
# this keep_userdir_on_url option, so that when a user clicks on the various
# links like "Show Uploads," it keeps them inside their proper folder.
#
$PREF{keep_userdir_on_url}				= 'no';



# PREFs Section 04: User-directories.
############################################################################
# If you want per-username upload subdirectories, and you already have some
# kind of login framework in place on your site that stores usernames in
# cookies, then you can use this to automatically choose the right subdir
# based on the value in the cookie.  This means that each user will only
# be able to view and upload to his own subdirectory within your
# uploaded_files_dir.
#
$PREF{enable_userdir_from_cookie}			= 'no';
$PREF{userdir_cookie_name}				= 'username';









# PREFs Section 05: Subdirectories.
############################################################################
# Allow users to upload to subdirectories if they want.
#
$PREF{enable_subdirs}					= 'yes';



# PREFs Section 05: Subdirectories.
############################################################################
# Allow users to create new subdirectories (but only within your
# uploaded_files_dir, of course).  You can also choose to only
# display a single "New subdir" textbox, even when the user is
# uploading multiple files, so that all the files in that one
# upload session will go into the same new subdirectory.
#
$PREF{enable_manual_creation_of_new_subdirs_during_upload}= 'yes';
$PREF{only_allow_one_new_subdir_per_upload}		= 'no';
$PREF{max_num_of_subdir_levels}				= 5;
$PREF{max_length_of_new_subdir_names}			= 25;



# PREFs Section 05: Subdirectories.
############################################################################
# FileChucker can automatically create a new subdirectory for each upload,
# and you can specify the name of this new subdirectory here.  It can
# include values from the user's cookies, from the URL, from any extra
# formfields that you have configured (see PREFs Section 07), and from the
# current date/time.
#
# Note that you must also set the enable_subdirs option (above).
#
# To include variables from either the URL or from a cookie, use the format
# %URL{varname} or %COOKIE{cookiename}.  To use values that the user types
# into your form fields, use the format %FIELD{shortname}.  For example if
# you have $PREF{formfield_01_shortname} = 'company', then you can use 
# %FIELD{company}.
#
# You can also use variables of the form %v to insert date/time values based
# on the standard date formatting variables; search the internet for the
# terms "unix man pages: date (1)" (or just run "man date" on any Unix
# system) for more information on the date format.
#
# Anything not preceded by a percent-sign will be passed straight through as
# literal text.
#
# For example, if you set:
#
#	$PREF{automatic_new_subdir_name} = 'Job-%Y%m%d-%COOKIE{company}';
#
# ...and the user has a cookie called "company" set to "MyCo", and the date is
# say Feb 28 2006, then the new subdir will be named:
#
#	Job-20060228-MyCo
#
# Finally note that to disable this, you must comment it out or set
# it to null ('').
#
$PREF{automatic_new_subdir_name}		= '';



# PREFs Section 05: Subdirectories.
############################################################################
# If you want to enable subdirectories, but do not want your users to be
# able to see the list of subdirectories on the upload form, then you can
# disable this.
#
# Whether or not this drop-down is displayed, you can pass ?path=/some/subdir/
# on the URL to specify the destination directory for the uploaded files.
# If the drop-down is displayed, then this has the effect of selecting the
# specified path by default, but the user can still change it.  If the drop-
# down is not displayed, then the path specified on the URL will be forced.
# Note that the $PREF{hide_path_to_uploads_dir} setting (PREFs Section 03)
# affects this option; if that setting is enabled, then the path specified on
# the URL must not include $PREF{uploaded_files_dir} on the front.  And
# conversely, if $PREF{hide_path_to_uploads_dir} is disabled, then the path
# specified on the URL *must* include $PREF{uploaded_files_dir} on the front.
#
$PREF{display_dropdown_box_for_subdir_selection}	= 'yes';



# PREFs Section 05: Subdirectories.
############################################################################
# A relatively frequent request is for the ability to allow uploads to
# subdirectories of your $PREF{uploaded_files_dir} folder, but not to
# that folder itself.  This option enables that behavior.
#
$PREF{force_all_uploads_into_subdirectories}		= 'no';









# PREFs Section 06: Email Notification.
############################################################################
# You can have the script send you an email whenever a new upload happens.
# It can be sent to as many recipients as you want.  Most of the email PREFs
# are fairly self-explanatory, but here are a few notes: the sender address
# doesn't have to be a real address, but it DOES have to end with a real
# domain name.  The smtp server is probably localhost or mail.yoursite.com,
# and we'll try both smtp and sendmail when trying to send an email. The
# email type can be either html or text, and the failure action can be
# either die_on_email_error or null, in which case we'll just ignore the
# error.  Note that if you set it to die_on_email_error, then that means
# we can't fork the sending operation off into a separate process, since we
# have to wait to make sure it completes; this means that the upload takes
# longer from the user's perspective (if the upload was big and the email-
# sending operation takes a while).  So once you've got FileChucker tested
# and are satisfied that the email portion works, you may want to NOT
# die on email error.
#
# SMTP Authentication is only needed if your mail server requires it.  If
# so, you'll need to set the path to sendmail to either '/dev/null' or
# just ''.
#
# Note that if you want your users to be able to enter their own email
# address(es) on the upload form, to receive email notifications at those
# addresses, then you must configure an extra formfield for that, in 
# PREFs Section 07.
#
# If you do enable an email-address formfield, you can choose to have the
# From: address on your notification emails be set to whatever address
# the user enters.  To do that, set the $PREF{sender_email_address}
# option here to 'user_email_address'.
#
$PREF{send_email_notifications}				= 'no';
$PREF{attach_uploaded_files_to_notification_emails}	= 'no';
$PREF{email_notification_recipient_1}			= 'me@my.com';
$PREF{sender_email_address}				= 'filechucker@mysite.com';
$PREF{smtp_server}					= 'localhost';
$PREF{smtp_port}					= 25; # usually 25 or 587.
$PREF{smtp_auth_username}				= '';
$PREF{smtp_auth_password}				= '';
$PREF{path_to_sendmail}					= '/usr/sbin/sendmail';
$PREF{email_type}					= 'html';
$PREF{email_subject}					= "New upload on mysite.com";
$PREF{email_failure_action}				= 'die_on_email_error'; 



# PREFs Section 06: Email Notification.
############################################################################
# If you enable a custom text box as an email field (see PREFs Section 07),
# you can choose to have notification emails sent to the user-entered
# address(es), and whether those emails should contain the uploaded files 
# as attachments.  Note that this is separate from whether the site's
# webmaster receives attachments on his notification emails (see above).
#
$PREF{send_email_notifications_to_userEntered_addresses}	= 'yes';
$PREF{attachments_on_notifications_to_userEntered_addresses}	= 'no';



# PREFs Section 06: Email Notification.
############################################################################
# If you want totally customizable notification emails, use the options in
# this section.  Here are some examples (these are for plaintext emails; be
# sure to add line-breaks <br /> and/or paragraphs <p> if you're using HTML
# emails):
#	
#	$PREF{admin_email_subject_for_new_uploads} = "New upload from: %uploader_hostname%";
#	
#	$PREF{admin_notification_email_template} = qq`
#	
#	New upload received.  Details:
#
#	Date:		%endtime_nice%
#	Uploader's IP:	%uploader_ipaddress%
#	Total size:	%totalsize_nice%
#	...
#
#	Files Uploaded:
#
#	%filelist%
#	
#	`;
#
#
#	$PREF{user_email_subject_for_new_uploads} = "Upload confirmation from mysite.com";
#	
#	$PREF{user_notification_email_template} = qq`
#	
#	Thanks for your upload!
#	...
#	
#	`;
#	
# The list of allowable variables includes all your formfield _shortname values
# (see PREFs Section 07), plus these built-in variables:
# 
# 	uploader_ipaddress 	uploader_hostname
# 	totalsize_bytes 	totalsize_nice
# 	userdir		 	username
# 	startetime	 	starttime_nice
# 	endetime	 	endtime_nice
# 	finalpath_local		filelist
#
# The etime (epoch-time) variables %startetime% and %endetime% can also be
# formatted into date variables in any format you'd like, by using this
# syntax: 
#
#	%endetime--date--#Y-#m-#d, #I:#M #p%
#
# Search the internet for "unix man pages: date" (or just run the command
# "man date" on any Unix system) for more information on the date format.
#
# The %filelist% variable is for the names of the files in this upload.
# Each filename in the list is formatted based on the template in the
# $PREF{admin_notification_email_filename_template} option or the
# $PREF{user_notification_email_filename_template} option, and these
# can include the variables filename, filesize, linktofile, realpath,
# urlpath, localpath, filenum, and filecount.  For example:
#
#	$PREF{admin_notification_email_filename_template} = qq`File %filenum% of %filecount%:\n%filename% (%filesize%)\n%linktofile%\n\n`;
#
# Or, if you are using HTML-formatted emails:
#
#	$PREF{admin_notification_email_filename_template} = qq`<p>File %filenum% of %filecount%:<br /><a href="%linktofile%">%filename%</a> (%filesize%)</p>\n`;
#
# To use this feature, uncomment and set the options below.
#
#$PREF{admin_notification_email_template}		= qq``;
#$PREF{admin_email_subject_for_new_uploads}		= qq``;
#$PREF{admin_notification_email_filename_template}	= qq``;
#
#$PREF{user_notification_email_template}		= qq``;
#$PREF{user_email_subject_for_new_uploads}		= qq``;
#$PREF{user_notification_email_filename_template}	= qq``;









# PREFs Section 07: Upload Form Configuration.
############################################################################
# Title appearing at the top of the page.  This can be text, HTML, an image,
# etc.  You can also create per-theme titles, for example light_title,
# round_title, etc, to give each theme/style a different title.
#
$PREF{title}						= '<div id="title">FileChucker</div>';
#
# Uncomment these if you've installed the images from the zip file and you
# want the nice logos:
#
#$PREF{title}						= qq'<div id="title"><img src="$PREF{path_to_filelist_images}fclogo03.png" alt="FileChucker" /></div>';
#$PREF{dark_title}					= qq'<div id="title"><img src="$PREF{path_to_filelist_images}fclogo02.png" alt="FileChucker" /></div>';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# Intro: text appearing below the title, before the upload form.
# Outtro: text appearing at the bottom of the form, just before the "Begin
# Upload" button.
#
$PREF{intro}						= qq`<p style="text-align: center;">Upload some files!</p>`;
$PREF{outtro}						= '';
$PREF{number_of_files_label}				= 'Number of files to upload:';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# If you're embedding FileChucker into an existing layout, then you probably
# don't want FC to print out full HTML tags.  So you can disable that here.
# In that case you must also put the following lines into the <head> section 
# of your website's header/template file:
#
#	<script type="text/javascript" src="/cgi-bin/filechucker.cgi?js"></script>
#	<link rel="stylesheet" type="text/css" media="all" href="/cgi-bin/filechucker.cgi?css" />
#
# Note that the CSS output may have conditional comments at the bottom that
# you'll need to copy directly into the <head> section of your site.
#
# If you are not going to use print_full_html_tags, then ideally you'll be
# calling FileChucker from a file like /upload/index.shtml that contains
# something pretty similar to this:
#
#	<!--#include virtual="/header.shtml" -->
#	<!--#include virtual="/cgi-bin/filechucker.cgi?$QUERY_STRING" -->
#	<!--#include virtual="/footer.shtml" -->
#
# ...where header.shtml and footer.shtml contain your site-wide standard
# HTML code that each page is wrapped in.  Or, if your header/footer are
# in PHP, then your /upload/index.php might look like this:
#
#	<? virtual("/header.php"); ?>
#	<? virtual("/cgi-bin/filechucker.cgi?" + $_SERVER['QUERY_STRING']); ?>
#	<? virtual("/footer.php"); ?>
#
# However, if you are on a brain-dead server (which is to say, IIS6+) which
# does not support any decent way to call a CGI script that includes the
# proper server environment variables, and your server does not have PHP
# installed, and you still want to include a standard header/footer with
# FileChucker, you can set default_sitewide_header_file and _footer_file
# here.  The contents of these files will then be included in FileChucker's
# output.  Note that no server-side processing (PHP, SSI, etc) will be done
# on the contents of these files; however you can specify a title within
# the header file by inserting the string %%title%% (for example, as in
# <title>%%title%%</title>) and we'll replace that with your value for the
# title_for_sitewide_header variable (or in some cases, an internally-set
# title).  You can also specify %%css%% and %%js%% which we'll replace with
# a call to our internal CSS/JS output.
#
$PREF{print_full_html_tags}				= 'yes'; # overridable by the more specific ones next.
$PREF{print_full_html_tags_for_uploader}		= '';
$PREF{print_full_html_tags_for_uploadcomplete}		= '';
$PREF{print_full_html_tags_for_filelist}		= '';
$PREF{print_full_html_tags_for_default}			= '';
$PREF{default_sitewide_header_file}			= '';
$PREF{default_sitewide_footer_file}			= '';
$PREF{title_for_sitewide_header}			= '';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# You probably don't want to change these.
#
# Note that the 4 <div>s for perpage_container enable the rounded corners of
# the "round" theme.
#
$PREF{outer_container}					= '<div id="fcbody">';
$PREF{perpage_container}				= '<div id="%%on_page%%page"><div id="fcc1"><div id="fcc2"><div id="fcc3"><div id="fcc4">';
$PREF{inner_container}					= '<div id="fc-container">';

$PREF{inner_container_end}				= '</div>';
$PREF{perpage_container_end}				= '</div></div></div></div></div>';
$PREF{outer_container_end}				= '</div>';

$PREF{print_filefields_wrapper_div}			= 'yes';
$PREF{print_file_element_wrapper_div}			= 'yes';

$PREF{viewpath_markup_start}				= '<div id="viewpath"><div id="viewpath-outer"><div id="viewpath-inner" class="clearfix">';
$PREF{viewpath_markup_end}				= '</div></div></div>';

$PREF{footer_markup_start}				= '<div id="fcfooter"><div id="fcfooter-inner"><div id="fcfooter-text">';
$PREF{footer_markup_end}				= '</div></div></div>';

$PREF{title_inside_perpage_container}			= 'yes';
$PREF{footer_inside_perpage_container}			= 'yes';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# You can adjust the text and the target for some of the footer links.
#
$PREF{home_link_name}					= "Home";
$PREF{home_link_url}					= "/";
$PREF{upload_files_link_label}				= "Upload Files";



# PREFs Section 07: Upload Form Configuration.
############################################################################
# By default, we print certain footer links (like Home, Upload Files, Show
# Uploads, New Folder, etc) depending on which page we're on (the file-list
# shouldn't have a link to Show Uploads for example, because we're already
# on that page).  But if you want, you can override all our footer links by
# specifying your own.  Note that you can set $PREF{custom_footer} which is
# a shortcut to set all 4 of these to the same value.
#
#$PREF{custom_footer_for_uploader}			= '<div id="fcfooter"> </div>';
#$PREF{custom_footer_for_uploadcomplete_page}		= '<div id="fcfooter"> </div>';
#$PREF{custom_footer_for_default_pages}			= '<div id="fcfooter"> </div>';
#$PREF{custom_footer_for_filelist}			= '<div id="fcfooter"> </div>';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# By default, if you upload a file that's 1 megabyte or bigger, the file 
# sizes and upload rate on the progress bar will be in MB and MB/s.  If you 
# want to force them to always be in KB instead, set these.
#
$PREF{force_KB_for_size_display}			= 'no';
$PREF{force_KB_for_transfer_rate_display}		= 'yes';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# Specify the width of the progress bar, and whether to also display the
# progress table with it (containing times, sizes, etc).
#
$PREF{progress_bar_width}				= 350;
$PREF{show_progress_table_during_uploads}		= 'yes';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# By default, when an upload begins, the progress bar pops out of nowhere
# and displays below the "Begin Upload" button.  If you want, you can set
# this preference so that it clears the rest of the page first, so that the
# progress bar & table are the only thing on the screen during the upload.
#
$PREF{clear_page_during_upload}				= 'yes';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# This message is displayed at the end of an upload, before we redirect to
# the "Upload Complete" page.
#
$PREF{server_processing_upload_message}			= "Upload complete; the server is now processing your file(s).<br />This could take a minute or two if your upload was very big.<br />Please wait.";



# PREFs Section 07: Upload Form Configuration.
############################################################################
# To cancel an upload, the user only needs to click on some other link, or 
# click on one of their Favorites/Bookmarks, or type some other address into
# the browser's address bar, etc.  But some users feel more comfortable using
# an explicit "Cancel" link, so if you want to, you can enable such a link
# by setting this PREF.  For example:
#
#	$PREF{cancelbutton} = '<div><a href="/">Click here to cancel this upload.</a></div>';
#
$PREF{cancelbutton}					= '';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# If you want to change the look (style) of FileChucker, you can add your
# own CSS here.  For example:
#
#	$PREF{custom_css_section} = qq`body { color: blue; background: #999; } a { color: red; }`;
#
# It's fine to break that up onto multiple separate lines, too, between the
# backticks after the "qq".
#
# If you want to use this to call an external stylesheet, use the standard
# CSS @import command.  Because this setting gets wrapped in style tags,
# you'll also need to close and re-open them, like this:
#
#	$PREF{custom_css_section} = qq`</style><style type="text/css">@import url(/path/to/stylesheet.css);</style><style type="text/css">`;
#
# You can also specify your own custom Javascript code.  Leave off the
# <script> tags.  And you can use schedule_onload_action(myfunction); to
# hook into the onload logic.
#
$PREF{custom_css_section}				= qq``;
$PREF{custom_js_code}					= qq``;



# PREFs Section 07: Upload Form Configuration.
############################################################################
# You can specify your own HTML for custom form fields here.
#
# ! NOTE: in many cases this is overkill, and the built-in extra formfield
# ! options are a better choice.  Scroll down to the end of PREFs Section 07
# ! to use those options instead.
#
# The PREFs should contain your HTML code, for example:
#
#	$PREF{custom_form_fields_top___code}	= qq`Email Address:<input type="text" name="email" /> <br />Phone Number:<input type="text" name="phone" />`;
#
# The _top preference will be displayed on the upload form before the file
# fields, the _bottom will be displayed after the file fields, and the
# _perfile ones will be displayed once per file.  Or, if you want to specify
# your own file elements, you can do that, and in that case just stuff your
# entire custom form code into the _top___code PREF.
#
# For each custom form field that you define here, you MUST also define it
# in the "extra formfields" section below, with a _shortname PREF that is
# the same as the name you use in your custom code here, and you must add
# a _custom PREF to indicate that FileChucker should use your custom code
# instead of generating that form field itself.  For example:
#
#	# In the "extra formfields" section below, set these:
#	#
#	$PREF{formfield_01}			= ""; # the title here is ignored when using custom formfield code, but the PREF must still be defined.
#	$PREF{formfield_01_shortname}		= "company_name";
#	$PREF{formfield_01_custom}		= "yes";
#
#	# Here in the custom formfields section, set this:
#	#
#	$PREF{custom_form_fields_top___code}	= qq`<p>Company Name:<input type="text" name="company_name" /></p>`;
#
# For any perfile code, the names of your perfile elements must end in _%i,
# for example:
#
#	$PREF{custom_form_fields_perfile___code}	= qq`File's author:<input type="text" name="author_%i" /> <br />File created at:<input type="text" name="location_%i" />`;
#
# If you want a given field to be mandatory, i.e. the form will not submit
# until the user enters a value, then add class="required" to the HTML code
# for the element.  For example:
#
#	$PREF{custom_form_fields_top___code}	= qq`Email Address:<input type="text" name="email" class="required" />`;
#
# You can also cause FileChucker to check that the value entered into an input
# element is a valid email address, by using class="emailformat" like this:
#
#	$PREF{custom_form_fields_top___code}	= qq`Email Address:<input type="text" name="email" class="required emailformat" />`;
#
# If you want to specify your own file elements as well (<input type="file" ... />)
# then you'll have to set $PREF{using_custom_file_elements} to 'yes'.  In
# this case you'll also need to specify the number of custom file elements.
# You MUST name your file elements exactly "uploadname1", "uploadname2", etc.
#
# If your code includes your own upload button, it must not use type="submit"
# but instead type="button" or type="image", and the rest must be exactly like
# this example, except for the value, which you can customize:
#
#	<input type="button" value="Begin Upload" id="uploadbutton" class="default button" onclick="startupload()" />
#
# ...and then you should set $PREF{upload_button} to null (below).
#
$PREF{custom_form_fields_top___code}			= qq``;
$PREF{custom_form_fields_perfile___code}		= qq``;
$PREF{custom_form_fields_bottom___code}			= qq``;
$PREF{using_custom_file_elements}			= 'no';
$PREF{num_custom_file_elements}				= 5;



# PREFs Section 07: Upload Form Configuration.
############################################################################
# This is the upload button, in case you want to use an image instead, etc.
#
$PREF{upload_button}					= qq`<div id="uploadbuttonwrapper"><input type="button" value="Begin Upload" id="uploadbutton" class="default button" onclick="startupload()" /></div>`;



# PREFs Section 07: Upload Form Configuration.
############################################################################
# For your extra formfields (see below), if you choose to make any of them
# required, then if the user does not fill them in, we'll display a message
# and change their colors.
#
$PREF{bgcolor_for_unfilled_required_fields}		= '#ffdd00';
$PREF{textcolor_for_unfilled_required_fields}		= '#000';
$PREF{default_bgcolor_for_required_fields}		= '#ffffff'; # or try null ('').
$PREF{default_textcolor_for_required_fields}		= '#000';



# PREFs Section 07: Upload Form Configuration.
############################################################################
# Extra formfields/textboxes (including email fields & drop-down lists):
#
# Allow the user to enter comments or information about the file(s) that
# they are uploading.  This information can be emailed to you as well as
# saved on the server in a text file and/or a database.
#
# You must specify a _shortname PREF for each form field; this may contain
# only letters, numbers, and underscores.  It is used for the "name" attribute
# of the form element, and for the name of the database column/field if you're
# storing your upload info in a database (see PREFs Section 09).
#
#	$PREF{formfield_01}			= "Company Name:";
#	$PREF{formfield_01_shortname}		= "company"; # becomes the DB column name.
#
# The default form-field type is a single-line text box, but you can make
# a multiline box (i.e. a <textarea>) by adding the _multiline option:
#
#	$PREF{formfield_01}			= "Description:";
#	$PREF{formfield_01_multiline}		= 'yes';
#
# The default position is 'top', i.e. above the file input field(s)s, but you
# can specify 'bottom' or 'perfile' to position the formfield there instead:
#
#	$PREF{formfield_01}			= "Description:";
#	$PREF{formfield_01_position}		= 'bottom'; # or 'perfile'.
#
# You can specify that FileChucker should save the user's input in a cookie,
# and then auto-fill the the textbox from that cookie the next time that 
# visitor loads the page, by setting a _save PREF like this:
#
#	$PREF{formfield_01}			= 'Company:';
#	$PREF{formfield_01_save}		= 'yes';
#
# Or, if you are setting a cookie on some other page on your website, and
# you want FileChucker to read that cookie and use it to fill a textbox,
# then create a _fillfromcookie PREF and set it to the name of your cookie,
# like this:
#
#	$PREF{formfield_01}			= 'Company:';
#	$PREF{formfield_01_fillfromcookie}	= 'company_name';
#
# You can create a _required PREF for any formfield, which will force the
# user to enter a value before allowing the form to be submitted.
#
#	$PREF{formfield_01}			= 'Company:';
#	$PREF{formfield_01_required}		= 'yes';
#
# To make a drop-down list, use the following example.  Note that the
# _dropdown_values PREF is optional; you should only use it if you want
# the values submitted to be different from the values displayed.
#
#	$PREF{formfield_01}			= 'Department:';
#	$PREF{formfield_01_email}		= 'yes';
#	$PREF{formfield_01_dropdown}		= '|||Sales|||Support|||Other';
#	$PREF{formfield_01_dropdown_values}	= '|||sales@mysite.com|||help@mysite.com|||contact@mysite.com';
#
# You can also make _radio and _checkbox elements; see the examples below.
#
# To make a hidden field, use the _hidden option.  In this case you'll need to
# fill the field some other way, for example with the _fillfromcookie option:
#
#	$PREF{formfield_01}			= 'PHP Session ID:';
#	$PREF{formfield_01_hidden}		= 'yes';
#	$PREF{formfield_01_fillfromcookie}	= 'phpsessid';
#
# You can add a _default PREF to set the initial/default value for an item:
#
#	$PREF{formfield_01}			= "Fax Number:";
#	$PREF{formfield_01_default}		= "N/A";
#
# You can specify a string value (text, HTML, etc) to appear before or
# after any given formfield by creating a _before or _after PREF for it:
#
#	$PREF{formfield_01}			= "Phone:";
#	$PREF{formfield_01_after}		= "<p>(Phone number will not be sold or redistributed.)</p>";
#
# You can automatically clean up any submitted text.  This will remove any
# characters except 0-9A-Za-z._- and will replace spaces with underscores:
#
#	$PREF{formfield_01}			= "Company Name:";
#	$PREF{formfield_01_clean}		= "yes";
#
# The _numeric option forces the user to only enter numbers:
#
#	$PREF{formfield_01}			= "PO Number:";
#	$PREF{formfield_01_numeric}		= "yes";
#
# If you are enabling reprocessing on your site (see PREFs Section 09) then you
# can add a formfield PREF called _reprocessing and set it to "refill" to cause
# that textbox to be refilled with the value from the original upload, as long
# as you have the upload info stored in a database (PREFs Section 09).  This is
# in some ways similar to the _save option, but whereas that refills the textbox
# from a cookie on the user's computer, this refills it from the value in your 
# database.  You can also specify "readonly" in the same preference to cause the 
# refilled value to be unchangable by the user.  Specify "skip" or "hide" to 
# skip/hide this formfield during reprocessing. You can also specify 
# "fill_with_num_files_selected" (self-explanatory).
#
#	$PREF{formfield_01}			= "Company Name:";
#	$PREF{formfield_01_reprocessing}	= "refill,readonly";
#
# Finally, note that you can use any formfield as an email address field,
# to which a notification email can be sent, by creating an _email PREF:
#
#	$PREF{formfield_01}			= 'Email Address:';
#	$PREF{formfield_01_email}		= 'yes';
#
# Then the formfield will accept one or more email addresses separated by commas
# and/or spaces, and notification of the upload including a link to the file(s)
# can be sent to the specified address(es).  You must configure the email
# notification PREFs (see PREFs Section 06) for this to work.  Note that you 
# should probably only create such an email field if you are requiring your 
# users to be logged in before they can upload.  This is because if you allow 
# just anybody to enter an email address, and you then send an email to that 
# address, you have created an open invitation for spammers to abuse your 
# website.  They can hit it thousands of times per day and send their spam to
# as many addresses as they want.
#
# The following examples are commented-out so they are inactive. You can 
# uncomment them (delete the leading "#") and edit them, or create your own.
#
#
#
#$PREF{top_formfields_title}				= 'Please enter the following information:';
#
#$PREF{formfield_01}					= 'Company:';
#$PREF{formfield_01_save}				= 'yes';
#$PREF{formfield_01_required}				= 'yes';
#$PREF{formfield_01_shortname}				= 'company';
#
#$PREF{formfield_02}					= 'Description of upload:';
#$PREF{formfield_02_multiline}				= 'yes';
#$PREF{formfield_02_size}				= '200x150';
#$PREF{formfield_02_shortname}				= 'description';
#
#$PREF{formfield_03}					= 'Email Address:';
#$PREF{formfield_03_save}				= 'yes';
#$PREF{formfield_03_email}				= 'yes';
#$PREF{formfield_03_required}				= 'yes';
#$PREF{formfield_03_shortname}				= 'email_address';
#
#$PREF{formfield_04}					= 'Gender:';
#$PREF{formfield_04_dropdown}				= '|||M|||F|||Other';
#$PREF{formfield_04_required}				= 'yes';
#$PREF{formfield_04_shortname}				= 'gender';
#
#
#
#$PREF{perfile_formfields_title}			= 'About this file:';
#
#$PREF{formfield_05}					= 'Created by:';
#$PREF{formfield_05_shortname}				= 'creator';
#$PREF{formfield_05_position}				= 'perfile';
#
#$PREF{formfield_06}					= 'Creation date:';
#$PREF{formfield_06_shortname}				= 'creation_date';
#$PREF{formfield_06_position}				= 'perfile';
#
#
#
#$PREF{bottom_formfields_title}				= 'Additional comments (optional):';
#
#$PREF{formfield_07}					= '';
#$PREF{formfield_07_multiline}				= 'yes';
#$PREF{formfield_07_size}				= '200x250';
#$PREF{formfield_07_shortname}				= 'comments';
#$PREF{formfield_07_position}				= 'bottom';
#
#$PREF{formfield_08}					= 'Age:';
#$PREF{formfield_08_radio}				= '0-13|||14-17|||18+';
#$PREF{formfield_08_default}				= '18+';
#$PREF{formfield_08_labelfirst}				= 'no';
#$PREF{formfield_08_label_spacer}			= " ";
#$PREF{formfield_08_item_separator}			= "<br /><br />";
#$PREF{formfield_08_shortname}				= "age";
#$PREF{formfield_08_position}				= 'bottom';
#
#$PREF{formfield_09}					= 'Would you like your items gift-wrapped?';
#$PREF{formfield_09_checkbox}				= 'yes';
#$PREF{formfield_09_default}				= '';
#$PREF{formfield_09_labelfirst}				= 'no';
#$PREF{formfield_09_label_spacer}			= " ";
#$PREF{formfield_09_shortname}				= "giftwrapping";
#$PREF{formfield_09_position}				= 'bottom';









# PREFs Section 08: Upload Restrictions.
############################################################################
# Allow the user to upload multiple files at the same time, up
# to this limit.
#
$PREF{max_files_allowed}				= 5;



# PREFs Section 08: Upload Restrictions.
############################################################################
# Set the maximum amount of data that can be uploaded at once.  Note that
# this is per upload, not per file; if you set this to 10 megabytes, then
# you can upload one 10MB file, or two 5MB files, etc, as long as the sum
# is not more than your limit.  Note that one megabyte is 1024*1024*1; 
# 5 MB is 1024*1024*5, etc.
#
$PREF{sizelimit_for_strangers}				= 1024*1024*30;
$PREF{sizelimit_for_members}				= 1024*1024*50;
$PREF{sizelimit_for_admins}				= 1024*1024*80;



# PREFs Section 08: Upload Restrictions.
############################################################################
# You can specify a quota for your upload directory.  You can also specify
# a quote for each userdir, if you have userdirs enabled (see PREFs Section
# 04).  Note that these values are in bytes; to specify them in megabytes,
# multiply by 1024*1024, for example 1024*1024*1 is one MB, 1024*1024*5 is
# five MB, etc.  Set them to zero to disable the quotas.
#
$PREF{quota_for_entire_upload_directory}		= 0;
$PREF{quota_for_member_userdirs}			= 0;



# PREFs Section 08: Upload Restrictions.
############################################################################
# You can allow or disallow uploads based on file extension.  Each of these
# two preferences takes a list of extensions separated by commas and/or
# spaces.  Note that the period must be included with the extension.  For
# example:
#
#	$PREF{only_allow_these_file_extensions} 	= '.jpg, .png, .gif';
#
# Finally, note that these are not case sensitive.
#
$PREF{only_allow_these_file_extensions}			= '';
$PREF{disallow_these_file_extensions}			= '.exe .php .php3 .php4 .php5 .phtml .cgi .pl .sh .py .htaccess .htpasswd';
$PREF{allow_files_without_extensions}			= 'yes';
$PREF{disallow_these_strings_within_filenames}		= '\.php, \.asp, \.cgi, \.pl$ \.plx'; # can include regexes, so periods must be escaped.  must be in single quotes.



# PREFs Section 08: Upload Restrictions.
############################################################################
# In both filenames and directory names, convert spaces to underscores,
# and remove anything that's not in the set [0-9A-Za-z._-].
#
$PREF{clean_up_filenames}				= 'yes';









# PREFs Section 09: Processing Uploads.
############################################################################
# In PREFs Section 03: Security, there is a option "serialize_all_uploads"
# that adds a long (~40 digit) serial number to the end of all filenames.
# But even if that option is disabled, if you don't set the 
# overwrite_existing_files option here, then a serial number WILL be
# appended onto the filename if a file by the same name already exists.
# Alternatively, you can set the nice_serialization options here, which
# will add a number like "_01" or " 01" if a file by the same name already
# exists.  So in summary, you can have all files serialized (long number),
# all files nice-serialized (2-digit number), only serialize when filename
# already exists (either long or 2-digit serial), or overwrite existing files
# (i.e. never serialize).  Note that regular- and nice-serialization are
# mutually exclusive, and that regular (serialize_all_uploads) takes
# precedence if both are set, since it's a security feature.
#
$PREF{overwrite_existing_files}				= 'no';
$PREF{nice_serialization_when_file_exists}		= 'yes';
$PREF{nice_serialization_always}			= 'no';



# PREFs Section 09: Processing Uploads.
############################################################################
# You can have a datestamp (YYYYMMDD-HHMM) added to the filename for
# each upload.  It will be added to the end, right before the extension.
#
$PREF{datestamp_all_uploads}				= 'no';



# PREFs Section 09: Processing Uploads.
############################################################################
# FileChucker can operate in a few special upload modes:
#
# Replace mode lets users upload files that already exist on the server,
# overwriting those files.  If you have any extra formfields enabled,
# they will not be shown in replace mode -- it's only for replacing the
# files themselves.
# 
# Reprocessing mode lets users go through the upload process, filling out
# any extra formfields that you have enabled; but instead of uploading
# files, it uses files that have been uploaded before and are already on
# the server.
#
# AddFile mode lets users upload new files, but does not show any of your
# extra formfields.
#
# These are disabled by default because most people probably won't have a
# use for them.
#
$PREF{enable_replace_mode}				= 'no';
$PREF{enable_reprocessing_mode}				= 'no';
$PREF{enable_addfile_mode}				= 'no';
$PREF{label_for_replace_action}				= 'Replace';
$PREF{label_for_reprocess_action}			= 'Reprocess';
$PREF{label_for_addfile_action}				= 'Add New Files';
$PREF{reprocessing_mode_file_list_message}		= "Reprocessing: %%folder_name%% [%%num_files%% file(s)]";
$PREF{reprocessing_mode_file_list_done_message}		= "Reprocessed: %%folder_name%% [%%num_files%% file(s)].";
$PREF{list_filenames_on_reprocessing_form}		= "no";
$PREF{pass_filenames_when_reprocessing_is_done}		= "no";



# PREFs Section 09: Processing Uploads.
############################################################################
# FileChucker can automatically rename every file that gets uploaded,
# based on a format that you specify here.
#
# You can use the following variables in your filename formatting:
#
#	#O - original filename from the user's computer (without extension)
#
#	#E - extension from original filename (without leading period)
#
#	#U - name of user's private directory (null unless you've 
#	     enabled the userdir PREFs)
#
#	#N - sequence number of this file within its original upload
#	     (set to 1 if only a single file was uploaded)
#
# You can also use variables of the form %v to insert date/time
# values based on the standard date formatting variables; Google for
# "unix man pages: date (1)" (or just run "man date" on any Unix
# system) for more information on the date format.
#
# If you've enabled any extra formfields (PREFs Section 07), you can
# use the values from those fields in renaming the uploaded files.
# Just use the _shortname from the PREF within a %FIELD container.
# For example if you have $PREF{formfield_01_shortname} = 'company',
# then you can use %FIELD{company}.
#
# Finally, you can include variables from either the URL or from a
# cookie by using %URL{varname} or %COOKIE{cookiename}.
#
# And anything not preceded by a pound-sign or a percent-sign will be 
# passed straight through as literal text.
#
# For example, if you set:
#
#	$PREF{reformat_filenames_for_all_uploads} = '%Y%m%d-#U_#N-%COOKIE{foo}-#O.#E';
#
# ...and then a user uploads 3 files, on say Feb 28 2006, then they
# will be renamed to:
#
#	20060228-userdirname_1-fooCookieValue-originalfilename.ext
#	20060228-userdirname_2-fooCookieValue-originalfilename.ext
#	20060228-userdirname_3-fooCookieValue-originalfilename.ext
#
# Finally note that to disable this, you must comment it out or set
# it to null ('').
#
$PREF{reformat_filenames_for_all_uploads}		= '';



# PREFs Section 09: Processing Uploads.
############################################################################
# This setting controls how uploads are processed internally.  It should
# probably be set to 'yes' in most cases.
#
$PREF{move_tmpfile_instead_of_copying_contents}		= 'yes';



# PREFs Section 09: Processing Uploads.
############################################################################
# You can log information about each uploaded file, like the uploader's
# IP/hostname/user-agent, timestamps, elapsed time, etc.  This information
# can be logged in text files and/or in a database.
#
# If you've enabled any custom text boxes, and you have not enabled the
# _in_database PREF here, then the _in_files PREF is automatically enabled.
#
# In order for the store_upload_info_in_database option to work, you must do
# three things:
#
#	1. set the database preferences in PREFs Section 12;
#
#	2. set $PREF{db_columns_for_upload_info} to a comma-separated list
#	   of the column names that you want to be populated; the names in
#	   this list must either a) be set by you in PREFs Section 07 under
#	   "extra formfields" with a _shortname PREF, for example:
#
#		$PREF{formfield_01}		= 'Please enter your name:';
#		$PREF{formfield_01_shortname}	= 'clientname'; # becomes the DB column name.
#
#	   ...or b) be one of the names from the following built-in list of
#	   upload data collected:
#
#		filepath,filename,origpath,origname,filesize,uploadsize,filecount,
#		serial,ip,host,userdir,username,useragent,starttime,endtime,
#		startetime,endetime,elapsecs,elapmins,elaphours
#
#	3. actually have a database on your server which contains a table
#	   with the columns specified in $PREF{db_columns_for_upload_info}.
#
# Column types for the built-in list of data collected:
#
#	filepath		text		# because path lengths are unlimited on most FSes.
#	filename		varchar(255)	# because filenames on most FSes are limited to 255 chars.
#	origpath		text		# because path lengths are unlimited on most FSes.
#	origname		varchar(255)	# because filenames on most FSes are limited to 255 chars.
#	filesize		bigint unsigned	# or int, if you're confident your files will never exceed 4 GB.
#	uploadsize		bigint unsigned	# at least as big as "filesize" since a given upload can contain multiple files.
#	filecount		int unsigned	# 4 billion files per upload seems like a reasonable limit.
#	serial			varchar(80)	# pseudo-random number formed by concatenating various sources, usually about 50 chars long.  could be longer if your users have lots of digits in their UA strings.
#	ip			varchar(40)	# we'll support IPv6-length IPs just in case.
#	host			varchar(150)	# hostnames can get pretty long.
#	userdir			varchar(255)	# unlikely that a single dirname would exceed this.
#	username		varchar(255)	# unlikely that a single username would exceed this.
#	useragent		varchar(255)	# my Firefox 1.5.0.4 UA is 105 chars.
#	starttime		varchar(22)	# format is "WedJul26,2006,09:38pm".
#	endtime			varchar(22)	# format is "WedJul26,2006,09:38pm".
#	startetime		bigint unsigned	# the current epoch-time value is around 1.1 billion; ~2 billion is the year 2035; INT's limit is about 4 billion, so BIGINT to be safe.
#	endetime		bigint unsigned	# the current epoch-time value is around 1.1 billion; ~2 billion is the year 2035; INT's limit is about 4 billion, so BIGINT to be safe.
#	elapsecs		int unsigned	# unlikely for a single upload to need/exceed 4 billion seconds (1 million hours).
#	elapmins		float unsigned	# a simple decimal number with a single digit after the decimal.
#	elaphours		float unsigned	# a simple decimal number with a single digit after the decimal.
#
# And of course your table should have an id column of type:
# BIGINT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY.
#
# Here's the SQL code to create that table:
#
#	CREATE TABLE `upload_info` (
#	`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY ,
#	`filepath` TEXT NOT NULL ,
#	`filename` VARCHAR( 255 ) NOT NULL ,
#	`origpath` TEXT NOT NULL ,
#	`origname` VARCHAR( 255 ) NOT NULL ,
#	`filesize` BIGINT UNSIGNED NOT NULL ,
#	`uploadsize` BIGINT UNSIGNED NOT NULL ,
#	`filecount` INT UNSIGNED NOT NULL ,
#	`serial` VARCHAR( 80 ) NOT NULL ,
#	`ip` VARCHAR( 40 ) NOT NULL ,
#	`host` VARCHAR( 150 ) NOT NULL ,
#	`userdir` VARCHAR( 255 ) NOT NULL ,
#	`username` VARCHAR( 255 ) NOT NULL ,
#	`useragent` VARCHAR( 255 ) NOT NULL ,
#	`starttime` VARCHAR( 22 ) NOT NULL ,
#	`endtime` VARCHAR( 22 ) NOT NULL ,
#	`startetime` BIGINT UNSIGNED NOT NULL ,
#	`endetime` BIGINT UNSIGNED NOT NULL ,
#	`elapsecs` INT UNSIGNED NOT NULL ,
#	`elapmins` FLOAT UNSIGNED NOT NULL ,
#	`elaphours` FLOAT UNSIGNED NOT NULL
#	) ;
#
# Finally note that each row in the database represents one uploaded file,
# not one upload session.  Unless of course you've configured FileChucker
# to only allow one file to be uploaded at a time, in which case there IS
# only one uploaded file in one upload session.
#
# You can also store the values of URL variables into the upload info files
# and/or database, by setting $PREF{store_values_from_these_url_variables}.
# This should be a list separated by commas and/or spaces.
#
$PREF{store_upload_info_in_files}			= 'yes';
$PREF{store_upload_info_in_database}			= 'no';
$PREF{db_table_for_upload_info}				= 'upload_info';
$PREF{db_columns_for_upload_info}			= 'filepath,filename,origpath,origname,filesize,uploadsize,filecount,serial,ip,host,userdir,username,useragent,starttime,endtime,startetime,endetime,elapsecs,elapmins,elaphours';
$PREF{store_values_from_these_url_variables}		= ''; # You must add these to db_columns_for_upload_info too (if you're storing to DB).









# PREFs Section 10: Post-Upload.
############################################################################
# After a successful upload, we normally display a page that says
# "upload complete" and lists the uploaded files, their sizes, etc.
# If you want, you can redirect to some other page instead.  This
# value MUST start with http:// or https://. Note that you can include
# variables in the value from either the URL or from a cookie by
# using %URL{varname} or %COOKIE{cookiename}.  For example:
#
#	$PREF{after_upload_redirect_to}			= 'http://mysite.com/foo/bar/?baz=%URL{baz}&bim=%COOKIE{bim}';
#
# All the relevant information will be passed on the query-string to your
# redirection URL, including any error-state information.
#
$PREF{after_upload_redirect_to}				= '';
$PREF{pass_original_querystring_through}		= 'yes';
$PREF{pass_filenames_on_redirect}			= 'yes';
$PREF{pass_formfield_values_on_redirect}			= 'no';



# PREFs Section 10: Post-Upload.
############################################################################
# On the "upload complete" page, we'll print "File X of Y:" followed by
# the filename as a link to the file.  But if you want the full URL of the
# link to be displayed as text on the page, you can enable this option.
#
$PREF{show_text_url_to_file_after_upload}		= 'no';



# PREFs Section 10: Post-Upload.
############################################################################
# Choose what is displayed on the "Upload Complete" page.
#
$PREF{show_builtin_upload_complete_message}		= 'yes';
$PREF{show_builtin_stats_on_upload_complete_page}	= 'yes';
$PREF{custom_message_for_upload_complete_page}		= '';









# PREFs Section 11: File-List Configuration.
############################################################################
# Options for controlling the display of the uploaded-files list.
# You can set the unit, number of decimal places, and the color
# that the rows turn to when you hover the mouse over them.  You
# can also specify how the date should be displayed.  Google for
# "unix man pages: date (1)" (or just run "man date" on any Unix
# system) for more information on the date format.
#
$PREF{unit_for_size_display_in_uploaded_files_list}	= 'KB'; # must be 'KB', 'MB', or 'mixed'.  See PREFs Section Z if you want Ko/Mo.
$PREF{num_decimals_for_uploaded_files_list_sizes}	= 0;
$PREF{shortened_display_filename_length___listmode}	= 35; # characters.
$PREF{shortened_display_filename_length___gridmode}	= 20; # characters.
#$PREF{filelist_row_hover_border}			= '1px solid #bbb';  # currently in testing.
#$PREF{filelist_row_normal_border}			= '1px solid white'; # currently in testing.
$PREF{date_format_for_filelist}				= '%b%d, %I:%M%P';
#$PREF{date_format_for_filelist}			= '%Y-%m-%d, %I:%M %P';
#$PREF{date_format_for_filelist}			= '%a %b %d, %Y, %H:%M';
#$PREF{date_format_for_filelist}			= '%I:%M %P %b %d %Y';
$PREF{only_show_files_with_these_extensions}		= '';
$PREF{hide_files_with_these_extensions}			= '.exe .php .php3 .php4 .php5 .phtml .cgi .pl .sh .py .htaccess .htpasswd';
$PREF{hide_items_whose_names_match}			= '\.fcimages'; # can include regexes, so periods must be escaped.  must be in single-quotes.
$PREF{time_offset}					= -0; # in hours; can include negative sign.



# PREFs Section 11: File-List Configuration.
############################################################################
# The file list can be displayed as a detailed list, or as a grid (useful
# when most of your files are images and you have thumbnails enabled).
# You can also choose to disable altogether the menu controlling these
# options.
#
$PREF{enable_multiple_filelist_modes}			= 'yes';
$PREF{default_filelist_mode}				= 'list'; # list or grid.
$PREF{num_columns_in_grid_mode}				= 3;
$PREF{show_options_menu}				= 'yes';
$PREF{name_of_top_level}				= 'uploads';



# PREFs Section 11: File-List Configuration.
############################################################################
# You can enable/disable some columns in the filelist.
#
$PREF{show_size_column_in_filelist}			= 'yes';
$PREF{show_date_column_in_filelist}			= 'yes';



# PREFs Section 11: File-List Configuration.
############################################################################
# Choose whether to display a checkbox at the end of each row, and a 
# drop-down list of actions at the bottom of the form, to allow users to
# perform actions on multiple files/folders at the same time.
#
# Also choose whether to enable the file/folder/size stats in the footer.
#
$PREF{enable_summary_of_counts_and_sizes}		= 'yes';
$PREF{enable_item_action_checkboxes}			= 'yes';
$PREF{enable_unzip_action}				= 'Unzip'; # this feature is in progress and incomplete.
$PREF{enable_delete_action}				= 'Delete';
$PREF{enable_rotate90_action}				= 'Rotate  90 &deg;';	# for images;
$PREF{enable_rotate180_action}				= 'Rotate 180 &deg;';	# for images;
$PREF{enable_rotate270_action}				= 'Rotate 270 &deg;';	# for images;



# PREFs Section 11: File-List Configuration.
############################################################################
# File-list styling.  Set the color the rows change to on mouse-over (and
# on mouse-out); choose the default file-list style and whether to display 
# a link in the footer to switch between the styles.  You can also create
# your own styles here by adding the name of your new style to the list in
# the enabled_styles PREF, adding a block of corresponding PREFs for it
# here, and then adding a section for it within the get_css() subroutine.
#
$PREF{default_filelist_style}				= 'light';
$PREF{enable_filelist_style_switcher}			= 'yes';
$PREF{enabled_styles}					= 'round, light, dark, big';

$PREF{round___filelist_row_hover_bgcolor}		= '#c0c2b9';
$PREF{round___filelist_row_hover_bgcolor_highcontrast}	= '#86a9bc';
$PREF{round___filelist_row_normal_bgcolor_even}		= '#efefef';
$PREF{round___filelist_row_normal_bgcolor_odd}		= '#efefef';
$PREF{round___filelist_row_hover_text_color}		= 'white';
$PREF{round___filelist_row_hover_link_color}		= 'white';
$PREF{round___filelist_row_normal_text_color}		= '#444';
$PREF{round___filelist_row_normal_link_color}		= '#444';
$PREF{round___filelist_row_visited_link_color}		= '#444';
$PREF{round___filelist_row_highlight_bgcolor}		= '#88d984';

$PREF{light___filelist_row_hover_bgcolor}		= '#c0c2b9';
$PREF{light___filelist_row_hover_bgcolor_highcontrast}	= '#507090';
$PREF{light___filelist_row_normal_bgcolor_even}		= '#efefef';
$PREF{light___filelist_row_normal_bgcolor_odd}		= '#e6e6e6';
$PREF{light___filelist_row_hover_text_color}		= 'white';
$PREF{light___filelist_row_hover_link_color}		= 'white';
$PREF{light___filelist_row_normal_text_color}		= 'black';
$PREF{light___filelist_row_normal_link_color}		= 'black';
$PREF{light___filelist_row_visited_link_color}		= 'black';
$PREF{light___filelist_row_highlight_bgcolor}		= '#5cae64';

$PREF{dark___filelist_row_hover_bgcolor}		= '#474747';
$PREF{dark___filelist_row_normal_bgcolor_even}		= '#545454';
$PREF{dark___filelist_row_normal_bgcolor_odd}		= '#545454';
$PREF{dark___filelist_row_hover_text_color}		= 'white';
$PREF{dark___filelist_row_hover_link_color}		= '#000';
$PREF{dark___filelist_row_normal_text_color}		= '#fff';
$PREF{dark___filelist_row_normal_link_color}		= '#fff';
$PREF{dark___filelist_row_visited_link_color}		= '#fff';
$PREF{dark___filelist_row_highlight_bgcolor}		= '#aa3333';

$PREF{darker___filelist_row_hover_bgcolor}		= '#4a774a';
$PREF{darker___filelist_row_normal_bgcolor_even}	= '#545454';
$PREF{darker___filelist_row_normal_bgcolor_odd}		= '#4d4d4d';
$PREF{darker___filelist_row_hover_text_color}		= 'white';
$PREF{darker___filelist_row_hover_link_color}		= 'white';
$PREF{darker___filelist_row_normal_text_color}		= '#fff';
$PREF{darker___filelist_row_normal_link_color}		= '#fff';
$PREF{darker___filelist_row_visited_link_color}		= '#fff';

$PREF{big___filelist_row_hover_bgcolor}			= '#507090';
$PREF{big___filelist_row_hover_bgcolor_highcontrast}	= '#507090';
$PREF{big___filelist_row_normal_bgcolor_even}		= '#efefef';
$PREF{big___filelist_row_normal_bgcolor_odd}		= '#e6e6e6';
$PREF{big___filelist_row_hover_text_color}		= 'black';
$PREF{big___filelist_row_hover_link_color}		= 'black';
$PREF{big___filelist_row_normal_text_color}		= 'black';
$PREF{big___filelist_row_normal_link_color}		= 'black';
$PREF{big___filelist_row_visited_link_color}		= 'black';
$PREF{big___filelist_row_highlight_bgcolor}		= '#5cae64';

$PREF{minimal___filelist_row_hover_bgcolor}		= '#a3a3a3';
$PREF{minimal___filelist_row_normal_bgcolor_even}	= '#fff';
$PREF{minimal___filelist_row_normal_bgcolor_odd}	= '#fff';
$PREF{minimal___filelist_row_hover_text_color}		= 'black';
$PREF{minimal___filelist_row_hover_link_color}		= 'black';
$PREF{minimal___filelist_row_normal_text_color}		= 'black';
$PREF{minimal___filelist_row_normal_link_color}		= 'black';
$PREF{minimal___filelist_row_visited_link_color}	= 'black';



# PREFs Section 11: File-List Configuration.
############################################################################
# If you have userdirs enabled (see PREFs Section 04), and you don't have
# any top-level folders other than the home folder which contains the 
# userdirs, then you may want to automatically place your users into their
# home folders when they're viewing the file-list, since there's nothing
# else for them to see at the top level.
#
# You can also choose to hide the userdir folder name (usually "home") in
# the breadcrumbs at the top of the filelist, i.e. the default is this:
#
#	Viewing: / uploads / home / username /
#
# ...but instead display this:
#
#	Viewing: / uploads / username /
#
$PREF{navigate_users_into_userdirs_automatically}	= 'no';
$PREF{hide_userdir_folder_name_in_breadcrumbs}		= 'yes';



# PREFs Section 11: File-List Configuration.
############################################################################
# The links to download files can either be normal HTML links that go
# directly to the file:
#
#	<a href="/path/to/uploads/blah/myfile.foo">myfile.foo</a>
#
# ...or, they can go through FileChucker:
#
#	<a href="/upload/?action=download&path=blah&file=myfile.foo">myfile.foo</a>
#
# If the links go through FileChucker, then you can password-protect them
# (via the PREF groups_allowed_to_download) and you can also choose to 
# receive an email notification whenever a file is downloaded (TODO).
#
# Note that the download_links_go_through_FileChucker option is mutually
# exclusive with the download_links_go_through_PeerFactor option.
#
# If you want the file's timestamp to be updated (to indicate that the file
# was accessed) when it is downloaded, you can enable that option.  Note
# that this is only possible when download_links_go_through_FileChucker is
# enabled.  TODO - this is a work in progress.
#
$PREF{download_links_go_through_FileChucker}		= 'no';
$PREF{update_timestamp_on_download}			= 'no'; # TODO - this is a work in progress.



# PREFs Section 11: File-List Configuration.
############################################################################
# You can choose to have your download links go through PeerFactor, which
# is a P2P-based automatic load-balancing system.  All the links in your
# file-list will get prefixed with:
#
#	http://www.peerfactor.fr/get_myfile.jsp?URL=
#
# When a user clicks on a download link, he will receive the file from the
# PeerFactor P2P network if demand for that file is high, or else he'll get
# the file directly from your server if demand for the file is low.  The
# PeerFactor site determines demand in real-time so this is all transparent
# to the user.
#
# Note that the download_links_go_through_PeerFactor option is mutually
# exclusive with the download_links_go_through_FileChucker option.
#
$PREF{download_links_go_through_PeerFactor}		= 'no';



# PREFs Section 11: File-List Configuration.
############################################################################
# Shopping cart / ordering system: you can enable a very basic ordering
# system, where your users can select items (files) from your upload area
# and add them to their cart, and they can then place an order for those
# items, which simply sends an email to you, containing their user info
# and the list of items that they selected.  Note that you must configure
# the SMTP settings in PREFs Section 06 for this to work.
#
$PREF{enable_ordering}					= 'no';
$PREF{select_item_link}					= '<span style="white-space: nowrap; font-size: 80%;">Add To Cart</span>';
$PREF{selection_cookie_name}				= 'selected_items';
$PREF{clear_selections_text}				= 'Empty Cart';
$PREF{clear_selections_verification_text}		= 'About to empty your cart.  Is that OK?';
$PREF{no_selections_text}				= 'Your cart is empty.';
$PREF{item_added_to_cart_text}				= 'Item added to cart.';
$PREF{duplicate_item_text}				= 'This item is already in your cart.  Add it again?';

$PREF{view_items_page_name}				= 'Your Cart';
$PREF{view_items_page_intro}				= '<h1>Your Cart</h1><p>Your cart contains the following items.&nbsp; Use the Submit<br />button below when you are ready to checkout.</p>';
$PREF{place_order_fields}				= '<div class="name"><input type="text" name="name" class="text required" /> Name</div> <div class="email"><input type="text" name="email" class="text required" /> Email</div> <div class="submit"><input type="button" value="Submit Your Order" class="default button" onclick="startorder()" /></div> ';

$PREF{process_order_page_name}				= 'Order Received - Thank You';
$PREF{process_order_page_intro}				= '<h1>Order Received</h1><p>Thank you for your order.&nbsp; We are now processing it and we will <br />contact you soon.&nbsp; Please print or save this page for your records.</p>';

$PREF{order_email_recipient_1}				= 'me@mysite.com';
$PREF{order_sender_email_address}			= 'orderform@mysite.com';
$PREF{order_email_subject}				= 'Order Received';
$PREF{order_email_top_intro}				= '<h1>Order Received:</h1>';
$PREF{order_email_items_intro}				= '<h2>Items Ordered:</h2>';
$PREF{order_email_user_intro}				= '<h2>User Information:</h2>';
$PREF{send_copy_to_userEntered_email_address}		= 'yes';



# PREFs Section 11: File-List Configuration.
############################################################################
# You can have thumbnails displayed for files that are images.  Note that
# if your server has GD but not ImageMagick, you won't be able to use
# thumbnails or rotation for bitmap images (*.bmp) because GD does not
# support them.
#
# The thumbnails are created automatically and cached in a hidden .fcimages
# folder.  To force the regeneration of the thumbnails (i.e. update the
# cache) for a given folder, pass ?makethumbs=1 on the URL.  (Subject to
# security settings in PREFs Section 03.)
#
# The thumbnail size is specified according to ImageMagick's rules, namely:
# by default, the width and height are maximum values. That is, the image 
# is contracted to fit the width and height value while maintaining the 
# aspect ratio of the image. Append an exclamation point to the size to 
# force the image to exactly the size you specify.
#
# If only the width is specified, the width assumes the value and the 
# height is chosen to maintain the aspect ratio of the image. Similarly,
# if only the height is specified (e.g., 'x150'), the width is chosen to
# maintain the aspect ratio.
#
# If your server has GD but not ImageMagick, then the size rules are the
# same except that if both width and height are specified, then they are
# treated as absolute values, not maximum values, and the exclamation
# point has no effect.
#
$PREF{enable_image_thumbnails_in_filelist}		= 'yes';
$PREF{enable_folder_thumbnails_in_filelist}		= 'yes';
$PREF{visitors_can_toggle_thumbnails_on_and_off}	= 'yes';
$PREF{image_thumbnails_on_by_default}			= 'yes';
$PREF{folder_thumbnails_on_by_default}			= 'yes';
$PREF{filelist_thumbnail_size}				= '130x130'; # 'WxH', in pixels.
$PREF{filelist_thumbnail_dir_name}			= '.fcimages';
$PREF{filelist_thumbnail_style}				= 'border: 1px solid #000;';
#$PREF{prefix_for_thumbnailed_dir_names}		= qq`<b>Album:</b> `;
$PREF{filelist_thumbnail_image_extensions}		= '\.jpg$|\.jpeg$|\.png$|\.gif$|\.bmp$|\.jpe$'; # regular expression.
$PREF{rotatable_image_extensions}			= '\.jpg$|\.jpeg$|\.png$|\.gif$|\.bmp$|\.jpe$'; # regular expression.









# PREFs Section 12: Database Setup.
############################################################################
# If you're using any FileChucker features that require a database, then
# you'll need to configure it here.  The database name can optionally have 
# a :hostname after the database-name.
#
# The 2 tmpfls specified here must contain one line each, and the line
# must contain just one thing: your database username (in tmpfl2), and
# your database password (in tmpfl1).  The files are probably in your 
# DOCROOT, but if you'd rather specify them with absolute or relative
# paths (relative to this script, that is), then disable the _in_docroot
# PREF.
#
# The database user needs at least the INSERT and SELECT privileges, but
# depending on which DB-related PREFs you're using, it may need other privs
# too (see that particular PREF for the details).
#
$PREF{database_name}					= 'dbname:dbhost.mysite.com';
$PREF{tmpfl1}						= '/cgi-bin/p.cgi';
$PREF{tmpfl2}						= '/cgi-bin/u.cgi';
$PREF{tmpfls_are_in_docroot}				= 'yes';









# PREFs Section Z:  Misc Settings Not Usually Needed.
############################################################################
# By default, if your server's version of the CGI.pm module is >= 3.03,
# then we'll use its upload hook.  If it's older than 3.03, we'll do it
# manually, since older versions don't support the upload hook.  This 
# means we can't show the counts for number of files completed/remaining,
# but if your server has an ancient version of the CGI.pm module, then
# you have no choice.  Anyway, this PREF is in case the script isn't
# working for you, even though you DO have v3.03 or newer.  Setting this
# to 'yes' will force the manual behavior, and the only loss will be the
# aforementioned files-completed/files-remaining; the time and size will
# still display properly.
#
# When not using the upload hook functionality (either because you disable
# it here, or because FileChucker automatically disables it because your
# server's version of Perl doesn't support it) you can specify an amount
# of time to sleep during each pass of the while() loop that uploads the
# data from the client.  Decrease this value to make uploads faster; or
# increase it to cut down on the server load.
#
$PREF{disable_upload_hook}				= 'no';
$PREF{sleep_time_during_nonhook_uploads}		= 0.05; # in seconds.



# PREFs Section Z:  Misc Settings Not Usually Needed.
############################################################################
# FileChucker can use a database backend instead of diskfiles to store
# its temporary working data, if you'd like.  There's really no benefit
# of one method over the other (and on servers that perform write-caching,
# thus preventing the progress bar from working properly, the database 
# backend doesn't actually work around the problem, as we had thought it
# might).
#
# For this to work, your database username (in PREFs Section 12) needs 
# privileges for INSERT, UPDATE, SELECT, DELETE, and CREATE.  If you're
# paranoid and don't want to give it CREATE privs, then see the
# create_db_table_for_temp_data() function to find out the column types,
# so you can create the table manually.
#
$PREF{use_database_for_temp_data}			= 'no';
$PREF{table_name_for_temp_data}				= 'temp_upload_data';



# PREFs Section Z:  Misc Settings Not Usually Needed.
############################################################################
# You probably don't want the temp-data entries filling up your DB since
# they don't actually contain any useful information after the upload is
# complete.  But you can disable this if for some reason you want them kept.
# Note that this doesn't delete the uploaded files; they aren't stored in
# the database.
#
$PREF{purge_temp_data_immediately}			= 'yes';



# PREFs Section Z:  Misc Settings Not Usually Needed.
############################################################################
# If you're using FileChucker in a way where it doesn't make sense for the
# default page to be the uploader, you can change that here.  Currently the
# options are 'uploader' and 'filelist'.
#
$PREF{default_page}					= 'uploader';



# PREFs Section Z:  Misc Settings Not Usually Needed.
############################################################################
# If you want to use Ko instead of KB, etc, you can set those labels here.
# Note that you should not change these to Kb or Mb, since lowercase-b means
# "bit", not "byte", so all the displayed values would be incorrect.
#
$PREF{KB}						= 'KB';
$PREF{MB}						= 'MB';



# PREFs Section Z:  Misc Settings Not Usually Needed.
############################################################################
# Specify the length of the serial number and whether it should be all
# numbers or can also contain letters.  A length less than 10 is NOT a
# good idea because the smaller the value, the better the chance that
# there will be collisions between simultaneous uploads.  But even 10
# is pretty low; 20 is better, and 30 is the default.
#
# You can also choose to use a hash for the serial, in which case the
# length and use_letters options have no effect.
#
$PREF{length_of_serial}					= 30;
$PREF{use_letters_in_serial}				= 'yes';
$PREF{use_hash_for_serial}				= 'yes';