You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I converted a collection type (intro) into a single type. Afterward, I wasn't able to receive the content anymore. I looked through the issues a little bit and saw a similar issue where it could be solved by using populate, which didn't work out for me.
Bug report
Required System information
Describe the bug
I converted a collection type (intro) into a single type. Afterward, I wasn't able to receive the content anymore. I looked through the issues a little bit and saw a similar issue where it could be solved by using populate, which didn't work out for me.
In Postman I tried these calls:
GET http://localhost:13370/api/intro
GET http://localhost:13370/api/intros
GET http://localhost:13370/api/intro?populate=*
GET http://localhost:13370/api/intros?populate=*
They all failed with that response:
{
"data": null,
"error": {
"status": 404,
"name": "NotFoundError",
"message": "Not Found",
"details": {}
}
}
I correctly set the permissions and the bearer token, because all requests on collection type work well.
Steps to reproduce the behavior
Expected behavior
I expect to get the data back I entered into the entry of a single type without 404 error.
The text was updated successfully, but these errors were encountered: