-
-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while loading large library via OPDS #3500
Comments
The error is saying you have a library name that doesn't serialize correctly into XML. Can you share with me the library names you do have that might have a symbol like this? |
The Library is just named "Comics", the error occured when I selected "Want To Read" or "All Series". |
Can you please open the url in your browser and paste the xml here for me for the place the navigation fails (aka produces this error)? |
The url is https://servername/api/opds/XXXXXX/want-to-read?pageNumber=6
From the docker's log:
If I go to https://servername/api/opds/1acaf62e-5e80-4569-bb13-c662be74fe06/want-to-read?pageNumber=5:
|
Thanks. Okay, I think Kavita just needs to take invalid characters and replace them with a placeholder to ensure the feed still loads fine. |
What happened?
When loading larger libraries via OPDS I get an error to load on Panels connected via OPDS. It seems to load the library until that point correctly.
The point/page signaled in the logs seems to be the same every time.
What did you expect?
Load properly.
Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.
0.8.4.2 - Stable
What operating system is Kavita being hosted from?
Docker (Dockerhub Container)
If the issue is being seen on Desktop, what OS are you running where you see the issue?
None
If the issue is being seen in the UI, what browsers are you seeing the problem on?
No response
If the issue is being seen on Mobile, what OS are you running where you see the issue?
iOS
If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?
No response
Relevant log output
Additional Notes
Server is running on unraid.
The text was updated successfully, but these errors were encountered: