Issue Summary

Bookmark card has few minor issues atm as listed below -

• Better error message handling: Currently bookmark card fails with Unable to parse URL error in case of all failures including insufficient metadata available. We should differentiate between "unable to parse" and "page has insufficient metadata" cases and show appropriate error message to avoid confusion (ref: ht

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

Hi folks many thanks for your great work.

Describe the bug

Date and datetime can be improperly persisted.

To Reproduce

• Add the following section to a config file

  - name: test
    label: Tests
    create: true
    folder: "content/_tests"
    fields:
      - name: title
        widget: string
      - name: date
        widget: date
        format: YYYY-MM-

Summary

Add a site AMP version.

Basic example

Nuxt.js has an example: https://github.com/nuxt/nuxt.js/tree/dev/examples/with-amp
Gatsby AMP Plugin: https://www.gatsbyjs.org/packages/gatsby-plugin-amp/

Motivation

The AMP Project support is very important to accessibility and Google's Pagerank. So, it could will be awesome had this support in Gridsome.

#62 我的环境

期望行为

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

当前行为

yaml出现错误

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

The docs recommend using rewrites instead of routes but AFAIK it's not possible to use methods in the rewrite config.

I tried it with now dev and it stoped with this error:

Error! Invalid rewrites property: [0] should NOT have additional properties

I'm guessing this feature has not been implemented and if that's the case please consider this a feature request.

The api server and webpack dev server should be restarted when the redwood.toml configuration is modified.

Related: #478

Bug report

In the documentation on the wyam website, and also in the Image module, there are references to SetJpegQuality, but this function was removed in Wyamio/Wyam@b9c8b6d#diff-32ea30b39bc5a67b2c9f6c3e331a6b69

Was this removed as a mistake, or in the course of some other refactor that did not get updated documentation?

- Do you want to request a feature or report a bug?
Feature

It would be helpful to see a flow of which endpoints are called in what order and how—for user/pass and for OAuth

When redeploying the recent changes made by @mraerino, I had to perform a by hand migration:

ALTER TABLE test_invoice_numbers DROP COLUMN id;
ALTER TABLE test_invoice_numbers ADD PRIMARY KEY (instance_id);

We should automate this if we can. Close this issue by doing that, or deciding not to and documenting it somewhere.

Opening this issue to see how others like myself can get involved with helping to further develop this. Happy to also help with anything like contributing documentation as well.

Following the README.md to set .env as follows:

HEADLESS_CMS_GITHUB_TOKEN=examplekey123abc
HEADLESS_CMS_TWITTER_CONSUMER_KEY=examplekey231abc
HEADLESS_CMS_TWITTER_CONSUMER_SECRET=examplekey321abc
HEADLESS_CMS_TWITTER_ACCESS_TOKEN_KEY=examplekey231abc
HEADLESS_CMS_TWITTER_ACCESS_TOKEN_SECRET=examplekey321abc

When running npm start I still get:

> headlesscms@2.0.0 s

I'm getting 404 errors whenever I try to reload any post. Navigation between pages from the UI works fine, but I cannot reload a post or even go to the post page directly.

This includes sample post & page as well as newly created posts:
http://localhost:4000/sample-page
http://localhost:4000/hello-world

Can you please help?

Thanks a lot for this great project!

I've just given this a try (using the add to netlify command).

I feel it could do with a bit more instruction for getting it to run locally.

I presume some form of:

npm install
npx eleventy

When installing Ghost there isn't an option to specify a custom database port for MySQL. If you're installing it on a managed database service that runs on a non-standard MySQL port this means you have to install ghost initially and let it fail, then manually edit the config.production.json file and add the port, then restart ghost.