Activity for DocFetcher
-
Edward Lipsett posted a comment on discussion General Discussion
Oof. Thanks for the clarification. So I either have to live with it on my C drive, or switch to the portable version. Hmm. Have to think on that. On Sun, Apr 5, 2026 at 3:53 PM Nam-Quang Tran qforce@users.sourceforge.net wrote: Hi there, DocFetcher and DocFetcher Pro are separate pieces of software with separate FAQ pages. The DocFetcher FAQ is here: https://sourceforge.net/p/docfetcher/wiki/FAQ/ The DocFetcher Pro FAQ is here: https://docfetcherpro.com/faq/ The relevant entry on the DocFetcher Pro...
-
Nam-Quang Tran posted a comment on discussion General Discussion
Hi there, DocFetcher and DocFetcher Pro are separate pieces of software with separate FAQ pages. The DocFetcher FAQ is here: https://sourceforge.net/p/docfetcher/wiki/FAQ/ The DocFetcher Pro FAQ is here: https://docfetcherpro.com/faq/ The relevant entry on the DocFetcher Pro FAQ says: How can I change the location of the indexes? DocFetcher has a misc/paths.txt file that allows customizing the location of the indexes. In DocFetcher Pro, the misc/paths.txt file is gone without replacement for technical...
-
Yes, I know this is covered in the FAQ, which states "For customizing the location of the index files, have a look at the file misc/paths.txt inside the DocFetcher folder." Unfortunately, my installation (Windows 11) does not include a paths.txt file. My index files are located on my (crowded) C drive at the address given in that FAQ. Could someone direct me to information on how to move (or re-create) my index files at a different location, NOT on my C drive? Or just post the paths.txt file, if...
-
Yes, I know this is covered in the FAQ, which states "For customizing the location of the index files, have a look at the file misc/paths.txt inside the DocFetcher folder." Unfortunately, my installation (Windows 11) does not include a paths.txt file. My index files are located on my (crowded) C drive at the address given in that FAQ. Could someone direct me to information on how to move (or re-create) my index files at a different location, NOT on my C drive? Or just post the paths.txt file, it...
-
Yes, I know this is covered in the FAQ, which states "For customizing the location of the index files, have a look at the file misc/paths.txt inside the DocFetcher folder." Unfortunately, my installation (Windows 11) does not include a paths.txt file. My index files are located on my (crowded) C drive at the address given in that FAQ. Could someone direct me to information on how to move (or re-create) my index files at a different location, NOT on my c drive? Or just post the paths.txt file, it...
-
Will be fixed in DocFetcher 1.1.28.
-
Anonymous created ticket #2450
DocFetcher error on installation #1
-
Simon posted a comment on discussion General Discussion
Thanks, that seems to have worked. Thanks too for an excellent piece of software!
-
It looks like a zombie instance of DocFetcher Server is still running and preventing the start of a new instance. Try killing the old instance and removing the lock file before starting a new instance: kill 1483 rm /tmp/docfetcher-server-71098e4244dee072cb3d81bd3b2a27c69fb90fe162f83182d7036e2980db1634.lock
-
Hi Quang, thanks for the reponse. I've attached the output here.
-
Hi Simon, DocFetcher Server brings its own Java runtime, but perhaps it's now damaged or the launch script was changed to a different Java runtime. Can you post the full terminal output from server-start-foreground.sh? If it contains sensitive data that you don't want to share in public, you can instead send an email to the support address: https://docfetcherpro.com/contact-support/ Regards q:-) <= Quang
-
I have had DocFetcher Server successfully running on an openmediavault (Debian) server for quite a while. For some reason the web interface stopped working and after a little poking around it seems I am unable to start the server using server-start-foreground.sh. At the end of the dump it says "Service exit with a return value of 122". Although I upgraded to Debian v8 the other day I didn't use DocFetcher immediately afterwards, so can't be certain that has any bearing. The dump seems to relate to...
-
I have had DocFetcher Server successfully running on an openmediavault (Debian) server for quite a while. For some reason the web interface stopped working and after a little poking around it seems I am unable to start the server using server-start-foreground.sh. At the end of the dump it says "Service exit with a return value of 122". Although I upgraded to Debian v8 the other day I didn't use DocFetcher immediately afterwards, so can't be certain that has any bearing. I don't understand what could...
-
UnsupportedOperationException
-
Please upgrade to the latest DocFetcher version.
-
Anonymous created ticket #2449
UnsupportedOperationException
-
Drafting Dreamer posted a comment on ticket #163
Hi Nam-Quang Tran, Thanks a lot for the patch! I really appreciate you getting this ready for the next release. Thanks again for your hard work on this project! Cheers, Drafting Dreamer
-
I've converted the Markdown files to HTML, see attached file. This will be shipped with the next DocFetcher release, whenever that comes out. The files would appear under "help\Chinese (Taiwan)" in the DocFetcher app folder.
-
Hi there, the app doesn't have this feature. However, you can use wildcards like this: Jos* Jos? Regards Quang
-
unable to index Synology drive fully
-
Hi Drafting Dreamer, thanks a lot for your translation! I will integrate it into the app for the next release. I won't be needing help - I'll let the AI sort things out ^^ Please note that it will take some time (probably months) before the next release is out. Your name ("Drafting Dreamer") will then be added to the credits page: https://sourceforge.net/p/docfetcher/wiki/Credits/ Regards q:-) <= Quang
-
[Localization] Complete Translation of Traditional Chinese (zh_TW) Documentation
-
Hi, DocFetcher Server currently does not support ARM CPUs, but this will be considered for future major release like v2.0. Regards q:-) <= Quang
-
ioncube posted a comment on discussion General Discussion
I would like to run DocFetcher server on SBC like RaspberryPi 4/5 with 4GB RAM. Are authors inclined for such a release?
-
Hi there, the screenshot suggests that the indexing actually finished, it's just that there was an error on the last file, which makes it look like the entire indexing process failed. Try a few searches, they should succeed. Regards q:-) <= Quang
-
Anonymous created ticket #2448
unable to index Synology drive fully
-
sandokan09 posted a comment on discussion General Discussion
Thanks, we have rescanned our .docx files as folder. Everything seems to be working as it should now.
-
This suggests that when you created the index, you added "docx" as a "zip archive extension". While docx is technically zip, telling DocFetcher Server to treat it as zip will override the app's built-in docx support. This leads to worse search results and also the weird filtering behavior you observed.
-
Hello Quang, Please excuse the late reply. We were able to solve the “problem” ourselves. I only checked the “Folder” option for the container types. This worked fine for PDFs. And although the docx files are stored in a separate folder just like the PDFs and are also integrated as a folder, the docx files are only displayed correctly if the “Archive” option is also checked. This seems illogical to me, but at least that's how it works. Thanks and regards
-
Hi Peter, DocFetcher is not designed to be run simultaneously by multiple users, and index corruption caused by concurrent writes is a known issue. There's a section "Setting up DocFetcher in a multi-user environment" on the DocFetcher wiki that explains this in more detail. See here: https://sourceforge.net/p/docfetcher/wiki/Tips%20%26%20tricks/ Regards q:-) <= Quang
-
markd89 posted a comment on discussion General Discussion
Thanks, I don't know what I was doing wrong, but it's happy now. I discovered I can use type:mp4 in the search box which is helpful. I didn't see that in the documentation, but I probably missed that too. Thanks again for the great app and geat support!
-
Peter Barton posted a comment on discussion General Discussion
I have a Server 2025 network shared folder that all users browse to and launch DocFetcher directly from the drive share. I Have successfully run the index process for the shared folder, which is mapped through the drive share path not the local C:\ drive path. Everything works fine and people can access and search documents. However, after a few days or a week of this we will get the message that the 'index is not compatible' and I am forced to re-index the folder again. I was initially running 1.1.25...
-
hotcore posted a comment on discussion General Discussion
Hi Quang, the regexes are matched against files, not folders, and the path separator as seen by the app is "/" rather than "\". Try this: C:/Users/theuser/AppData/Local/.* thx for this! I'll try tomorrow. Best wishes AvW
-
Elmar Grosse Ruse posted a comment on discussion General Discussion
Thank you very much. Either way sounds good.
-
Hi there, the regexes are matched against files, not folders, and the path separator as seen by the app is "/" rather than "\". Try this: C:/Users/theuser/AppData/Local/.* Regards q:-) <= Quang
-
Hi there, that's probably a problem with the snap package. Try the DocFetcher releases from the project website: https://docfetcher.sourceforge.io/download/ Regards q:-) <= Quang
-
Hi there, you can either use the non-portable version of DocFetcher and edit the misc/paths.txt file to move the index into the encrypted folder, or you can use the portable version of DocFetcher to move the entire app and its index into the encrypted folder. Regards q:-) <= Quang
-
Will be fixed in DocFetcher 1.1.28.
-
Hi there, can't reproduce the issue. With DocFetcher 1.1.27, I can index and find jpg, mp4 and webp files by filename just fine. There might be a problem with your indexing settings (on the indexing dialog) and/or your search filter settings (on the left side of the app window). Posting some screenshots here would be helpful. Regards q:-) <= Quang
-
Hi, since I simply want to exclude a specific folder and it's contents, I guessed it wouldn't be a problem, however, after trying a few things myself and later using answers somewhere on the web, as well as AI, I cannot get it right at all. The Windows 11 folder I wish to exclude is: C:\Users\theuser\AppData My latest regex looks like this (tested and working on https://regex101.com/ ) [^C:\\Users\\theuser\\AppData\\.*] But testing it against e.g. this next folder fails C:\\Users\\theuser\\AppData\\Local...
-
KitchM posted a comment on discussion General Discussion
Using Debian 12 with Xfce .18. DocFetcher cannot display existing drives that are mounted in the OS currently. They do not show up on your file manager screen and so cannot be selected to start the index. Snap version 1.1.25-snap1 reversion 4 latest/stable vasilisc
-
Dear community, I indexed a folder on my computer that is normally encrypted. The index of docfetcher however is stored in a not encrypted folder on my computer. I assume, my data now is not that safe anymore. I can move the index to an encryted folder and use docfetcher whenever I have decrypted that folder - correct? Thank you for any advice!
-
Anonymous created ticket #2447
UTF8 encoding is longer than the max length 32766
-
Hi Nam-Quang, I am indexing folders with pictures and videos. I just want the filenames indexed. However we only seem to be indexing the filenames on .WEBP images. Other images and video files are not getting indexed. If I right click on the index and List files, I only see .WEBP. Maybe I am missing a setting somewhere? Thanks! Mark
-
EDIT: I'm going to make a new issue for this. Nam-Quang, I installed 1.127 and this issue is indeed resolved. However.. I am indexing folders with pictures and videos. I just want the filenames indexed. However we only seem to be indexing the filenapes on .WEBP images. Other images and video files are not getting indexed. Maybe I am missing a setting somewhere? Thanks! Mark
-
Name-Quang, I installed 1.127 and this issue is indeed resolved. However.. I am indexing folders with pictures and videos. I just want the filenames indexed. However we only seem to be indexing the filenapes on .WEBP images. Other images and video files are not getting indexed. Maybe I am missing a setting somewhere? Thanks! Mark
-
Hi there, to properly investigate this, I need to take a look at one of those MS Word files, or at least an equivalent test file where the search fails. Can you send me a file via the support email address listed on the following page? https://docfetcherpro.com/contact-support/ Regards q:-) <= Quang
-
Hello, after a successful test run with our PDF archive (10,000 documents, ~5-10 MB per file), I purchased Docfetcher Server. In a second step, I wanted to index an archive with approximately 500 DOCX files (~10 MB per file). The indexing runs smoothly, but only takes a few seconds compared to the PDFs. Afterwards, however, the search finds virtually nothing. For example, each of our 500 documents contains the same terms on the title page. When I search for them, however, a maximum of 2-3 documents...
-
Fixed in DocFetcher 1.1.27.
-
Anonymous created ticket #2446
crash
-
Will be fixed in DocFetcher 1.1.28.
-
Will be fixed in DocFetcher 1.1.28.
-
Please upgrade to DocFetcher 1.1.27 or later.
-
Will be fixed in DocFetcher 1.1.28.
-
Will be fixed in DocFetcher 1.1.28.
-
Fixed in DocFetcher 1.1.27.
-
Will be fixed in DocFetcher 1.1.28.
-
Fixed in DocFetcher 1.1.27.
-
Will be fixed in DocFetcher 1.1.28.
-
Fixed in DocFetcher 1.1.27.
-
Hi there, DocFetcher isn't equipped to handle 50,000-page PDF files. You need to either open the PDF file in an external viewer and use the viewer's search function, or use a PDF tool to split the 50,000-page files into smaller files so the DocFetcher search results show the location more accurately. Regards q:-) <= Quang
-
No Name posted a comment on discussion General Discussion
I have 10 HUGE pdfs - 50000 pages. When I search something it instantly finds which pdf the text is located in. But it doesn't say WHERE IN THE PDF it is. Is it possible to show on which page the text is located instantly?
-
I have 10 HUGE pdfs - 50000 pages. When I search something it instantly finds which pdf the text is located in. But it doesn't say WHERE IN THE PDF it is. Is it possible to show on which page the text is located instantly?
-
Will be fixed in DocFetcher 1.1.28.
-
Fixed in DocFetcher 1.1.27.
-
Fixed in DocFetcher 1.1.27.
-
Fixed in DocFetcher 1.1.27.
-
Fixed in DocFetcher 1.1.27.
-
Fixed in DocFetcher 1.1.27.
-
Fixed in DocFetcher 1.1.27.
-
Fixed in DocFetcher 1.1.27.
-
Please upgrade to DocFetcher 1.1.26 or later.
-
Will be fixed in DocFetcher 1.1.28.
-
Anonymous created ticket #2445
Bug
-
Will be fixed in DocFetcher 1.1.28.
-
Anonymous posted a comment on ticket #2444
Crash during create index
-
Anonymous created ticket #2444
Crash during create index
-
Will be fixed in DocFetcher 1.1.28.
-
Fixed in DocFetcher 1.1.27.
-
Fixed in DocFetcher 1.1.27.
-
Fixed in DocFetcher 1.1.27.
-
ChangeLog
-
DocFetcher released /docfetcher/1.1.27/DocFetcher-1.1.27-Windows-64bit-Setup.exe
-
-
-
-
-
-
Nam-Quang Tran committed [9ea43d] on Git Repo
Version 1.1.27.
-
Nam-Quang Tran committed [f2fa58] on Git Repo
If the user tries to run the portable version from a protected folder like "C:\Program Files", show an error message instead of crashing.
-
Nam-Quang Tran committed [ba9f09] on Git Repo
Increased default preview font sizes.
-
Nam-Quang Tran committed [b4a391] on Git Repo
Fixed setup for IntelliJ IDEA.
-
Nam-Quang Tran committed [690e83] on Git Repo
Changed default fonts used in preview pane for better Unicode coverage:
-
Nam-Quang Tran committed [2dd9ea] on Git Repo
Bugfix: Fixed crash when indexing MS Office documents on Java installations with missing Big5 charset by catching NoClassDefFoundError and ExceptionInInitializerError in Word/PowerPoint/Visio parsers. Bug #2151.
-
Nam-Quang Tran committed [54c4aa] on Git Repo
Bugfix: Fixed crash when indexing encrypted PDFs on systems with corrupted Java installations by catching InternalError thrown when cryptographic provider libraries are missing. Bug #2158.
-
Nam-Quang Tran committed [f49b9d] on Git Repo
Bugfix: Fixed crash when indexing corrupted ZIP-based files (Office 2007+, OpenDocument, EPUB) by catching ZipError in multiple parsers. Bug #2188.
-
Nam-Quang Tran committed [aa10b2] on Git Repo
Bugfix: Fixed query parser crash when searching with Unicode curly quotation marks. These are now auto-converted to straight quotation marks. Bug #2226.
-
Nam-Quang Tran committed [f1d2fd] on Git Repo
Bugfix: Fixed ArrayIndexOutOfBoundsException crash in charset detection library during document preview. Bug #2235.
-
Nam-Quang Tran committed [4c62f8] on Git Repo
Bugfix: Fixed JVM native crashes on Windows after extended runtime by switching from memory-mapped I/O to RAFDirectory for Lucene indexes. Bug #2242.
-
Nam-Quang Tran committed [676cf8] on Git Repo
Bugfix: Fixed IllegalArgumentException crash when adding items to folder tree due to rare SWT bugs or race conditions. Bug #2248.
1 >
