Kimbaras

Cool! Unfortunately can't really help with the code part as it's not my field of work, but I offer myself as a beta tester if needed :)

Hi all, Got the same issue and similar setup. Also in my case the Librum Server is deployed on an Ubuntu (22.04) machine. The client is on a Windows 10...

And here the log from Windows 10 [librum_log.txt](https://github.com/Librum-Reader/Librum/files/14764373/librum_log.txt) Let me know if you need also the logs from the Linux one. Thanks

Here are the last 10k lines of server logs (i've renamed it to avoid confusion). I don't think it goes much back as I've deployed it couple of days ago...

> Ok, so the issue seems to be caused by to the Products logic we have added some weeks ago. I'll look into solving this for self-hosted instances of Librum...

> Hm, are you using the same server for both clients? This should not be a client issue, but a server issue. Yep, same server for both. Basically my path...

Hey there, Any update on this one? I've seen that there was both a Docker update as well as Windows (0.12.2, when I replied to the issue I had 0.12.1...

> so the problem is that kavita doesnt group things based on folder structure. the folder requirements is there to help the scan loop. PDFs rely rather heavy on filename...

> That is correct. I am investigating and working on improving the PDF parser in this v0.8.x series of releases. Thanks for the feedback. At this point, if you could...

> These are reserved keywords that if found in the filename will cause Kavita to treat it like a special, much like the SP01 marker does. For manga/comics there is...