DocFetcher Pro 1.8 Release

DocFetcher Pro 1.8 has just been released.

The one big news item for this release is that the program finally runs on macOS, specifically on macOS 10.10 (Yosemite) and later. For those who have used the free DocFetcher on macOS before, a notable improvement of DocFetcher Pro on macOS is that the latter comes with the DocFetcher Pro daemon, the small companion of DocFetcher Pro that provides automatic index updating while the main program isn’t running. Please note that on macOS, the daemon needs to be manually added to the startup apps (also known as Login Items). How this is done is explained on the page “Daemon Setup” in the user manual.

For Windows and Linux users, this 1.8 release brings a critical Outlook-related bugfix (email bodies were no longer indexed) and two minor improvements, as explained on the changelog.

The next items on the development agenda are:

  • a long-overdue bugfix release for the free DocFetcher (v1.1.23)
  • support for the v0.4 format of 7z archives
  • DocFetcher Pro Server, a variant of DocFetcher Pro with multi-user support

As stated in the previous post, due to the complexity of the above items it’s hard to give any reliable release date estimates, but hopefully they will all be completed in 2021.

On the planned 7z v0.4 support: DocFetcher Pro inherited its 7z support from DocFetcher, so currently they both support 7z archives up to v0.3 of the 7z format. However, the recent versions of 7-zip create 7z archives in the v0.4 format, so those archives cannot be read by DocFetcher and DocFetcher Pro. That’s kind of a big deal, considering the relative popularity of 7z archives. Adding v0.4 support in DocFetcher Pro requires completely rewriting the 7z handling, so this is going to be a major item on the development agenda.


Subscribe to DocFetcher Pro news

DocFetcher Pro 1.7 Release

DocFetcher Pro 1.7 has just been released. Two indexing-related crashes and one search-related crash were fixed. See the changelog for details.

DocFetcher Pro now comes with a proper user manual, replacing the one copied from the free DocFetcher. With the inclusion of the new user manual, the beta phase has now officially ended. As a consequence, bugfixes and the accompanying announcements will be released at a slower pace, so as to free up developer time for the upcoming items on the agenda:

  • a macOS release of DocFetcher Pro
  • a long-overdue bugfix release for the free DocFetcher (v1.1.23)
  • DocFetcher Pro Server, a variant of DocFetcher Pro with multi-user support

Due to the complexity of the above items, it’s hard to give any reliable release date estimates, but hopefully they will all be completed in 2021.


Subscribe to DocFetcher Pro news

DocFetcher Pro 1.6 Release

DocFetcher Pro 1.6 has just been released. The DocFetcher Pro daemon is now fully functional, and two indexing issues were fixed. One of the two issues concerns the indexing of HTML files, the other was an IOException crash due to files with very long filenames. For details, see the changelog.

As for the DocFetcher Pro daemon: If you didn’t know, the daemon’s purpose is to work together with DocFetcher Pro to ensure that your indexes are always in sync with your indexed files. Specifically, here’s how it works:

  1. DocFetcher Pro is capable of monitoring your indexed folders for any file changes, and will automatically update your indexes when such file changes occur, assuming you haven’t turned off automatic index updates.
  2. Of course, when DocFetcher Pro isn’t running, it can’t monitor your indexed folders, so any file changes occurring during that time will be missed. This gap is filled by the DocFetcher Pro daemon. It becomes active when DocFetcher Pro isn’t running, and by itself it doesn’t do any indexing, it just records detected file changes so that the next time DocFetcher Pro is started, the latter will know which indexes need to be updated.

If you install DocFetcher Pro via the Windows installer, the daemon will be installed automatically. In all other versions of DocFetcher Pro, you will have to manually add the daemon executable to your startup applications.


Subscribe to DocFetcher Pro news