- #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 126.96.36.199 version
- #79 – Re-factor the add/edit pages to use a more straightforward UI enhancement
- #67 – User Defined Fields – Filter-by not working bug
In the process of checking on our competition I noticed a few interesting things about the open source document management market:
- Some of our competitors are completely gone from the market
- Some are no longer offering a “free” version
- 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:
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.
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.
OpenDocMan 188.8.131.52 as been released. This release does not include any database changes but it does include a few substantial changes to the email notifications system as well as other bug fixes.
Changes included in this release:
#109 – Group specific email notifications for approved/rejected do not appear to work
#108 – Only the first file in a multi-upload are being logged into the access log
#107 – Add an onAfterDetails and onAfterHistory plug-in methods
#106 – Reviewers comments not showing up right on details page
#105 – Move the details page into a smarty templatized page
#104 – Add a new report for current files
#103 – Bootstrap.min.js not found in login page
#102 – Show the full 255 char description in the file list
#100 – Update Italian Translation from Forum
#99 – Some page text is untranslated
#98 – Error when searching a text UDF field
#95 – Some DB queries still have odm_ hardcoded for db_prefix
#93 – Email notifications to reviewers when a file is awaiting review enhancement
#92 – Some admin sections not translated
#90 – Undefined index: secondary1 in udf_functions.php on line 274
#89 – Send an email to reviewers any time a new file is added
#53 – Type in the file auth comment screen
In our latest 184.108.40.206 beta commit we added a new feature and fixed a bug:
- When a new file is added, or checked-in department reviewers will receive email notifications of the file waiting for review
- Previously when you authorized or rejected a file the email notifications settings were badly broken. We have tried to fix all of these but this particular area in the code will need some further attention.
You can test-drive the latest beta here:
OpenDocMan DMS version 220.127.116.11 has been released and includes the following changes. Not database updates are required:
- XSS security improvements
- Issue #94 -Warning: Invalid argument supplied for foreach() in FileTypes_class.php on line 59
- Issue #82 – No menu items in small browser window
- Issue #54 – Rejected File – View reviewers comment – link broken
- Issue #51 – Tweeter theme menu button not working for mobile devices
All users are encouraged to update to the latest version
If you are searching for an Installtron OpenDocMan installer, it looks like the folks at Installatron script installer have added OpenDocMan document management system to their list of supported scripts. For more details check out their announcement.
OpenDocMan v18.104.22.168, an open source document management system, has been released which contains various bug fixes. All users are encouraged to upgrade. No database changes.
- Fixed Issue #57 – Added Dutch translation (finally!)
- Fixed Issue #78 – Access log not working
- Fixed Issue #80 – Bug: Warning: finfo::finfo() [finfo.finfo]: Failed to load magic
- Fixed Issue #81 – Trying to delete a file after adding it gives error
We have had a rough time lately trying to get mime-type detection working for all users. Hopefully this release will come closer
to that goal. Please contact us on our web site if you experience mime-type issues still.
- Fixed Issue #77 – some issue various users were having with mime type detection
- Fixed a strange control character in functions.php
- Fixed issue #72 – Data Tables Apear In settings under the languge tab
OpenDocMan 22.214.171.124a hotfix, has been released which includes the following changes:
- Issue #74 – Undefined variable: modified_date in /var/www/doc/functions.php on line 383
- Issue #75 – Notice: Undefined variable: id in check-in.php Issue
- #76 – Some filetypes are coming through as unknown