OpenDocMan v1.2.9 Released

v1.2.9 includes bug fixes as well as new features. The release includes database updates.

#182 Details page is showing reviewer comments instead of the file comment
#181 Site settings page doesn’t show error messages
#180 Add a max_query limit to the site settings to improve performance. This should help users who have a large amount of files and noticed slow page loads on the main page, especially admin users. We will no “limit” the number of files that show up in the normal file list page, but have no limit for search results. This limit will be set in the Admin->Site Settings->max_query setting with a default to 500.
#179 Clean up the db install/upgrade to make it more clear
#177 Login page – text has no left margin
#176 Missing columns int the database.sql file
#87 Missing slash on the end of the dataDir (Site Settings Page) causes problems


OpenDocMan v1.2.8.1 Released

This release includes bug fixes and enhancements. No database changes.

#175 – Admin setting doesn’t stick
#174 – Permissions Links inconsistent between themes
#173 – add image/svg as standard document type

#171 – Feature – Add Bengali Language
#157 – Add DWG to mimetypes.php


OpenDocMan v1.2.8 Released

Version 1.2.8 of OpenDocMan has been release. This release includes a new limited-user feature as well as a fix for some Windows file path issues. This release contains database changes.

The limited-user feature allows the administrator to enable/disable access to the “Add” and “Check-In” areas for specific users. This also removes the menu items.





OpenDocMan v1.2.7.3 – Release Notes

OpenDocMan v1.2.7.3 has been released which includes a security fix, a bug fix for sub-select UDF fields, and the arabic language.

You can download the latest release from Here


OpenDocMan v1.2.7.2 Released

OpenDocMan v1.2.7.2 has been released which includes security fixes. This release does not include any database changes. All users are strongly urged to update to the latest version.

Changes included in this release:

SQL injection issue

You can download the latest version here.


OpenDocMan v1.2.7.1 Release

OpenDocMan v1.2.7.1 has been released which includes security and bug fixes. This release does not include any database changes. All users are strongly urged to update to the latest version.

Changes included in this release:

  • SQL injection issue
  • Security updates
  • #148 – Permission settings disappear when more than 10 users/departments
  • #139 – Assign to department is showing for non-admin users
  •  #138 – Added Romanian translation
  • #137 – Missing language translations

The latest version can be downloaded here.

1 Comment

OpenDocMan DMS Release 1.2.7

OpenDocMan 1.2.7 as been released. This release does not include any database changes but it does include a change to the Department/User permissions section on the Add and Edit File pages as well as other bug fixes.

Changes included in this release:

  • #136 – File details not showing last reviewer comment
  • #132 – Use full PHP opening tags rather than short ones which may be unsupported
  • #131 – Remove all short tags
  • #125 – EDIT option issue
  • #83 – User Defined Fields – Filter isn’t working also in version
  • #79 – Re-factor the add/edit pages to use a more straightforward UI enhancement
  • #67 – User Defined Fields – Filter-by not working bug
Download the latest release


1 Comment

OpenDocMan Release – Change Log

This release is a minor update with security fixes, bug fixes, and language file changes. No database changes.

Changelog (10/16/2013)

* 112: Add Czech Translation
* 122: Mime-Type Check Fails if function_exists(‘mime_content_type’) but returns null
* 126: Update spanish translation from
* 129: URL redirection security
* 130: Update Italian Translation from


Where Have All The Open Source Document Management Systems Gone?

In the process of checking on our competition I noticed a few interesting things about the open source document management market:

  1. Some of our competitors are completely gone from the market
  2. Some are no longer offering a “free” version
  3. Some require you to “contact sales” in order to find out anything about the system, even to watch an introduction video!

Document management system development is difficult, and open source software development only adds to the difficulty level. In open-source development there are limited resources, limited time, and an unlimited number of feature requests pouring in. While open source development has its challenges, it can also be easier in some aspects. Open source development has a lower overhead (hopefully) as there are many helpful tools and services that are provided to the open-source community at no charge (GitHub, etc). Frequently there are contributions from the community to the project, thus allowing the project to grow and improve without having a salary expense. However, just because your open-source project software is available for free should not mean you cannot make any money from it. 

It looks to me like some of our open-source document management system competitors have decided to move away from open source in order to make money, and I get that. But I find it slightly disingenuous to have a free product and convert it into a paid product without allowing the free product to continue to exist on its own. The Magento project has a business model where the community edition exists next to the commercial edition. They have shown how you can have an open source project and a commercial project running in parallel. Contrast that with other projects that either “hide” their community version, or removed it from their offerings completely. I think what a lot of these other open-source DMS systems have failed to apply are monetization methods. Monetizing your open source project is something that I think all project owners should be looking into, and I would argue it is critical for self-preservation. Lets take a couple of examples that help argue my point:

Joe’s DMS:

Let’s say Joe has an open-source document management project that has been around for a few years. The project is fairly popular and there are a lot of people coming to the site and downloading the software for free but there is no financial gain for Joe, he does this out of the kindness of his heart. He begins to get burnt out, tired, distracted and just moves on to something else. This leaves the community with no support, and no innovation which in the end is a bad thing for all open source projects and their users.

Bills DMS:

Contrast that story with Bill’s project. His project has also been around for a few years and has a lot of users. This project has monetized the project in various ways and has found out ways of generating some revenue while still providing their open source software to the community. Is Bill’s project more likely to continue to exist when there are paying customers helping to keep the lights on? I say yes!!

Now, there are some hardcore open-source folks who will say that open-source software should be free of all cost and that charging money for it is sacrilegious  Most of them have probably never run an open source software project, or been responsible for answering the hundreds of emails each year from users, maintaining all of the servers and sites required for the project, paying the hosting, domain, and software expenses. Trust me on this, open source projects are not free of expenses. 

 I believe that in order to have a healthy open-source software project you need to have some sort of monetization plan. If your open source software project has no revenue generation plans, feel free to contact me and we can discuss.

Stephen Lawrence Jr.