Hi Dan,

I just wanted to let you know that we have now released LogViewPlus v3.1.19 as a BETA release.

This release addresses the directory url issue discussed above.

Hope that helps.  Thanks again for bringing this issue to our attention.

Toby

Glad to hear you are finding LogViewPlus helpful Dan!   

Thanks again for spotting this issue.  I will post back here when the next BETA release is available.

Hi Toby. 

This is brilliant news! Thank you for finding a solution to this problem and for explaining why the issue is occurring. I'll be looking out for the next release.

This software is an absolute lifesaver for me. As someone with dyslexia, it really helps me navigate log files effectively. I struggled quite a bit with Notepad++ as my company's choice of log file viewer, so this program has been incredibly supportive.

Thanks for all your hard work on this software and for your amazing support. It is truly appreciated. 😊

Kind regards

Dan

Hi Dan,

Thanks for bringing this issue to our attention. 

I have had a look and it appears to be a different problem than originally raised by Gabe.  In this case, the problem is the '%20' modifiers in your path.  LogViewPlus treats file paths as URLs internally and it automatically converts %20 into a space.  This is the correct behaviour in most cases, but in your case the directory name is literally "Program%20Files%20(x86)" and not "Program Files (x86)".  This results in the file not being found.

I have implemented a fix for the issue which will be available in the next release.  In the meantime, I would recommend renaming the directory or moving the target file to a different directory.

Thanks again,

Toby

Hi Toby. 

I seem to have the same issue as Gabe.  I have been using Logview Plus Version 2.5.37 for years, but the time has finally come to upgrade to the latest version.  I have tried the latest official Logview Plus, v3.1.15, and the latest beta version, v3.1.18, and both will not load log files if there is an unusual character in the folder path.
Example: C:\C_\Program%20Files%20(x86)\LogFiles
It is the same as Gabe drag and drop; files will not load and also with the File Open feature within log view plus.  The files will not be found as the folders will appear empty even though the file is in there.
Renaming the folders is not really an option to get around this issue, as multiple users of the program will not appreciate this extra step.
For now, I can keep using the old version. 

Dan

Hi Gabe,

Thanks for bringing this issue to our attention.  I was able to recreate the issue locally and can confirm the bug.

As it happens, we had a v3.1.12 BETA release planned for today and I was able to implement a fix.  We can't normally turn issues around this fast, but we got lucky today. 

Hope that helps.  Please let me know if you have any further issues.

Toby

Hi! Love the software, as always. I found a small bug. When I try to open a file in the file path C:\Users\MYUSERNAME\Desktop\141308\logs
LogView Plus will silently fail to load the file. I figured out that renaming the folder called "141308" to "14-13-08" fixes the issue and I can open the files normally.

To be clear, I was dragging the the files from windows explorer into LogView Plus in both instances. And I was able to replicate this even when moving the folder with the unusual characters into other directories, so I'm fairly sure it is the culprit. Also worth noting that I tried multiple files in the offending folder, and no matter which parser I was using I would have the same issue, so I don't think my parsers were part of the problem.

I'm fine, I can simply rename the folder for now. But thought I'd point it out.
Best,
Gabe.