(http://www.mambodocman.com/index.php?option=content&task=category§ionid=2&id=11&Itemid=31)

What is DocMan? DocMan is a document management and download system to Mambo Open Source 4.5. With this component you can manage documents across multiple categories and subcategories and make them available for download on a Mambo powered web site.

Features These are the main features of DocMan: • •

• • • • • •

Infinite categories and subcategories. The documents can be organized across custom categories and subcategories; Custom groups support. Documents can be owned by a specific registered user, a groups os registered users, all registered users or everybody; * Download counter and log. You can display a download counter per document and all the downloads can be logged* (by user, IP, browser, date and hour); Own search system. Documents can be searched by name and/or description; Online editor. Plain text files can be edited online; History and archiving system. All documents can use the history description and be archived to later retrieve; Mass group e-mail function. A user assigned to a group can e-mail other group users to discuss a document; Anti-leech system. The built-in anti-leech system avoids direct linking to documents; Path protection. Real paths to documents are never displayed to users.

* Note: feature only available since DocMan 1.0 stable

How to install DocMan? Fresh install DocMan can be installed just like any other Mambo component. From the administration panel, select from the menu Components->Install/Uninstall. Find Upload New Component and, clicking over the browse button, locate your DocMan's package. Always use the original, uncompressed package. Now, click Upload file. Wait a few seconds. After this step, you should see a message with DocMan's logo indicating a successfuly instalation. You're done. Now, proceed to DocManConfiguration.

1/4

How to optimize your PHP installation to handle large file uploads? Though PHP presents a very versatile and user friendly interface for handling file uploads, the default installation is not geared for working with files in excess of 2 Mega Bytes. This article is an aid to configuring PHP for handling such large file transfers.

php.ini The php.ini file contains all the configuration settings for your installation. Sometimes these setting might be overridden by directives in apache .htaccess files or even with in the scripts themselves but for the moment let's just concentrate on the ini file. This file contains the following settings that we need to modify • • • • • •

file_uploads upload_max_filesize max_input_time memory_limit max_execution_time post_max_size

The first one is fairly obvious if you set this off, uploading is disabled for your installation. We will cover the rest of the configuration settings in detail below. upload_max_filesize and post_max_size Files are usually POSTed to the webserver in a format known as 'multipart/form-data'. The post_max_size sets the upper limit on the amount of data that a script can accept in this manner. Ideally this value should be larger than the value that you set for upload_max_filesize. It's important to realize that upload_max_filesize is the sum of the sizes of all the files that you are uploading. post_max_size is the upload_max_filesize plus the sum of the lengths of all the other fields in the form plus any mime headers that the encoder might include. Since these fields are typically small you can often approximate the upload max size to the post max size. According to the PHP documentation you can set a MAX_UPLOAD_LIMIT in your HTML form to suggest a limit to the browser. Our understanding is that browsers totally ignore this directive. memory_limit When the PHP engine is handling an incoming POST it needs to keep some of the incoming data in memory. This directive has any effect only if you have used the --enable-memory-limit option at configuration time. Setting too high a value can be very dangerous because if several uploads are being handled concurrently all available memory will be used up and other unrelated scripts that consume a lot of memory might effect the whole server as well. max_execution_time and max_input_time These settings define the maximum life time of the script and the time that the script should spend in accepting input. If several mega bytes of data are being transfered max_input_time should be

2/4

reasonably high. You can override the setting in the ini file for max_input_time by calling the set_time_limit() function in your scripts.

Special Notes Apache Settings The apache webserver has a LimitRequestBody configuration directive that restricts the size of all POST data regardless of the web scripting language in use. Some RPM installations sets limit request body to 512Kb. You will need to change this to a larger value or remove the entry altogether.

Configuration 1. Backend Here you will find general options to use with the backend. 1.1 Documents Path Absolute path where the documents will be stored. Make sure it starts from the server's root and ends with no right slash. On unix systems it can be, for example, /var/www/mydocs. On Windows systems, use only double right slashes. An example in such system could be c://inet//docs. The first time you access the configuration, this value will be auto-adjusted to your server*, pointing to the default DocMan directory dmdocuments, present in the Mambo's root. *Note: this feature is only available since DocMan 1.0 stable

2. Frontend 2.1 Section in down? If yes, the section will be displayed as being down for maintenance and regular users will not access it. Administrators can always browse the section. In this case, a message is displayed on top of the page indicating this status. This is used for testing and updating. For example, when an administrator needs to update several documents and don't want regular users to access it until done. 2.2 Documents per page Number of documents to display per page. If more, a navigation bar is displayed. 3/4

2.3 Registered users only? If no, anonymous users can access documents owned by 'Everybody'. If yes, anonymous users (e.g. without registering at the site) will not have access to the section. 2.4 Show category images? If yes, category images will be displayed when browsing categories. 2.5 Use category image instead folder icon? If yes, category images will be used instead regular folder icons when listing categories. If no icons are being used, you can still use this option.

4/4