PDF has been a painful topic since the beginning.

There is no "perfect" free library to render PDF in Java yet (although PdfBox is making progress).

So what I'll do in a future version is to allow users to plug external PDF renderers (MuPDF, Poppler...) to Ubooquity.

This should solve all the most of the PDF relarted problems as they are usuallly more efficient than PdfBox.

In the meantime, the only workaround (which might not work in all cases) is to try to allocate more memory to Ubooquity (see the FAQ).

Ubooquity 1.9 and 1.10 do not use the same version of PdfBox (the lib used for PDF rendering), that's probably the cause of your problem.

Unfortunately, your covers are "broken" by the most recent version of PdfBox, which fixes a lot of problems for other PDF files. So I can't go back to the older version.

If you can provide me with a example of "broken" file, I'll take a look at what happens, in case there some fix I can apply (though its quite unlikely).

I'll continue to update PdfBox when I release versions of Ubooquity, so your problem might go away as PdfBox evolves (the project seems quite active).

I also plan to allow plugging external PDF renderers to Ubooquity (e.g. MuPdf, Poppler...) so that people can choose the one that suit their needs.

No, it's not expected (at least if I understood correctly the Logback documentation).

But I retested the whole procedure and got the same behavior that you had.

So I don't know exactly why the file needs to be in the working directory, but I'll update the Ubooquity documentation accordingly.

Thanks for the info.

By the way, the doc has been put on Github, so the new link to the procedure is:

https://vaemendis.github.io/ubooquity-doc/pages/tutorials/log-customization.html

Not possible the moment.

It will be when I implement the new templating mechanism I have in mind to allow full customization of the pages.

But it will be a while before I can do it...

Ubooquity logging can be customized by overriding its Logback configuration file.

An example of such customization is available in the documentation.

In your case, you will probably want to use a SyslogAppender, which is fortunately already included in the logback-classic lib used by Ubooquity.

So you should already have everything you need to plug Ubooquity log to your Synology logging system.

The new web admin (in version 2.0) will have a "remember me" checkbox.

Don't check it and your cookie will expire when you close your browser (that's a very standard behavior).

Otherwise the session will stay alive for 30 days.

(in the meantime, you can log off manually with the "log out" link)

The embedded web server happens to have a pool of 20 threads.

I don't know if this might be related or not.

In any case, all this part has been replaced in version 2.0.

So please try again when the new version is out, I'm pretty sure you won't have the problem anymore.

Good catch, I'll see what I can do (since the database is unfortunately not capable of natural sorting, which is what I would need here).

As for the full rescan, it will be necessary with the next version anyway (even preferences will be lost).