Can not see created API

laminas-api-tools / api-tools-admin

Laminas API Tools Admin module

https://api-tools.getlaminas.org/documentation

BSD 3-Clause "New" or "Revised" License

13 stars 21 forks source link

Can not see created API #27

Open weierophinney opened 4 years ago

weierophinney commented 4 years ago

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.

Originally posted by @tasmaniski at https://github.com/zfcampus/zf-apigility-admin/issues/323

weierophinney commented 4 years ago

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.

Originally posted by @gsomoza at https://github.com/zfcampus/zf-apigility-admin/issues/323#issuecomment-174639609

weierophinney commented 4 years ago

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.

Originally posted by @tasmaniski at https://github.com/zfcampus/zf-apigility-admin/issues/323#issuecomment-174655779

weierophinney commented 4 years ago

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

Originally posted by @gsomoza at https://github.com/zfcampus/zf-apigility-admin/issues/323#issuecomment-174656428

weierophinney commented 4 years ago

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 ...

Originally posted by @tasmaniski at https://github.com/zfcampus/zf-apigility-admin/issues/323#issuecomment-174658887

weierophinney commented 4 years ago

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.

Originally posted by @gsomoza at https://github.com/zfcampus/zf-apigility-admin/issues/323#issuecomment-174663073

weierophinney commented 4 years ago

Yeah, that would be fine :)

Originally posted by @tasmaniski at https://github.com/zfcampus/zf-apigility-admin/issues/323#issuecomment-174665022

rockblings commented 4 years ago

I am having the same issue. i created a new service using the laminas api tools admin ui but it just created a single empty folder under the API directory.