Hi!

I'm using DocMan 1.4 in my sites. But I wanted to use a different folder to store the files for each user in my multisite. Is there a way to install the extension separatedly? Or any ideas how to separate eveyone's files?

Thanks in advance.

Here it is two different methods:
1) In DocMan -> configuration menu, you can change the path for storinig files.
So you just have to go in its configuratoin.

2) If you deploy a slave site into a specific directory, you can also decide to create a physical "dmdocument " directory rather than to use the symbolic link (so use MKDIR).
You have to define that in a JMS template to create the slave site.

Thanks for the reply, Edwin.

It did work, to create physical "dmdocuments" using the MKDIR in the template. But... I still don't know how to configure each slave to use it's own folder.
The problem is that I have only one "docman.config.php", and that file is being used by all my sites. Is there a way to copy that file too so that I can configure each site individually, or a way to edit the file using php to generate the path "on the run"?

I really apreciate your help.

Ok... forget it... I just found out how it works.

Multisites creates other config files (docman.config.<site_id>.php) for each slave site.

Thanks for the help

Hi Edwin

To follow this up I have set the template to create the dmdocuments in the slave site and copy over the .htaccess.

The problem I am having is the configuration is still set for /var/www/html/dmdocuments instead of /var/www/html/<multisites>/<slave_site_dir>dmdocuments

Would it be possible to have this configuration automated?

Thanks
Dave

The path of the configuration is defined into the DocMan configuration menu.
So go in the slave site and modify it.

If you want to automate this path computation during a website creation, the only solution is to do add a specific script to modify the DocMan parameter present in its configuration that is stored on the disk. Such kind of script could be called during a website creation from the front-end but this require to enable the billable website functionality and to have quota available