-
Notifications
You must be signed in to change notification settings - Fork 159
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
Broken on Nextcloud 27 (Hub 5) #830
Comments
I ran into same issue, unfortunately I don't have anything to contribute in a way of fixing it. Besides of course disabling the app. |
same issue here |
I confirm the problem when updating |
one line log from nextcloud.log
|
I've got this problem too after upgrading from Nextcloud 26.0.2 to 27.0.0. |
I have the same problem after moving to v. 27. Fatal | onlyoffice | OCP\AutoloadNotAllowedException: Autoload path not allowed: /var/www/html/apps/onlyoffice/appinfo/application.php
Fatal | no app in context | OCP\AutoloadNotAllowedException: Autoload path not allowed: /var/www/html/apps/onlyoffice/lib/appconfig.php
|
Hope this will be fixed and a NC27 version will be released soon 😄 |
Same issue - please fix it |
For qownnotesapi I just had to remove the |
For me, the fix mentioned in the @hackerspace-team comment doesn't work. It throws an error:
Could you (@hackerspace-team ) explain the steps that you took installing the plugin? Maybe I'm missing something? Note: the error only appears when opening the onlyoffice section in the settings. |
delete /apps/onlyoffice |
Sorry for bothering, restarting apache and php-fpm fixed this for me, but because the changes are not yet upstreamed to the Nextcloud Appstore, I'll leave this issue for the developers to close. |
Yes, clearing the opcache seems very important in this case after classes got moved around. |
Works for me too without restarting/clearing anything. |
I confirm that the issue persists. Nextcloud asks me to do this:
When I do this, I get the error message:
|
After updating to the OnlyOffice App 8.0.0 I got the error message After removing the Nextcloud Docker container and starting it up again, the message was gone and OnlyOffice worked fine! |
The autoloader must be cached and doesn't adapt to the new class paths. Therefore restarting helps. |
fix ok 4 me 8.0 but need to restart PHP 8.2 fpm service and nginx then activate the apps and it's ok |
This is not a fix for me as I am not using docker and Nextcloud is running on apache2. |
fixed for me, nextcloud-fpm docker, thanks ! |
@piiskop restart apache2 then |
Fixed for me. A restart of apache2 was indeed necessary. |
Of course, I restarted apache2. Many times. No help. The issue remains. |
Please reopen the issue as it is not fixed. A while ago, I stopped creating new files with ONLYOFFICE after a data loss. Since then, I use LibreOffice and do things offline. I still have some files online that I used to use ONLYOFFICE for editing but now I see that it is not worth using ONLYOFFICE anymore at all. It is not acceptable that an upgrade in Nextcloud to a major version breaks down an app. |
This is a php autoloader "issue", not an app issue. Every app that had to move files around, because Nextcloud moved on had the same issue. But I'm not sure how much you are paying for onlyoffice, to even have some "right" to complain. 😅 |
This should go without saying, but as an admin it's not advised to blindly upgrade to a new major version without testing, at least without anticipating that there may be kinks that still need to be ironed out. If that's too much to ask, I recommend following standard, admin 101 best practices and waiting to upgrade. |
I am not paying anything to ONLYOFFICE but attention. I use the community version and I always get a reaction from the Siberian developers. One of them usually gets angry if the complaint is not directly ONLYOFFICE-regarded but about Nextcloud or the connector as some other people are responsible for the connector and that connector is very poor. @linucksrox, are you suggesting that rather should the admin be responsible for bugs in a major version than the developer? As I see it, Nextcloud developers have lots of development issues. I am wondering whether they test something at all not mentioning performing throughout integration testing as there are so many primitive issues like transparent icons on a white background and then there is a new major version and the issue still persists or there are new issues. Tons of unnecessary things are made for new releases and these important primitive things are still left unresolved. This is a very weird versioning policy. |
|
After an update to Nextcloud (version 26 => 27) the app broke. When testing in a clean installation the same issue also happens.
The text was updated successfully, but these errors were encountered: