Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

Can't access old service with new version #147

Open
zbintiosul opened this issue Dec 24, 2015 · 2 comments
Open

Can't access old service with new version #147

zbintiosul opened this issue Dec 24, 2015 · 2 comments

Comments

@zbintiosul
Copy link

I had version (1) with service:
/api/notification
Created new version (2) with new service:
/api/reset-bagde

Default version is 1.

In version 2 I changed /api/notification logic, only for version 2.
/api/notification was copied in V2 folder and I changed it, but the problem is I can't access v2/api/notification :(

response is:
{
"type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html",
"title": "Not Found",
"status": 404,
"detail": "Page not found."
}

Can someone explain me, why? and is the problem in version of apigility?
"zfcampus/zf-apigility": "1.0.2"

by this video this should work: https://youtu.be/D_mcntk4tXI?t=1241

@zbintiosul
Copy link
Author

Problem is in module.config.php, no configs for V2.
I created a new config V2.module.config.php and I added Code, from module.config.php and replaced \V1\ with \V2.
Also I merged both configs in module.php: module.php.

And now is working and v1 and v2 with services from version 1.

@michalbundyra
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at laminas-api-tools/api-tools#39.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants