Has anyone encountered issues connecting to Kavita with Panels? I’ve tried the api in the host section and then a normal setup using my local ip and port number. Neither option is connecting. Any help would be appreciated. Thank you!
Edit: Tagging @majora2007 to help keep updated on a possible resolution.
So far, I’ve managed to get the api url settings working which allowed me to add the server. However, clicking into kavita in the import services box gives me a service error
"The operation couldn’t be completed. (Panels.OPDSParserError error 0.)
This error applies to any folder I click into, ie. All collections; All libraries; etc…
I’m looking at the error logs and I’m seeing some errors trying to parse Kavita’s feed. Looks like the feed is missing the feed.id field.
{
"OPDSParserError.missingField" = {
"message" = "Missing required field";
"missing_field" = "feed.id";
"raw_xml" = "<?xml version=\"1.0\" encoding=\"utf-8\"?> \n<feed xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns=\"http://www.w3.org/2005/Atom\"> \n <updated>2021-11-08T19:06:26</updated> \n <title>All Libraries</title>...[truncated]"}
According to the Atom RFC https://datatracker.ietf.org/doc/html/rfc4287#section-4.1.1 , an Atom feed (an OPDS feed is an Atom feed) the atom:id field is required.
OPDS 1.2 spec OPDS Catalog 1.2 | specs also defines atom:id as MUST.
Maybe this field was removed in one of the latest releases of Kavita? 
I’m happy to make any change on Panels to improve compatibility with other servers. But in this case, I think it should be fixed on the server-side because it breaks the RFC.
This is indeed a problem with Kavita. When I implemented a “No items” for when there were no feed results, I forgot to include the Id.
Thanks Dani for tracking it down.
Amazing. Thank you for confirming.
This has been fixed in Kavita. It will release with next stable (v0.4.9) or is available on latest nightly.
legend