Skip to content
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

Can't access old service with new version #39

Open
michalbundyra opened this issue Jan 10, 2020 · 1 comment
Open

Can't access old service with new version #39

michalbundyra opened this issue Jan 10, 2020 · 1 comment

Comments

@michalbundyra
Copy link
Member

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


Originally posted by @zbintiosul at zfcampus/zf-apigility#147

@michalbundyra
Copy link
Member 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.


Originally posted by @zbintiosul at zfcampus/zf-apigility#147 (comment)

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

No branches or pull requests

1 participant