[AndrewD]

Originally Posted by 7lanet

Possible inconsistencies between LDM and its environment
- Parameter upload_enabled is enabled but parameter upload_dir is not set

You have turned on the LDM admin setting *upload_enabled* but you have not set *upload_dir*, so LDM doesn't know where you want to store uploaded files. You have to tell it.

Originally Posted by 7lanet

- allow_url_fopen is off and cURL is not available in php.ini file - Remote downloads not available

*allow_url_fopen* is a control setting for php on your web server, in the php configuration file *php.ini*. Your site admin has set up your server so that php cannot use one of the standard ways of accessing remote files.

*cURL* is an addon library for your web server. It provides another (better) way to access remote files. Your web admin has not installed it.

Consequently, LDM cannot *manage* remote downloads - it can only manage *local* downloads. A *local* download is physically stored on your server (either an upload or a file with no url in its name). A *remote* download is a file accessed via a full url.

Originally Posted by 7lanet

- upload_max_filesize 2M >= post_max_size 2048k in php.ini file - Large uploads may fail without warning

These are two more settings that control php's handling of uploads, also found in the php configuration file *php.ini*. They specify the maximum amount of data that can be uploaded in one go. It is good practice (but not essential) that *post_max_size* has a bigger value than *upload_max_filesize*. Otherwise, when a user tries to upload file that is bigger than *post_max_size*, some versions of php will fail to generate an error message.