New to Apigility, stuck in "Getting Started", help .......

[peopzen]

Hello guys,
I am new to Apigility and get stuck in first API in "Getting Started".

Created 'Status' API, created 'Ping' service. When creating field "ack", it told "Error saving field" and "Error during the API communication", I couldn't create a new field. I tried deleting "Status" API, but it told me "Error during the delete of the API" and "Unable to delete API".

Anyone has some ideas about the issue?

My platform: Win7+IIS7.5+PHP7.0.8, virtual host on the local machine.
Installing Apigility-skeleton 1.4.1 by Composer. Setup development mode; no opcode cache, disabled php display_error; full control to "config" and "module" folders.

[peopzen]

ok, I found a simple issue: Composer didn't properly download all necessary components. My installation is not complete. I used php command to download the full skeleton, it works now.
Be careful when using Composer command.

[michalbundyra]

@HAOlle Can you provide here more information for further references?
What was the composer error? How did you resolve it?

If this issue is resolved please close it. Thanks!

[peopzen]

I noticed it wasn't completely downloaded when using composer to get the package. Sorry, I didn't copy the error message.
I used php command to get the package again and ran the built-in server. It works fine. However, I copied it to IIS vhost folder and set up URL-rewrite and full control to "config" and "module" folders. It still doesn't work when adding Fields in a Service.
I think it is a IIS configuration and permission issue.
Anyone can help? Thanks in advance.

[morrsky]

I experience similar error when my file permissions are not correct.
I guess you have copied as User.. Can you confirm that the files are writable by the server?

[peopzen]

Both "module" and "config" folders (and subfolders and files) are set "full control" to User and IIS_ISUERS. The website folder is owned by Administrator. any settings I missed?

[weierophinney]

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