FileChucker

Uploader with Progress Bar, File Manager & Multi-User Support

At A Glance:

FileChucker screenshot 1 of 3

FileChucker screenshot 2 of 3

FileChucker screenshot 3 of 3

Contents

About
Live Demo
Features
FAQ
Download
Instructions: Apache on Mac/Linux/BSD
Instructions: Apache on Windows
Instructions: IIS on Windows
Performance
Support
Changelog

About

FileChucker is an AJAX-based web application that lets you accept file uploads on your own website.  It's simple to install, packed with features, fully configurable, nice looking, and very handy for when you want to share files with anyone, or accept files from anyone.  And during uploads FileChucker shows a progress bar & table, so the user knows how much time is left before the upload is complete.

FileChucker can also function as a full-fledged online file manager for your server: it can allow moving/renaming/deleting of uploaded files & folders right in the browser.  Of course these features are configurable and password-protectable so you can customize FileChucker however you'd like.

FileChucker works in all major browsers (Firefox, Safari, Google Chrome, IE, Opera), and runs on virtually any server, with no programming required.  It's known to run on Dreamhost, Bluehost, Media Temple, 1and1, GoDaddy (with their Linux hosting plans), Network Solutions, Yahoo, iPower, HostGator — name any major hosting company and there are probably quite a few FileChucker installations on it.  And FileChucker integrates easily into WordPress, Joomla, and any other PHP page, yet it also allows you to upload huge files — working around PHP's upload size limits — because it's written in Perl rather than PHP.

Live Demo

You can try out the FileChucker Live Demo right now.

Features

  • Easy integration with WordPress, Joomla, and any other PHP page on your site
  • Works around PHP's upload size limitations, allowing huge uploads on most servers
  • Share files that are too large for e-mail by simply uploading them and then sending the link to your friend
  • Real-time progress bar and time elapsed/remaining during uploads
  • Built-in password protection: two separate passwords allow "admin" and "member" access levels without usernames; or, integrate with UserBase or your site's existing login system
  • If you don't want to bother with passwords at all, FileChucker can also be configured to automatically create a private directory for each upload, perfect for single-use uploads; the private directory is optionally re-usable for new uploads by the user who created it
  • Integrates with CornerStore so you can quickly and easily sell products and services based on your uploaded files
  • E-mail notification of new uploads; can be sent to the webmaster and/or to the person performing the upload
  • Create, move, rename, and delete files/folders on your server through the browser, functioning as a web-based FTP system or FTP replacement
  • Multiple folders/subfolders for uploads, optionally user-creatable
  • Can function as a photo gallery script, with automatic image thumbnailing, image rotation, and a grid-layout display of your photo albums and thumbnails
  • Supports custom folder permissions so you can specify read-only or read-write access for users/groups on a per-folder basis
  • Can automatically rename all uploaded files to remove any "unfriendly" characters, append a time/datestamp, or rename to a completely custom format that you specify
  • Logs information about each upload, like uploader's IP address, hostname, browser & operating system
  • You can configure unlimited custom form fields anywhere on the upload form, so your users can enter comments or information about the file(s) they're uploading; supports text fields, radio buttons, checkboxes, drop-down lists
  • Can integrate with your site's login framework to store each user's uploads in his own directory automatically, and after an upload, can redirect to a page that you specify
  • Restrict what kinds of files can be uploaded and/or displayed based on file extension
  • Has a built-in human test to prevent spambot abuse (sometimes called a CAPTCHA system; "CAPTCHA" is (TM) by Carnegie Mellon University)
  • Works on a standard server or a secure server (https://)
  • Supports i18n and l10n (internationalization and localization) in most areas of the application, so it can be translated into other languages by simply modifying the settings containing the text strings
  • Adjustable max upload size (in bytes), up to as large as your server can support (typically multiple gigabytes)
  • Adjustable user quotas
  • Can upload one or multiple files, up to whatever limit you specify
  • Fully customizable via preferences that you can adjust
  • Check out the preferences file in the free version to see some of the adjustable features and documentation.

Download

You can download the FileChucker Free version and install it on your site right now.  FileChucker Free has a fully-functional upload page with multi-file support, and a basic download page.  For advanced features including password protection, email notifications, custom folder permissions, private folders, custom form fields, database storage, and a full-featured download page with copy/move/delete support, image/video thumbnails and much more, get the FileChucker Personal or Business license.

Purchase

To get the full version of FileChucker, please choose your license type below.  Personal licenses are only for non-business websites.  The 3- and 10-site licenses are for when you want to install FileChucker on multiple different websites, and they include big discounts!  All licenses are lifetime licenses: you pay only once, and it's yours forever.  And all licenses include free tech support, free upgrades for 1 year, and discounted upgrades for life.

FileChucker Full Version:
1-Website License - Personal
$19.99
1-Website License - Business
$39.99
3-Website License - Business
$119.97
$89.99
10-Website License - Business
$399.99
$249.99
Instant credit card payments through PayPal.
No sign-up required!
FileChucker Installation Service:
Let us install it for you.
$29.99

Quick Instructions for Most Servers (Apache on Linux, Mac OS X, BSD)

Unzip your filechucker.zip file, and then upload the contents of the www.example.com folder onto your website.  Then visit the following address, replacing example.com with your own domain name:

www.example.com/cgi-bin/filechucker.cgi

If that works, then FileChucker is installed properly.  You should now read the FAQ.

If nothing works, read the full instructions.

Quick Instructions for Apache-on-Windows Servers

If your server doesn't already have Perl installed, download and install the free ActivePerl.  You may need to reboot after installing it.  Open a command prompt and type   perl -v   and if you get some output about Perl and its version info, you should be all set.

If you had to install Perl, you may also want to install the DBD::MySQL Perl module (if you want to use any of FileChucker's optional database-based features), and the MIME::Lite module (if you want to use any of the email features), by opening the Run dialog or a command prompt and then typing ppm install DBD-mysql (or ppm install MIME-Lite).  Or you can run just the ppm command by itself to use the graphical installer.

Now follow the regular Apache instructions.

Quick Instructions for IIS-on-Windows Servers

If your server doesn't already have Perl installed, download and install the free ActivePerl.  You may need to reboot after installing it.  Open a command prompt and type   perl -v   and if you get some output about Perl and its version info, you should be all set.

If you had to install Perl, you may also want to install the DBD::MySQL Perl module (if you want to use any of FileChucker's optional database-based features), and the MIME::Lite module (if you want to use any of the email features), by opening the Run dialog or a command prompt and then typing ppm install DBD-mysql (or ppm install MIME-Lite).  Or you can run just the ppm command by itself to use the graphical installer.

Unzip your filechucker.zip file, then open the www.example.com folder and move the contents of the cgi-bin folder into the upload folder.  Then delete the cgi-bin folder.  Upload the "upload" folder onto your website, then visit the following address, replacing example.com with your own domain name:

www.example.com/upload/filechucker.cgi

If that works, then FileChucker is installed properly.  You should now read the FAQ.

If nothing works, read the full instructions.

Full Instructions for Most Servers (Apache on Linux, Mac OS X, BSD)

Also available: instructions for IIS/Windows and Apache/Windows
Want us to install it for you?  Just purchase the FileChucker Installation Package.  We also provide customization and integration services -- just ask!

Note I: Do not edit the filechucker.cgi file unless absolutely necessary; instead, edit filechucker_prefs.cgi for all your customizations.

Note II: if you are using Windows on your desktop, and when you open the *.cgi file, the lines all appear to be crunched together, try opening it in Wordpad (not Word) instead.  In Wordpad, save the file; this should fix the line-endings so the file's contents appear correctly in other editors like Notepad.

On your website:

  1. First, complete the quick instructions.
  2. Set the permissions on /cgi-bin/filechucker.cgi (aka, chmod it) to world-readable and world-executable, that is, a+rx or mode 0755.  Do NOT use 0777.
  3. Set the permissions on the /cgi-bin/encdata/ directory to world-readable, -writable, and -executable, that is, a+rwx or mode 0777.
  4. Set the permissions on the /upload/files/ directory to world-readable, -writable, and -executable, that is, a+rwx or mode 0777.
  5. Now visit yoursite.com/cgi-bin/filechucker.cgi in your browser and FileChucker should be working properly.
  6. If you get an Internal Server Error, it's most likely a permissions problem.  See this page for more details.
  7. Read the FAQ.

Now FileChucker is ready to run, and you can access it by going to yoursite.com/cgi-bin/filechucker.cgi (or yoursite.com/upload/ if your server supports it).

Full Instructions for Apache-on-Windows Servers

Also available: instructions for Apache/[Linux|Mac|BSD] and IIS/Windows
Want us to install it for you?  Just purchase the FileChucker Installation Package.  We also provide customization and integration services -- just ask!

Note I: Do not edit the filechucker.cgi file unless absolutely necessary; instead, edit filechucker_prefs.cgi for all your customizations.

Note II: if you are using Windows on your desktop, and when you open the *.cgi file, the lines all appear to be crunched together, try opening it in Wordpad (not Word) instead.  In Wordpad, save the file; this should fix the line-endings so the file's contents appear correctly in other editors like Notepad.

On your website:

  1. First, complete the quick instructions.
  2. Now visit yoursite.com/cgi-bin/filechucker.cgi in your browser and FileChucker should be working properly.
  3. If it doesn't execute or you get errors, you may need to change the first line of the filechucker.cgi file from #!/usr/bin/perl to either #!perl or #!c:\path\to\perl.exe
  4. If it doesn't execute or you get errors, you may need to rename the script and its prefs file from a .cgi extension to a .pl extension.
  5. If you get errors about FileChucker being unable to delete something from the encdata or files folder, you may need to set a "Delete" bit on the folder's properties.
  6. Read the FAQ.

Now FileChucker is ready to run, and you can access it by going to yoursite.com/cgi-bin/filechucker.cgi (or yoursite.com/upload/ if your server supports it).

Full Instructions for IIS-on-Windows Servers

Also available: instructions for Apache/[Linux|Mac|BSD] and Apache/Windows
Want us to install it for you?  Just purchase the FileChucker Installation Package.  We also provide customization and integration services -- just ask!

Note I: Do not edit the filechucker.cgi file unless absolutely necessary; instead, edit filechucker_prefs.cgi for all your customizations.

Note II: if you are using Windows on your desktop, and when you open the *.cgi file, the lines all appear to be crunched together, try opening it in Wordpad (not Word) instead.  In Wordpad, save the file; this should fix the line-endings so the file's contents appear correctly in other editors like Notepad.

On your website:

  1. First, complete the quick instructions.
  2. Now visit yoursite.com/upload/filechucker.cgi in your browser and FileChucker should be working properly.
  3. If it doesn't execute or you get errors, you may need to complete one or more of the following steps (most are not necessary on most IIS servers, so try one at a time):

    Rename the script and its prefs file from a .cgi extension to a .pl extension.

    Change the first line of the filechucker.cgi file from #!/usr/bin/perl to either #!perl or #!c:\path\to\perl.exe

    For the /upload/encdata and /upload/files folders, do the following: right-click on the folder, choose Properties, and go to the Security tab.  Find or add the IUSR_computername account, and give it "Full Control".  This account is sometimes called the Internet Guest Account.

    Run the inetmgr command and change the CGI web service extension from "prohibited" to "allowed".  If your Web Service Extensions list doesn't include an item for Perl CGI scripts, then add a new one (named something like "Perl CGI", or "CGI Scripts", etc -- the name is not important), and for its "Required Files", enter C:\Perl\bin\perl.exe "%s" %s (adjust the path as necessary for your Perl installation)

    Run the inetmgr command and right-click on the website and choose Properties.  Go to the "Home Directory" tab, then to "Application Settings", and set "Execute permissions" to "Scripts and Executables".

    Run the inetmgr command and go to "Application Settings" then "Configuration", and add an application extension for .cgi (and .pl) with the executable set to: C:\Perl\bin\perl.exe "%s" %s (adjust the path as necessary for your Perl installation)

    Run the inetmgr command and right-click Default Web Site (or your site's name, if different).  Then click New -> Virtual Directory and follow the prompts, entering "upload" as the name of the virtual directory, and choosing FileChucker's upload folder (c:\inetpub\wwwroot\upload\ by default) for the path.  For Access Permissions, check (enable) the Read, Run Scripts, and Execute boxes.  When finished, right-click the new virtual directory and choose Properties -> Application Configuration -> Mappings, and make sure there's a .cgi (and/or .pl) extension there, mapped to the C:\Perl\bin\perl.exe "%s" %s command (or your server's path to perl.exe).

    If you get errors about FileChucker being unable to delete something from the encdata or files folder, you may need to set a "Delete" bit on the folder's properties.

    Create the c:\temp\ folder if it does not exist; if this isn't possible, and you get errors or failures when you try to upload files, then set $PREF{disable_upload_hook} = 'yes' in filechucker_prefs.cgi.
  4. (Optional; recommended) You may want to disable directory-listing for your /upload/ directory; you can do this through inetmgr.
  5. (Optional; recommended) If your server runs PHP, then you should disable it for your /upload/files/ directory, so that visitors can't upload PHP applications and modify the files on your server.  (FileChucker does disallow the uploading and listing of dangerous file extensions including .php by default, but disabling PHP execution for your uploads folder will further strengthen your installation's security.)
  6. (Optional) To increase IIS's CGI timeout, which will prevent large uploads if set to a low value, you need to set the "CGITimeout" metabase value to a large number, like 5000 or 10000 or more.  There are several ways to adjust this value.  One is to use the Metabase Explorer, from the IIS Resource Kit.  Another is to run the inetmgr command, right-click "Local Computer", choose Properties, then check "Enable Direct Metabase Edit";  then edit the file c:\windows\system32\inetsrv\metabase.xml in a text editor (you may need to use Notepad, not Wordpad), find the CGITimeout setting, and change it to a larger value.
  7. (Optional) FileChucker's image features (thumbnails, rotation) require an image-processing library like GD or ImageMagick.  To install the GD Perl module, open a command prompt and run the command ppm install http://theoryx5.uwinnipeg.ca/ppms/GD.ppd or ppm install http://cpan.uwinnipeg.ca/PPMPackages/10xx/GD.ppd one of which should work depending on your version of Windows and ActivePerl.

    To install ImageMagick, go to www.imagemagick.org and download & install the binary release for Windows.  Then read this FAQ item for instructions on setting $PREF{convert_command}.
  8. Read the FAQ.

Now FileChucker is ready to run, and you can access it by going to yoursite.com/upload/filechucker.cgi (or yoursite.com/upload/ if your server supports it).

Performance

First, it should be noted that FileChucker itself imposes no limits on the amount of data that can be transferred (except whatever limit you specify in your setting for $PREF{sizelimit}).  FileChucker also does not place any limit on the speed of an upload.  If you are having trouble with uploading large files, or with uploads going really slow, the problem is in your network, or somewhere else in your server's hardware or software configuration.  Many FileChucker users on many platforms (Windows, Linux, IIS, Apache, OS X Server) are uploading files sized in the hundreds of megabytes, so the problem is not within FileChucker.

In a test upload of a 700MB file across a 100mbit LAN, the transfer ran at about 5MB/sec, requiring about 2.5 minutes to complete.  After the actual data-transfer was complete, the server spent ~50 seconds processing the file (CGI.pm's internal processing) before the script finished running. (FileChucker now has the ability to avoid this extra processing time altogether, as long as your server is running a relatively recent Perl distribution.)  The server was a Dell Dimension 1100 desktop system, with an Intel Celeron 2.53GHz CPU (256 KB cache, 5061.56 bogomips), 512MB RAM, 1GB swap, and a standard 7200RPM ATA IDE disk.  The server was running Apache 2.0.54 with a fairly standard installation.  During the upload, the server's RAM and swap usage did not increase significantly (probably a few KB or a few tens of KB), because the uploaded file got streamed to disk (to a temporary file) by CGI.pm.  This is why the server needed to spend ~50 seconds processing the file after the upload was complete: it was decoding the raw POST data from the temporary file into the actual final destination file.  (Again, FileChucker no longer needs to do this.)

In a second test upload on the same server as above, a 1.4 gigabyte file took about 5 minutes to upload, and when the data finished transferring, the server spent just under 2 minutes doing POST-processing before the script finished. 

The one thing we've seen that's helped to increase performance during file-uploads (aside from faster hardware and/or a faster network link) is to make sure the server has a recent version of the CGI.pm Perl module. In FileChucker, if you enable the debugging PREFs, then visit your server's FileChucker installation in your browser and pass ?debug on the end of the URL, then view the page's source-code, at the bottom you'll see a bunch of debugging information inside of an HTML comment.  One of the items near the top of this info is the CGI version that your server is running.  The current version is somewhere around 3.20 or greater; if you're in the 2.xx series, or even the low 3.0x series, then upgrading your Perl installation (which will upgrade your CGI.pm module) may give you better performance during uploads.

If you want to upload files larger than 2 gigabytes, then you can't use Apache 1.3.x or 2.0.x.  You need to use Apache 2.2.x, as explained on the "New Features in Apache 2.2" page:

Large File Support

httpd is now built with support for files larger than 2GB on modern 32-bit Unix systems.  Support for handling >2GB request bodies has also been added.

Support 

If you need any help with FileChucker, please complete the following steps in order:

  1. Make sure you've followed the installation instructions.
  2. Make sure you've read the FAQ.
  3. If you're getting an Internal Server Error, read the Internal Server Error page.
  4. If you're getting errors about missing Perl modules, read the installing Perl modules page.
  5. The troubleshooting page has some FileChucker-specific solutions that may help.
  6. If you still need help, you can contact us.  Be sure to send us the full URL to the script on your server.

ChangeLog

v4.99e (20141022):

  • New include_simple_formfield_format_on_redirection_qs, so that in case you're redirecting to a non-FC upload confirmation page, you can access simple name=value variables on the URL, rather than having to parse FileChucker's special numbered-variable format.
  • New disable_multiple_files_in_one_element_for_mobilesafari setting, since MobileSafari currently has a bug that prevents video files from uploading if the file field has multi-file support enabled (as any modern file field will, nowadays...).
  • New groupsallowed_settings_override_custfolderperms_for_file_downloads setting, for cases where you want to enable custom folder permissions so that only your specified users/groups can browse folders, but still allow individual file download links to be public (e.g. links sent in notification emails).
  • Removed a bunch of really old, virtually-never-used code, and optimized a bunch of other code.
  • Bugfix: the fancy new AJAX file-delete feature would mysteriously fail if you were in the top level (not in a subfolder) and you tried to do a deletion using the checkboxes instead of the options->delete link.

v4.99d (20140523):

  • Bugfix: we now only attempt to load the SFTP module if you've enabled a feature that requires it (e.g. use_sftp_when_transferring_to_another_server), to prevent errors on servers where the module is missing.

v4.99c (20140513):

  • Bugfix: removed some development code that was inadvertently left in the previous version.

v4.99b (20140513):

  • New $PREF{email_hello_domain} setting, which defaults to your domain name, which is used in email headers -- previously this was just defaulted to "localhost.localdomain"; this change *should* make it less likely that any app-based emails get flagged as junk/spam by email servers, or services like Gmail.
  • New scroll_progress_bar_into_view setting, in case your upload form is really big, which previously might have made the upload progress bar scroll out of view when the user clicked the Begin Upload button.
  • New optgroup setting for custom drop-down fields on the upload form, so you can organize large drop-downs into groups.
  • The ftp_files_to_another_server feature now also supports SFTP.
  • On embedded installations where your page has an onload call in its body tag, which prevents FileChucker's own onload code from running, we now automatically detect that and run our code on the fly when the upload begins, rather than displaying an error about enabling multiple onload actions, as before.
  • Switched some of our nonces from md5 to sha256, and we now include the Digest::SHA::PurePerl module, for servers missing Digest::SHA, to guarantee support.
  • New _maxlength setting for custom form fields.
  • The code that auto-updates our static CSS and JS files when you change your prefs now also detects changes to the script itself, and does an update then.
  • Bugfix: when using FileChucker with your own custom form field code, sometimes FileChucker would fail to see some of your file input fields, if you had a screwy form where the fields had duplicate names.

v4.99 (20140311):

  • New enable_folder_passwords feature, which will likely have multiple uses in the future, but currently allows you to set folder-wide passwords that override any per-file passwords on files within that folder.
  • New groups_allowed_to_bypass_perfile_passwords feature, to allow any group(s) you choose to download files without needing the passwords, whereas previously only admins could do this.
  • New treat_sendmail_closing_error_as_failed_delivery setting, required on some servers where sendmail doesn't act quite right so we couldn't tell for sure whether a message had been successfully sent.
  • We now automatically internally disable the multidownload feature when the per-file password feature is enabled, rather than requiring it to be manually disabled, since multidownload would bypass any per-file passwords.
  • New Test Email Sending link on the admin menu, for easier access to the ?do_email_test page.
  • The email test page has been greatly improved, with a more detailed explanation of which delivery methods were tried, which prefs need to be adjusted in the event of a failed delivery, notes about required Perl modules and SMTP auth, and where to find more help.
  • We're now using the mysql_auto_reconnect feature again, after a longstanding bug in that Perl module was apparently fixed, meaning we no longer have to rely on our own internal workaround for dropped MySQL connections, which is good since it only worked about 99% of the time -- it was still possible for a dropped connection to cause an error that we couldn't detect, if the drop occurred at just the right (wrong) time.
  • Bugfix: when email delivery fails and we retry 2 times before giving up, if all 3 attempts failed, our error message said "attempt 4 of 3" instead of "3 of 3".
  • Bugfix: when using the per-file passwords feature, we would sometimes get stuck in a redirect loop, preventing the file from downloading.

v4.98 (20140224):

  • Re-organized the prefs file to move shared prefs (mostly styling and text strings) to a single section, to make multi-app installations easier to configure.
  • Bugfix: on Apache/Windows servers, our uploaded_files_dir was sometimes set incorrectly.

v4.97 (20140210):

  • Nicer, quicker delete function: deleting files/folders is now done via AJAX, so the page does not have to be reloaded afterwards.
  • The nice short ?show URLs introduced in the previous update are now used in more (most) of FileChucker's internally-generated links.

v4.96 (20140126):

  • New ?show=foo URL variable for nicer URLs.  Previously, where you would have had www.example.com/upload/?action=listfiles&path=foo, the URL is now www.example.com/upload/?show=foo.  It works for files too: instead of www.example.com/upload/?action=viewer&path=foo&file=bar.jpg, you can use www.example.com/upload/?show=foo/bar.jpg.
  • New enable_perfile_passwords_via_filelist feature, allowing you to set per-file passwords on previously-uploaded files (which will then be required of anyone trying to view/download the file), in addition to the previously-available per-file passwords feature where the password is set during upload, which is also still available.
  • New groups_allowed_to_view_2nd_level_of_download_page.  This can be used in conjunction with the groups_allowed_to_view_top_level_of_download_page and groups_allowed_to_view_download_page features to create "public" yet relatively secure download folders.  For example, if you set groups_allowed_to_view_download_page to public, but set the top_level and 2nd_level prefs to admin, then the only way a member of the public can view anything is if it's in a very specific subfolder whose address you intentionally give to him.  E.g. if you have /upload/files as your default upload/download location, then create /upload/files/private and /upload/files/private/JohnnyExample-YYYYMMDD-C29A4BD1E3, then you could send Johnny the link to the JohnnyExample-YYYYMMDD-C29A4BD1E3 folder and he could access it, yet he couldn't access the parent folder ("private/") nor any other subfolders (because he wouldn't know their names without guessing or brute-forcing it, which, for such long folder names, would be impractical).
  • New nicer-styled emails by default instead of plain-text emails, and new email_wrapper_head and email_wrapper_foot prefs to easily apply this style to any app-generated emails, and easily tweak it.
  • New static_css_url and static_js_url settings, and a new feature that creates and updates them automatically, so that embedding FileChucker into a page in your website is easier and loads faster.
  • New enable_targeted_autodelete feature, to allow auto-deletion of files and/or folders based on arbitrary rules including pattern matching, specific subfolders, age, etc.
  • New enable_comments_on_folders feature, in addition to the previously-available file comments feature, so visitors (or just you) can leave comments on folders in addition to files.
  • New script_redirect and custom redirect features for the file_links_in_*_go_to settings, for more flexibility in specifing how your download links work and where they go.
  • The options menu on the download page is now a little nicer, with tighter text and a drop shadow.
  • The are-you-sure-you-want-to-delete-this prompts on the download page now include the name of the file/folder in question.

v4.95 (20131126):

  • New mail-retry feature, so that when we try to send an email but it fails, we'll automatically retry 2 times right away.  Of course this can't overcome sending errors that are due to a misconfiguration of your prefs, but it helps greatly whenever there's a temporary glitch with a mailserver, which happens surprisingly often.
  • New $PREF{log_all_sent_mail} feature, including a viewer so you can browse all the mail sent by FileChucker.  Helpful for debugging mail-sending problems, or if you just like to keep a log of all outgoing mail.
  • FileChucker's internal mail-sending function now allows the To: parameter to be a list of multiple recipients, which means in any pref/feature where you specify a recipient email address, you can now include multiple recipients (of course many such prefs/features already supported this in a different way, but now it works for all emails).
  • Bugfix: the create_resized_copies_of_uploaded_images feature, when set to use relative pathnames, would ignore any specified subdirectory on the upload when creating the copies; now it mirrors the upload subdir into the copy directory.
  • Bugfix: enabling skip_database_table_creation on an installation that had been updated from a previous one would result in wrong table names being used (no data would be lost, but you'd be using new empty tables because their names would be different).

v4.94 (20131026):

  • Performance boost: decreased the number of iterations in the expand_custom_vars_in_prefs___inner sub (used for allowing prefs to be set with values of other prefs, i.e. nested) in a way that can cut a few hundred MS off our execution time without any other effect on the app.
  • Performance boost: new skip_database_table_creation pref, which can speed up load time quite a bit depending on your server and database server, since technically we only need to check/create the tables the first time we run and once after each update.
  • Improved blocking of XSS attack attempts (of course most browsers now block such attacks at the browser-level anyway).
  • New max_file_size_for_public, _members, and _admins settings, similar to the existing sizelimit_for_public (etc) settings, except per-file instead of per-upload.
  • New runtime-alert feature ($PREF{runtime_emailalert_time_limit}), to send you email alerts when FileChucker's runtime exceeds a certain number of seconds.  This can alert you to problems such as server overload, corrupt uploaded files, or any other issue that might cause the app to take too long to run.  There's a separate setting for uploads ($PREF{runtime_emailalert_time_limit_for_uploads}) since those will often take longer for large files, and which isn't a problem in that case.
  • New encodable_app_template_static_css and _js prefs, for use with the encodable_app_template_file feature, for improved performance when using the template (avoiding 2 calls to the script by using static files instead).
  • Reorganized email prefs and improved their documentation.
  • New $PREF{webmaster_email_address} and $PREF{app_email_address} settings to serve as defaults for other email prefs.
  • New enable_database_connection setting, for situations where you're using custom code that requires a database, but aren't using any of FileChucker's built-in database-using features, which would enable the database connection automatically.
  • New max_image_dims_to_resize setting, which causes FileChucker to skip resizing images (e.g. for thumbnails) that are very large in terms of their resolution (but not necessarily large in file size, which the existing max_image_size_to_resize setting would catch), since trying to resize such images can quickly consume all of the server's RAM.
  • New static_hostname setting, for servers on networks where there are long delays for hostname lookups, which would previously cause FileChucker to take a long time to load, since it had to wait for the lookup.  Now you can manually set your hostname and skip the lookup.
  • New code to check for invalid/non-standard/otherwise-screwy remote IP addresses and fix them when possible.
  • New code to set UserBase's table names automatically, rather than from the userbase_prefs.cgi file, for installations that are integrated with UserBase.
  • Removed note about 7-Zip from the error message we show when a multi-file download fails due to the zip file not existing (the note is for Windows users and explains that they'll need to install a zip command such as the one from Info-ZIP or 7-Zip, but it appears current versions of 7-Zip don't work when called this way).
  • Various small improvements to our database-viewer pages.
  • Bugfix: when using the $PREF{admin_user_present} setting (not used by default nor in most installations) and setting it to '%ENV{PHP_ENC_ISADMIN}' as suggested in the prefs file, it would always evaluate to true, because of a bug in the way we were interpolating the %ENV vars.  This bug would also apply to any other prefs set to strings containing only a single (undefined) %ENV variable, but there aren't any other such prefs by default.
  • Bugfix: we no longer set the PATH env var to a sane Linux/Unix value if we're running on a Windows server.
  • Bugfix: in some error cases we displayed a vague "Message expired" error; now we'll display more about what really went wrong.
  • Bugfix: the Upload Complete page's "Return to upload page" link would be a broken link (missing a question-mark) in some rare cases.
  • Bugfix: when using a filechucker_prefs_extra.cgi file (which isn't used by default), and changing certain $PREF{upload_email_template_for_*} email settings within it, those settings would be ignored, with the default versions of the prefs from the main prefs file used instead.
  • Bugfix: we now use Javascript to add the 'multiple="multiple"' attribute to the file upload fields (which is what tells the browser to enable the multi-files-within-one-element feature) instead of having it there in the HTML code by default, to appease the validator.  As a consequence there is also a new allow_multiple_files_in_one_element pref for the rare case where you'd want to disable this feature.
  • Bugfix: moved the onload for the upload progress bar from HTML to Javascript to appease the validator.
  • Bugfix: minor and inconsequential change to a comment within our CSS to appease the validator.
  • Bugfix: replaced a few ampersands with their HTML equivalents to appease the validator.

v4.93 (20130831):

  • Small prefs change: added note to the top of the file pointing out that most prefs are optional and can be left at their default values.

v4.92 (20130510):

  • Bugfix: the previous update caused a syntax error on older versions of Perl, so rolling it back for now.

v4.91 (20130505):

  • New use_unicode_in_sql_safety_checks feature, necessary on some servers with some languages.

v4.90 (20130429):

  • New comments feature, allowing visitors to post comments on previously-uploaded files.  Useful in situations where you're using FileChucker as a photo album, or for receiving notes from your clients on their uploaded files, or for sending notes to clients regarding their uploaded files, etc.  Includes email notification of new comments, and optional admin moderation of new comments.  See $PREF{enable_comments}.
  • New uploaded_files_dir___admin setting, for rare situations where you've got the normal uploaded_files_dir being set via some kind of user variable, and you want to specify a different directory for admin (non-user) access.
  • New admin_user_present setting for when integrating with a third-party login system, as another way to signify admin presence.
  • FileChucker can now display in-page preview images for TIFF files, by creating JPG previews of them, since most browsers can't display the TIFF format.

v4.89 (20130129):

  • The $PREF{encodable_app_template_file} feature no longer requires that you put the %%css%% and %%js%% variables in your template file; we'll just automatically insert our CSS and JS either right after the <head> tag, or right before the </head> tag.
  • New $PREF{force_nocache_on_all_output} setting, required only on rare goofy servers that automatically cache our app output on the *server* side.
  • New code to block potential XSS attacks.
  • Bugfix: formfields excluded from the upload form via the $PREF{formfield_NN_only_for_these_groups} setting were still being included in notification emails; now they're excluded there too.

v4.88 (20120919):

  • New $PREF{use_NetSMTP_for_email} setting, needed only for a small percentage of (cranky) email servers.
  • For upload notification emails, you can now specify a Reply-To address, in addition to a From address.
  • If you're using the $PREF{encodable_app_template_file} feature (which is basically an alternate way to do an embed), you can use the new $PREF{encodable_app_template_replacement_001} settings to specify text to be replaced within the template file, e.g. replacing a standard header image with a different one for each logged-in user.
  • New rawname URL variable for the Upload Complete page (and stored in the upload info table if enabled), to access the filename as submitted before we applied any of your specified modifications.
  • New $PREF{email_link_on_options_menu___folder} setting, to easily email a link to any folder on your download page.

v4.87 (20120806):

  • New multi-item move feature: heretofore you could only move files and folders one at a time; now you can use the checkboxes and the Actions Menu at the bottom of the downloads page to move multiple files/folders at the same time.
  • New $PREF{preview_videos_in_viewer_mode} setting, so that in the preview/slideshow viewer, where images are shown as web-sized versions with links to the full version, videos are now shown the same way (as opposed to just showing a link to the video file, as we do for non-previewable file types like text files).
  • New $PREF{enable_username_from_cgi_script} feature.
  • New $PREF{title_text} setting to specify the title that appears in places where HTML isn't allowed, such as the browser's title bar.
  • New settings $PREF{file_upload_field_N_is_required} (where N is 2, 3, 4, etc) for installations with multiple required file fields.
  • New setting $PREF{disable_upload_iframe_for_these_user_agents}, to work around bugs in particular browsers.
  • For drop-down form fields populated from SQL queries, the allowed query format is more flexible (e.g. allowing SELECT DISTINCT in addition to just SELECT).
  • New $PREF{formfield_NN_maxlength} feature, to limit the length of input values in single-line form fields.
  • New $PREF{hide_filenames_in_filelist} feature, used for example when all your uploaded files are images or videos and thus will have thumbnails, and you want just that small image displayed with no text.
  • New $PREF{hide_parent_folder_link_in_file_list} setting.
  • Removed all the old style/theme code, CSS, and prefs (e.g. $PREF{light___filelist_row_hover_bgcolor}) in favor of a new simpler system with just two themes: light and dark.
  • Removed the $PREF{enable_individual_item_viewer_mode} setting (it had actually been ignored since v4.66 in favor of the new file_links_in_ settings in that version).
  • New $PREF{database_tablename_prefix} setting (defaults to "fc_"), for sites with multiple FileChucker installations where you want to use separate database tables for each one.
  • Renamed $PREF{file_and_dir_info_table} to $PREF{pathinfo_table}, and changed its default value from "file_and_dir_info" to "pathinfo".
  • New $PREF{extra_sql_safe_characters} setting, in case you want to allow other characters to be stored in your database than the ASCII ones that FileChucker allows by default.
  • New $PREF{static_error_message} setting, in case (after you've got FileChucker all installed and configured) you want any error to display a simple static message (e.g. "Server Error") instead of a detailed error message.
  • New $PREF{server_handles_ip_addresses_incorrectly} setting, for servers that don't provide accurate/consistent identification of client IP addresses via environment variables.  This is unnecessary on 99% of servers, and it only affects certain error/confirmation messages that the app generates: normally we restrict these based on logged-in status, or IP address, but with this setting enabled, we'll allow the message to be shown with no restriction, but we'll also auto-expire it quickly to minimize the (already remote) chance that the message could be viewed by someone other than the visitor who generated it.
  • New $PREF{always_show_details_for_move_and_copy_operations} setting: normally we only display a results page for these operations if an error occurs, but with this setting we'll show the list of items successfully moved/copied.
  • Various CSS tweaks.
  • Reorganized some of the sections at the end of the prefs file.
  • We now support the Digest::SHA module, in addition to Digest::SHA1, for servers where the latter isn't installed.
  • New %QS hash to allow you to use variables from the URL's query-string within your prefs file (e.g. "%QS{foo}" will turn into "bar" if ?foo=bar is passed on the URL).
  • We now specify accept-charset="UTF-8" on our <form>s, which should resolve some internationalization issues.

v4.86 (20120416):

  • Simplified the embedding process so that the $PREF{print_full_html_tags} setting is no longer required.  Now when FileChucker is embedded within a different page, the full filechucker.cgi URL will continue to work properly as well.

v4.85 (20120404):

  • Now supports integration with CornerStore, so you can easily sell products and services based on the uploaded files in FileChucker.
  • Prefs added:
    groups_allowed_to_view_buy_links_db
    groups_allowed_to_edit_buy_links
    groups_allowed_to_create_buy_links
    groups_allowed_to_delete_buy_links
    integrate_with_cornerstore
    show_buy_column_in_filelist
    cornerstore_cgi_location
    cornerstore_buy_link_separator
    cornerstore_item_table_list
    cornerstore_buy_link
    file_and_dir_info_table

v4.84 (20120325):

  • For uploads containing multiple files and per-file form fields, there is now a link to auto-fill the form fields using the values from the fields on the previous file.
  • We now use accept-charset="UTF-8" on the upload form, which should allow unicode characters in form fields to be processed correctly.
  • Replaced $PREF{path_to_filelist_images} with $PREF{app_images_url} for standardization across multiple apps.
  • When server write-caching prevents the upload progress bar from working properly, the message displayed is more end-user friendly.
  • New $PREF{static_error_message} setting, in case you want to hide all real error messages and show a more generic/short/friendly error instead.
  • New $PREF{always_use_nonforking_code_when_sending_email} setting, which can help work around email issues on screwy servers.
  • Bugfix: sometimes a spurious "couldn't rmdir (delete) directory" would be displayed (when FileChucker was cleaning up old files/folders) because of the way we were checking for empty directories.
  • Bugfix: when using the custom folder permissions feature, any permissions set on the very top level (/) would fail to show up as inherited permissions when viewing the levels below it (though the actual permissions were still enforced correctly).
  • Prefs added:
    app_images_url
    always_use_nonforking_code_when_sending_email
    static_error_message
  • Prefs removed:
    path_to_filelist_images

v4.83 (20120130):

  • New $PREF{extra_header_output} to allow you to include a custom favicon, or to integrate with VisitorLog, etc.
  • You can now pass ?dirlist=foo on the URL to the upload page, to hide any folders in the "Upload to:" drop-down field (if enabled) that don't match foo.
  • New $PREF{enable_username_from_environment_variable} feature, which is just what it sounds like, for integration with non-UserBase login systems.
  • New $PREF{subgroup_*} settings (see below) to enable more fine-grained control over folder permissions when using UserBase's subgroup manager feature.
  • When using $PREF{store_upload_info_in_database}, there are now two new fields stored by default: rawname and extension.  rawname is the original filename from the client, before any serialization or $PREF{reformat_filenames_for_all_uploads} options, etc, are applied.
  • New $PREF{debuglog} setting to make debugging easier, especially on servers without decent built-in error logs, or where the host won't let you access the error log.
  • Bugfix: if you added more than 99 form fields to the upload form, only the first 99 would work properly.
  • Prefs added:
    enable_username_from_environment_variable
    username_envvar_name
    subgroup_owned_users_have_same_folder_perms_as_their_subgroup_manager
    subgroup_owned_users_can_read_the_userdir_of_their_subgroup_manager
    subgroup_owned_users_can_write_the_userdir_of_their_subgroup_manager
    hide_toplevel_userdir_shortcut_for_subgroup_owned_users
    extra_header_output
    debuglog

v4.82 (20111026):

  • New $PREF{show_myaccount_link} setting for when integrated with UserBase; this is in addition to $PREF{show_login_link}, which is now a dedicated login/logout link (in previous versions, it changed to a My Account link when integrated with UB).

v4.81 (20111026):

  • New method for detecting when the upload is complete in the iframe, which eliminates a ~1-2 second delay at the end of uploads before the Upload Complete message is displayed, and which also allows us to detect and display any server errors that occur during an upload.
  • We now cache any environment variables received from PHP, so that we're able to use them during POSTs (e.g. uploads).
  • The get_userdir_from_username and get_userdir_from_email prefs have been replaced by enable_userdir_from_login_system and userdir_template, which now also supports including the user's email address and user ID within the userdir value.
  • New $PREF{uploadbutton_id} setting, for situations where you're integrating with an existing complex form where it'd be a hassle to change the CSS ID of the upload button, so you can adjust it in FileChucker instead.
  • New $PREF{ignore_image_resizing_errors} setting, to suppress errors during thumbnail generation, which, on a server with a properly-functioning image module/library, are generally only caused by the occasional corrupt image file, which we can't do anything about anyway, so displaying an error is largely pointless.
  • New $PREF{css_shared} setting, for CSS that is common to multiple Encodable apps.
  • Bugfix: on some servers, small uploads and/or slow connections result in the write-caching error being displayed when it doesn't actually apply, so we now wait until we're at least a few seconds into the upload before displaying it.
  • Bugfix: on some servers, at the end of an upload, the upload size would appear to revert to a very small value, causing the time displays on the upload progress table to freak out; we now ignore any decreasing values for the size, so this issue no longer occurs.
  • Bugfix: with custom folder permissions enabled, viewing the permissions would result in an error on Windows servers.
  • Prefs added:
    enable_userdir_from_login_system
    userdir_template
    uploadbutton_id
    ignore_image_resizing_errors
    css_shared
  • Prefs removed:
    get_userdir_from_username
    get_userdir_from_email

v4.80 (20111006):

  • Bugfix: when using the human test (aka CAPTCHA) feature, we'd eventually display an error when auto-deleting the old human test images, because of an incomplete directory check.

v4.79 (20111005):

  • Bugfix: when deleting a directory, we would display a MySQL error if custom folder permissions were not enabled.

v4.78 (20110929):

  • We now include the version number in the prefs file too, to make things easier for those with multiple installations, and during updates/moves, etc.

v4.77 (20110901):

  • Changelog coming soon.

v4.76 (20110715):

  • Changelog coming soon.

v4.75 (20110609):

  • New $PREF{show_keep_me_logged_in_checkbox_on_login_page} setting, in case you want to disable that checkbox, which was previously always shown.
  • New $PREF{ignore_chosen_subdir_during_upload_if_new_subdir_entered} setting, for situations where you want any new subdirs to be forced into the top level, instead of inside an existing subdir.
  • Bugfix: we were failing to store upload info into the database for file-less form submissions (if both of those option were enabled).

v4.74 (20110501):

  • Changelog coming soon.

v4.73 (20110326):

  • Changelog coming soon.

v4.72 (20110321):

  • Bugfix: when integrated with UserBase, and pulling the login_url value from the UserBase prefs file, we'd set it to the wrong value if it was still set to the default of $ENV{SCRIPT_NAME} (setting it to filechucker.cgi instead of userbase.cgi).

v4.71 (20110319):

  • Bugfix: the pagination links on the filelist page were supposed to be hidden when they weren't needed (i.e. when the number of items is less than your num-items-per-page setting), but that wasn't happening.
  • Bugfix: the filelist page was displaying a "Buy" header (which is part of an upcoming feature still under development) when it shouldn't have been.

v4.70 (20110313):

  • When integrated with UserBase, FileChucker can now set its own login_url pref from UserBase's prefs file.
  • More changelog items coming soon.

v4.69 (20110126):

  • We now reject form submissions without files (unless you've specified to allow such submissions) on the server-side as well as the client side, to stop spambots that POST directly to the script without using the frontend.
  • Bugfix: a change in the previous version contained a bug that resulted in spurious permissions errors when not using custom folder permissions.

v4.68 (20110123):

  • Changelog coming soon.

v4.67 (20101231):

  • Changelog coming soon.

Older Changelog Items

Shopping Cart

Your cart is empty.

Client Quotes

You've done a wonderful job with FileChucker and UserBase, and they have made a big difference to how our website runs.
– Nicholas H.
Why didn't I just do this from the get-go?  So much easier.  Thanks for your work.  FileChucker makes my work easier.
– Dominic M.
The work, the thought and the organization you put into this app is incredible.
– Bruce C.
I looked all over trying to find a simple cgi script.  I found that FileChucker was by far the best.  If you have issues with your hosting service's php.ini max upload size then this is the way to go.  Looking forward to future enhancements.
– Bob C.
Nice script, it's saving the day on our project.
– Aaron W.
I just wanted to say that yours is the first product that I've tested so far that hasn't failed on handling uploads.  This is going to work for a print company, so they are handling nothing but large files and all the other solutions I've tried so far have not been reliable.  So far yours has been 100% successful in my tests.
– Kevin H.
I just installed the demo of your product and got it up and running in no time.  I searched high and low for a decent login script and thank God I found yours.
– Adrian F.
FileChucker is working great...  Clients love it.  Vendors love it.  We love it.
– Gerry W.
The amount of customization in the program is incredible.  I was able to integrate it into my existing page layout relatively simply.  I was also able to easily customize the look/feel to match the current site.
– Jason M.
Do you know how rare it is to have a "canned" shopping cart with the ability to fairly easily do complex pricing options on a single item?  Maybe you do, but if you don't... basically, they don't exist!  I have looked.  Everywhere!  And the few that might even come close to the functionality that you have in CornerStore cost a fortune!
– Tashina P.
Just one word: Fantastic.  10-minute job to plug FileChucker into my app, and it now works a treat.  It's through the hard work by people like yourselves that make my job so much easier.  Congratulations on an outstanding product... Many many thanks.
– Sean F.
Our members think your software is fantastic...  I would recommend your software and your company to anyone.  Thanks for all your help.  It has been a pleasure dealing with you.
– Tommy A.
FileChucker is helping drive the backend of several high profile entertainment sites for people like Shania Twain and Dolly Parton.  We're also using it to drive backend file uploads for a multi-billion dollar banking institution.  It's a great product.  We've tried other "chucking" upload solutions with progress bars using flash and php, but nothing works as reliably as FileChucker.
– Michael W.
Thanks again for a great product and great support - beyond expectations.
– Greg S.
FileChucker is a great drop-in solution for file uploads, and worth every penny of its very reasonable cost.  Encodable's support is excellent to boot.
– Loren A.
I just want to say you guys really stand alone in that you have a quality product and you provide genuine customer service.  It's sad but those qualities are seldom found separately, much less together.  Thanks again for your time and help.
– Alex S.
Thank you VERY much for all of your help.  You've really impressed me.  We have support agreements for other software that costs thousands of dollars / year (just for the support), and most of them aren't as helpful as you have been.
– Keith Y.