collectiveaccess / providence

Cataloguing and data/media management application
GNU General Public License v3.0
290 stars 166 forks source link

service.php returning fatal error on develop branch #1502

Closed Monica-Wood closed 9 months ago

Monica-Wood commented 9 months ago

System set up:

When navigating to www.example.com/providence/service.php presented with an uncaught fatal error and log states ERROR --> ApplicationException: Invalid controller path

Expect to return JSON with something like {"ok":false,"errors":{"message":"Action is not defined","extensions":{"category":null},"locations":null}}

To track down that the error comes from the develop branch, I confirmed that on my dev server which is running /dev/php8 branch and php 7.4 (using same directory/nginx config setup) is working as expected as do other systems running dev/php8 code, but with different nginx config (providence being the domain root). I then switched my dev server to the develop branch (doing the usual composer updates etc.) and it now shows the same 'uncaught fatal error'.

Monica-Wood commented 9 months ago

Addition to this. It looks like the /OAI and /simple end point is still working, just not the JSON/REST API endpoints.

kehh commented 9 months ago

I think you have to add a json to the path after service.php

kehh commented 9 months ago

(the json services are preparing for deprecation iirc)

collectiveaccess commented 9 months ago

dev/php8 puts the graphql api on service.php. json services are in services.php/json

Monica-Wood commented 9 months ago

OK. So the reason things aren't working at service.php without the json is because the graphql hasn't been merged into develop yet?

collectiveaccess commented 9 months ago

yes