Troubleshooting
If this troubleshooter does not help, and you are sure the cause is a bug, then please check the bug tracker to see has your bug been reported before - if not, then please report it.
It is possible that your problem has already been reported and fixed. Please try the nightly version of KFM to see if your problem has been fixed.
1. Problems with Installation
First, please read the Requirements on the front page of the site. If your system does not match the requirements, you may have found your problem already. If this is the case, but you really think your system should be supported, please describe your system and explain why it should be supported.
It is possible that your problem has already been reported and fixed. Please try the nightly version of KFM to see if your problem has been fixed.
error: no writable workpath is specified.
one of the first tests KFM does is to verify you have provided a workpath that it can write to. By default, this is set to .files, within a directory specified by the $kfm_userfiles variable.
$kfm_userfiles must be writable by the web server. This is not always the same user account as your FTP account. If in doubt, use your FTP client to "chmod 777" (read/write/execute permissions for everyone) the directory and its children.
$kfm_userfiles is relative to the document root. For example, if your web root is /home/kae/public_html and your files are located at /home/kae/public_html/files then your $kfm_userfiles should be '/files/' (make sure to include the end slash).
If you want to use a directory that is not accessible normally by a web browser, you should use "get.php" for the $kfm_userfiles_output, and the $kfm_userfiles should be something like "/../../Desktop/userfiles/" (that's what my test server's $kfm_userfiles is set to - my web root is /home/kae/public_html/kfm/ and my files are located at /home/kae/Desktop/userfiles/)
once $kfm_userfiles passes its "is writable" test, the .files folder is created automatically.
database tables not created (MySQL)
KFM supports MySQL 4.1+. It has been noted that earlier MySQL versions have problems with the KFM installation scripts.
If you are using an earlier version, it is strongly urged that you upgrade. In particular, earlier versions have problems with non-English characters, so if you are using KFM in a non-English website or will be using files with non-English characters, you must upgrade before installing KFM.
If you insist on keeping the same version, the way to install is to remove the DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci bits from the file scripts/db.mysql.create.php, and then load the KFM index.php file in your browser.
2. Problems with KFM Usage
fails to upload flv/avi/mpg files
If KFM allows some types of files, but uploading other types fails, then please check the size of the failed files. .avi, .mpg, .flv files tend to be very large.
If it is a file-size problem, then you need to adjust your PHP settings. It is not a problem with KFM. Edit your PHP's php.ini, and change the upload_max_filesize line to something larger, then restart your web server.
If it is not a file-size problem, then check the $kfm_banned_extensions line in your configuration.php