-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
XML parser error #24371
Comments
This really has to be taken care of by the maintainer of the app - sorry there is not much we can do -> close |
Thought so. Thanks for the info anyway :) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there, after the Update to 9.0.1 I get an XML parser error with the OPDS app . I don't know if this is an issue with oc 9 or not. I've contacted the maintainer of OPDS catalog, but I didn't get a response yet. So I thought you guys might be able to give me some hints where I can start looking for the problem.
I updated to 9.0.1 from 8.2.3. OPDS app was already latest 0.6.15. Update with occ command. Went well on the first run.
Expected behaviour
When I browse to https://mydomain.de/index.php/apps/files_opds/ I see the catalog page (looks like an rss feed)
Actual behaviour
Instead I see an xml parser error:
Line 88 changes, sometimes it's 88, or 89 or 90. Don't know why.
Firefox webdeveloper says in addition to the parsererror:
Server configuration
Operating system: Ubuntu 14.04
Web server: apache 2.4
Database: Mysql
PHP version: 7.0.5
ownCloud version (see ownCloud admin page): 9.0.1
Updated from an older ownCloud or fresh install: 8.2.3
ownCloud log (data/owncloud.log): The log doesn't say anything but finished cron jobs, loglevel is debugg.
I use encryption, but this wasn't a problem before. I start to think, the problem is in the database. But even choosing a new folder fpr the library and disabling and enabling the plugin again doesn't do a thing.
Thx 4 f1.
st.
The text was updated successfully, but these errors were encountered: