FAQ
From DocMGR
I can't connect to my postgresql database
First, make sure postgresql is running!!! Follow the steps below to make sure your database is setup correctly.
* Compile and install postgresql * mkdir /usr/local/pgsql * Create the postgres user if it does not exist * chown -R postgres /usr/local/pgsql/data * su postgres * /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data * Modify /usr/local/pgsql/data/postgresql.conf and set "port = 5432" and "tcpip_socket=true" * Start postgresql with "/usr/local/pgsql/bin/postmaster -S -D /usr/local/pgsql/data -i" * Create the DocMGR database with "/usr/local/pgsql/bin/createdb docmgr" * Run "/usr/local/pgsql/bin/psql -d docmgr -f /path/to/docmgr/scripts/docmgr.pgsql * Add this to rc.local: su postgres -c "/usr/local/pgsql/bin/postmaster -S -D /usr/local/pgsql/data -i".
I have php's imap support compiled in (or sendmail is installed on my system) and I still cannot send email
If you are using sendmail, make sure the sendmail service is running on your system. If you are not using sendmail, but are using php's imap support, you need to make sure the mail service that came with your system is running.
Why is there no mysql support?
I'm finding all databases seem to have their place. I can appreciate everyone's position that they want their favorite database supported. I'm the same way with other applications and Postgresql. But, as I develop more and more, I'm finding I can provide better support by putting my focus into one database, instead of spreading it thin by trying to support multiple databases. Because Postgresql by default already supports all the features I require, and implements them well, I have selected to use it.
Why is the tsearch2 backup and restore procedure so complicated?
Well, it's not anymore! If you're running 8.0 or later, tsearch2 backup/restore should be straight forward. For 7.4.x versions of postgresql, there is a file called reprocedure_update.sql in the DocMGR scripts/ directory which I obtained directly from the tsearch2 website. Running it on the docmgr database with a "./psql -d docmgr -f ./regprocedure_update.sql" will update docmgr's database to allow regular database dumps and restoration. Note, when restoring a tsearch2 database dump (after the above patch is applied), perform the following steps:
* Create the database with "./createdb docmgr" * Run the tsearch2.sql file on the database. This file can be found in the contrib/tsearch2 directory in your postgresql sources. Run this with "./psql -d docmgr -f tsearch2.sql". * Restore your database dump with a "./psql -d docmgr -f dbdump.sql". Ignore any errors you get about existing tsearch2 functions.
Why should I use tsearch2?
Tsearch2 allows for a much more accurate search and retrieval capability within DocMGR. It allows for search ranking, faster searches on larger databases, and extended boolean search capabilities (nested boolean searches, for one). It's just plain better than the PHP based indexing system that is stock with DocMGR.
Why aren't my pdfs being indexed?
If pdf support is enabled and you can't get search results for text in your pdf, chances are you're dealing with an encapsulated pdf. These are the pdfs that usually come from scan to pdf (copiers and such), and are basically images encapsulated with a pdf wrapper. DocMGR attempts to index these using gocr. But, since we have to rely on an ocr engine, results will not be 100%.
If you want to see what kind of output you are getting, try converting the pdf to a pnm file "convert file.pdf file.pnm" will do it. You'll probably end up with multiple files. Then, run "gocr file.pnm" to see what it's returning.
Does DocMGR work with Windows?
Unfortunately, no. Many of the utilities DocMGR uses are unix only. You might be able to get them to work by compiling them in cygwin and adding them to your path, but it's going to be painful. IIS also isn't very reliable in calling external programs from php, in my experience.
I want DocMGR in XXXXXX language
Grab the English.php file from the lang/ directory and translate it. You will also need to add the new language file in the config.inc.php file. Please don't forget to email me the file so I may include the translation in the next release. Please view the Language page for more information.
I'm having indexing problems with a particular object type
First, make sure indexing support is enabled for whatever object type you are trying to index. You can check this in Admin -> External Applications. If indexing support is enabled, perform the following steps:
1. In the config/config.php file, uncomment "define("DEV_MODE","1");" and set DEBUG to 5. These are both located towards the bottom of the file.
2. Browse to the object you are having problem with, and put your cursor over the name. In the status bar of your browser, you'll see a link ending with "objectId=1234" where 1234 is the id of the object you are trying to index.
3. From the root docmgr/ directory, run "php bin/di/docmgr-indexer.php --index-object 1234". You should see detailed status messages as the file is indexed. If any error messages are being displayed, you should see them here.
If you are running 0.55 or later, disable background indexing in the config.php file and try again. If any errors occur, you should see them at this point.
My collection tree in the left column does not display any collections
If you are using a non-English language, or your database is not in ISO-8859-1 format, then you need to change the DBENCODING value in the config.php file to the same encoding as your database. Note: PHP uses the iconv function to make the character conversion if available. So, you need to put a value in this setting that iconv() recognizes for your encoding. This may be different than the nomenclature used by postgresql.
When I try to login I see "Error!
The application <appname> could not be found in /sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin
This basically means a required application by DocMGR is not in the path where apache can find it. The "/sbin:/usr/sbin..." is where apache looks for external applications. If you know your app is installed and DocMGR still doesn't find it, try running "which <appname>" from a terminal. It will return the path to your app. From there, just symlink the app to a directory apache uses, using "ln -s /path/to/appname /usr/bin/". You may need to make it executable to your apache user as well. "chmod 755 /path/to/appname" will usually do the trick.
I cannot connect to my Webdav folder in my Windows Explorer (Windows XP)
When you have difficulty connecting from the already present webdav link (see Network Locations in Windows XP) to your DocMGR site then try connecting to the webdav path first in Internet Explorer by entering the http://your-docmgr-site/webdav/client.php URL in IE. This should bring up the authentication window after which the direct webdav connection in Windows Explorer will also work again.
