Your comments

I tried reproducing the issue by recreating the structure you described, but I don't have the probblem.

Same offer as for Pseudocomicnerd in the messages above: would you be able to send me the database file of a Ubooquity instance that have this issue ?

I don't know what might be causing this behaviour, but if you send me your Ubooquity database I'll take a look.

This is the ubooquity-6.mv.db file. Just be sure to stop Ubooquity before copying it.
You can upload it to any file sharing service (e.g. Wormhole) and send me the link at: tom 'at' vaemendis.net

Note that I will be able to see the names of all your files (but not access the files themselves).

I'm glad it worked out in the end, although I would have prefered to understand why. :D

The interface is now a web interface not the previous folder navigation
style, but that maybe because the url is simply
host:port/collection/opds

You mean in Moon Reader ? You don't have something like that ?

Image 805

Image 806

I get the same error

I'm missing something there.

Do you think you could send me your database file ? 
This is the ubooquity-6.mv.db file. Just be sure to stop Ubooquity before copying it.

Note that I will be able to see the names of all your files (but not access the files themselves).
If you prefer and are willing to work a bit more, you can create another database (just launch Ubooquity in another folder) and recreate the issue with just a few files/folder before sending me the database.

However that has opened a new problem authentication fails everytime. I
have a special character in my password, so removed that and tried just
alphanumeric numeric and no password and they all fail with the 2
android apps I use moonreader & fbreader for OPDS feeds. If i try a
browser though the opds url works everytime.

I have had the exact same issue in the past with Moon Reader and FBReader. I don't know where it comes from, although I suspect some credential caching issue on client side (since, as you noticed, the browser never has the issue).

UnfortunateIy I don't remember how the problem went away. Since it was in the middle of big changes, I wiped and reconfigured both my Ubooquity instance and the readers a lot of times. 

the “reader application” has to design the opds to work with ubooquity

No, OPDS is a standard, so (in theory) all clients should be able to work with all servers as long as the specifications of the format are correctly implemented.


It is however rarely that easy with software, as you can see. :)


As far as I can tell, Ubooquity serves valid OPDS (I checked again with this validator today). But from what you tell me, there must be a difference between the feed provided by Ubooquity and the feeds provided by other servers.


The following could help me invetigate further:

  • The version of KOReader you use, as well as the platform (Kindle, Kobo, Android...).
  • Some examples of OPDS pages (XML files) that work correctly for you. You can get them by navigating the feed directly in your browser (to get clickable links, display the page source once the feed is displayed, using the CTRL+U shortcut in your browser)

I did not manage to reproduce the issue on my side.

Is the error log exactly the same as before ?

This line in the logged XML should not be possible after 3.0.1:

 <title>Fantasy & SciFi</title>

Ampersands (and othe special characters) are now escaped in titles.

Would you mind posting the new log ? Perhaps I missed a second issue.

Yes it's supposed to be fixed.

I'll run some additional tests by putting "&" in as many places as possible and see if something breaks.

Did you make any changes to the duplicate detection that you would like

me to try out and see if there are any improvements apart from the new

flag?

Thanks, for now I just made the feature optional.

I'll look into optimizations after the release of 3.1.0 (which will be the official Ubooquity 3, not in beta anymore).