Troubleshooting · Developer docs

Troubleshooting

Grouped by symptom, never by module, because the person with the problem does not know which module has it. One hundred questions across ten pages, each answered with the causes in the order they usually turn out to be true.

Answer API requests

My edit saved, but the site did not change

Published

Pages, blog posts, book pages, FAQ records and custom entity records are versioned. A write makes a new revision, and the site shows only the live one. A patchRevision or revisions write is saved as an inactive revision unless it carries "activeRevision": true inside it, so the request answers "saved successfully" and the live page stays as it was.

Two other causes look the same:

  • The record is unpublished, or scheduled. Your credential is a backend user's, which reads unpublished records by id; a visitor gets a 404. Check signed out.
  • The page cache. A page served from the cache shows the old content until it is refreshed.
HTTP 
PUT /cdna-api/pages/page/1885?properties={id,activeRevision{id},lastRevision}
Content-Type: application/json

{
  "patchRevision": {
    "originRevision": 3488,
    "activeRevision": true,
    "areaContent(navSection)": "API sandbox"
  }
}

# without "activeRevision": true, lastRevision moves and activeRevision does not

An inactive revision already saved can be made live by its id: {"activeRevision": <revision id>} on the record's edit route. See Making a revision live, rolling back and publishing.

In the API reference: Edit a page.

More in API requests

  1. "Invalid reference to related records at activeRevision; expecting an id" when I send activeRevision: true
  2. Updating one area emptied the others
  3. My patch changed the wrong section, with no error
  4. A multiselect area answers 422 "Unexpected associative array encountered"
  5. Custom fields look lost after a write

Was this page helpful?

Your answer goes to the docs team.