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

Can not see created API #323

Open
tasmaniski opened this issue Dec 5, 2015 · 7 comments
Open

Can not see created API #323

tasmaniski opened this issue Dec 5, 2015 · 7 comments

Comments

@tasmaniski
Copy link

Hello,

The problem is simple, I just created a new API via admin-ui.
So new module is created with base structure in it.
Also modules.config.php is updated with new module.

But I can't see that new Api on admin.
which leads that I can't work further with admin - can not create any rpc or rest services.

@gsomoza
Copy link
Contributor

gsomoza commented Jan 25, 2016

Are you by any chance seeing the same errors in the browser's console as one of these tickets: #312 or #325 ? Even if not, I'd follow the same procedure I mentioned there just in case.

Otherwise: did you only create the new API and that's it? No additional code-changes? If so, I'd recommend:

  • Check server logs to see if there were any errors while creating the API. That could have meant that the skeleton was only partially created, leaving things unstable. Having a VCS like Git can help in this situation: not only to revert but also to see to what extent files were created or not.
  • Double-check file permissions (that could have been another cause) and make sure the web server can write to those directories.

@tasmaniski
Copy link
Author

No,

if I first change application config file I will not be able to create API from admin in the app config file.
So the issue was in that - I changed app config before I create any API.

@gsomoza
Copy link
Contributor

gsomoza commented Jan 25, 2016

Oh ok, so the issue is fixed for you now?

@tasmaniski
Copy link
Author

It's fixed for me, but the issue is still there :)
So if someone try to use apigility-admin,
need to be sure that didn't change the config before.

Can be closed ...

@gsomoza
Copy link
Contributor

gsomoza commented Jan 25, 2016

Gotcha, thanks for the heads-up! If people regularly bump into this it might be useful to add some kind of warning about it in the README or other docs.

@tasmaniski
Copy link
Author

Yeah, that would be fine :)

@weierophinney
Copy link
Member

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

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

3 participants