-
Notifications
You must be signed in to change notification settings - Fork 17
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
Display problems in "Apps" view in Nextcloud 10 #30
Comments
Thanks. I will try to reproduce and fix it. I assume a incompatibility with the info.xml. |
Please see #31. I will close this, because the problem description seems to be the same. And the answer should fit for this issue too. If you have questions regarding this, please use the other issue. Thx! |
Since the other issue was closed as well, I edited the info.xml myself. Removing the English name, summary and description elements as well as lang="de" from the respective tags for the German description fixed the problems I described. |
I don't think, that this is still a bug in the newest nextcloud version: this should have been fixed already. I suggest you to update the nextcloud server to the latest version. Because in my test runs everything is working! |
Yep, this describes the problem perfectly. Thanks for investigating! |
Bug report
Current Behavior
After extracting the current master version of OCR to nextcloud/apps/ocr/ on my Nextcloud 10.0.1 installation, it appears in the Apps section under "Not activated" like this:
[object Object],[object Object] 1.0.0
von Janis Koehr (agpl-lizensiert)
I can enable and use OCR just fine, but as soon as it is enabled, the "Activated" page of the Apps view does not load anymore (endless loading animation).
After disabling the OCR app on the command line (with occ disable:app ocr), the "Activated" page works again.
I took a quick look at the OCR app code, but couldn't find the reason for this behaviour myself.
Your Environment
Log File Content (nextcloud/owncloud.log of the "data"-directory)
Nothing that looks like it has to do with this issue.
The text was updated successfully, but these errors were encountered: