-
Notifications
You must be signed in to change notification settings - Fork 7
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
restapi.php broken in 2.1.4 #74
Comments
Hi @bcleonard thanks for the feedback. You may be the first besides myself to comment on this :-) The REST API is something fairly new From my perspective the Of course, that's assuming you do have a working base URL for your installation. For example, in my Ubuntu wsl2 distribution I have a symlink from the COPS source repo to /var/www/html/cops with /var/www/html served with Apache, and I can access the REST API via http://localhost/cops/restapi.php for development, and similarly from my Synology NAS in production. Does that help at all? |
Hmm, actually never mind the dev mode - I moved nikic/fast-route to production around version 2.1.3 already. The comment on the working base URL remains though, and yes, the functionality has changed a bit since the initial 1.3.6 release - sorry for the confusion. The equivalent of the old |
Note: if you have a setup that requires the use of
|
Hi @bcleonard with the input above were you able to fix your homepage link? |
With nginx in front of the COPS site, you probably need to double-check if it is configured to support PATH_INFO first - see https://www.nginx.com/resources/wiki/start/topics/examples/phpfcgi/ Then you may need to specify Once they're configured to reflect how you set up your environment, you should be good to go for all future versions :-) |
Glad it worked out :-) BTW, if the PATH_INFO hadn't worked out, only a few /restapi.php/ paths are specific to the REST API itself. For all standard COPS pages you could always fall back to using the old |
restapi.php is broken starting with release 2.1.4 (I suspect it was 2.1.3, but that was unreleased).
I noticed it when my homepage link using the api broke after the upgrade to 2.3.1.
When accessing /restapi.php, I get the following error: Fetch error Not Found /restapi.php/openapi
Please see the attached screenshots for a working/not-working.
I suspect that the openapi stuff has not been fully implemented. If that is the case, I recommend that you roll back the changes until its fully baked.
The text was updated successfully, but these errors were encountered: