Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: mophilly on January 02, 2006, 12:19:24 AM

Title: PHP, MantisBT and file uploads
Post by: mophilly on January 02, 2006, 12:19:24 AM

I cannot get MantisBT to accept a file to be uploaded. When i attempt it, MantisBT returns an error that the target directory does not exist or permissions are incorrect.

I hope some here can point me in the right direction. I do not know how to interroge PHP settings on SME, and the template fragments for php.ini are still a bit hard for me to understand in some cases.

Here is the error raised by Mantis:

Quote

#503
Invalid upload path. Directory either does not exist or not writable to webserver

Here is my set up:

SME Server
version 6.0 with updates
The ibay "tracker" has been given a PHP base dir for tmp. The tmp directory exists, owner is "www", group is "www" and permission is 777.

Mantis
v1.0.0rc4
config_inc.php contains these settings:
$g_allow_file_upload = ON;
$g_file_upload_method = DISK;
$g_allowed_files = '';
$g_disallowed_files = '';
$g_document_files_prefix = 'doc';
$g_absolute_path_default_upload_folder = '/home/e-smith/files/ibays/tracker/files/uploads/';

The test project has an upload path defined; same as above.

PHP
- I assume PHP is allowing uploads because I have the webshare installed and working. However, I can't say that I am _certain_ all the PHP + virtual directly settings are in order.

Any suggestions, links and WAGs gratefully encouraged.

TIA,

 - M

Title: PHP, MantisBT and file uploads
Post by: Normando on January 02, 2006, 02:07:40 PM

I set file upload method to DATABASE in config.defaults.inc.php and run ok.
If you want you can download as files.

Title: PHP, MantisBT and file uploads
Post by: mophilly on January 02, 2006, 06:29:43 PM

Thank you for the reply.

I had it set to DATABASE in config_inc.php. But I will try it again.

You wrote that you made the change in config.defaults.inc.php. I thought that file was to be left unchanged, and site specific overrides go into config_inc.php. Did you find a better behavior by modifying config.defaults.inc.php, or something else?