Describe the bug
Find-one endpoint /resource/:id responses with 500 status code instead of 404, this happens with MongoDB setup.

Steps to reproduce the behavior

1. Setup Strapi with MongoDB configuration.
2. Create a collection (resource).
3. Give findOne access to the public.
4. Send a request to /resource-name/any-invalid-id.

Expected behavior
404 response.

**Sys

Describe the bug
If you use github as backend the following basic setup is required:

• run your own github auth server backend (see https://github.com/vencax/netlify-cms-github-oauth-provider) - https://mygithub-auth-backend.org as an example
  -create oauth app in github and configure callback url pointing to your github auth server backend (https://mygithub-auth-backend.org/callback)
• set

#62 我的环境

期望行为

yaml格式和properties格式的代码应该正常显示

当前行为

yaml出现错误

properties代码出现错误
<img width="867" alt="WX20191019-022128