-
Notifications
You must be signed in to change notification settings - Fork 64
Deleting API Doesn't Return APIs #222
Comments
This error looks to me like the Short term solution: manually remove the "test" module entry from that file, if it's still there. Long term: Is it at all possible you're running on a Mac with an SSD, by any chance? If so, we observed some problems with that combination whereby the SSD takes > 1s to commit file changes, which can lead to the situation you're seeing. As a result of these observations, we made some changes in the admin UI to add delays between receiving a success confirmation and sending off the request to retrieve the list of modules. You can try this out by running Please let me know what you observe. |
I get same error on 1.0.4. I have ubuntu with SSD. Disable opcache in php.ini resolved issue. I think cacheEnabledAction in zf-apigility-admin should chect this, but now it's disabled. |
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#46. |
When deleting an API, the API gets deleted, and the page then goes to a blank APIs page without the other APIs. It clears the API list but fails to fetch the new API list. The following error is returned from GET after a successful DELETE.
The text was updated successfully, but these errors were encountered: