-
Notifications
You must be signed in to change notification settings - Fork 48
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
Autoload path not allowed #219
Comments
Nextcloud 27 removed the PSR-0 class loader. We need to upgrade the structure to PSR-4 or implement a custom class loader. Also see: |
I just want to contribute a full log:
|
The documentation does not really help to fix the problem. If anyone knows how to do this - help is welcome. |
I agree that the documentation alone is not that helpful for fixing this problem but I found https://help.nextcloud.com/t/breaking-removal-of-psr-0-class-loader-in-nextcloud-27/153916 on this topic and gave it a try, please see #222 |
Unfortunately after merging #222 there is no error any longer but the app still does not work. It now looks as it will not even be loaded any longer. |
That's interesting. I'm running the docker image I also just set my |
No, no idea at all. KeeWeb is just not used, eventhough it is active. And about logs: yes, you are right. Indeed the error messag is caused by the |
My last comment was a mistake - since KeeWeb is not even used, it will of course not create any log message. |
It seems, removing |
Oh, that's unfortunate. I still don't understand why it works for me without the autoload file then, but I can take a look at this later and submit a follow-up PR to re-add the file. I just can't test if that will fix the issue for you if I don't know why it doesn't break for me at the moment :D |
I took another look at the documentation and I didn't find any reference to an |
Thanks for your help. Now I get a new error...
I'll check what is going on. |
In addition the MIME type registration also does not work. When I click a kdbx file it will only be offered for download and not opend in Keeweb. Did you test it with NC27? |
Yes, I am running latest |
Well - I don't have a Docker version, just NC 27 installed manually with PHP-FPM 8.1 and Apache 2.4. |
Just to be sure I tested in again on a vanilla new setup of NC27 - fresh install with a new database. Same result: Keeweb will not be loaded. Now I don't get an error message but it still does not work. kdbx files will only be offered for download and clicking the Keeweb icon in the toolbar will only create a blank page. |
Ok, now it gets really interesting. 🤯 edit: I used ubuntu 22.04, with php-fpm, apache, mysql, a freshly built keeweb app from master and nextcloud 27.0.0 for the test |
Update: ok the ssl issue must've been something else, it also works via http, without ssl. I now also tested different browsers (firefox, chromium) and can't get it to break :( |
Good news. I moved to another server which is more or less identical to my production system and there everything works fine. Seems the development box is a bit flaky. Anyway - I'll do some tests and after that I think we are good to go. And #205 is also closed by your changes - thanks! |
Awesome, thank you, too 🥳 |
Hi, I've got this error in servers's logs too.
Debian 12, PHP 8.2.7, Nextcloud 27.0.0.8 |
Sorry, I can not reproduce this error any longer, therefore I also don't know how to fix it. |
Do you use NC 26? This seems to broken :-( Also see #224 |
OK after restarting php8-fpm 👍 |
Hmm... maybe the OPCache of PHP still contained the old code. Can you paste the OPcache configuration of your PHP setup? Depending on your setup you may find this in
The interesting part is the modification check settings like If you follwed some "optimization tips" and disabled the OPCache validation - the perfomance gain is often neglectable and not worth the trouble. By default the validation is enabled, so if neither of the mention options is set, then the OPCache should automatically reload new versions of the source files if needed. |
nextcloud/server#38797 may be related, also mentioning a caching issue due to recent changes in nextcloud itself |
Since I update Nextcloud from Version 26.0.2 to Version 27.0.0 I get the following error message
Autoload path not allowed: /dataDisk/htdocs/nextcloud-27.0.0/apps/keeweb/controller/pagecontroller.php
Trace:
{
"file":"/dataDisk/htdocs/nextcloud-27.0.0/lib/autoloader.php",
"line":166,
"function":"isValidPath",
"class":"OC\Autoloader",
"type":"->"
},
{
"file":"/dataDisk/htdocs/nextcloud-27.0.0/apps/keeweb/appinfo/app.php",
"line":23,
"function":"load",
"class":"OC\Autoloader",
"type":"->"
},
has anyone an Idea how to fix?
for now I had to revert back to Version 26.0.2
The text was updated successfully, but these errors were encountered: