Changes do not save
Get your edits to stick. A failed save is almost always something between the browser and Drupal, an ended session, or content that was edited outside the builder.
I see "Server error: Unable to save field"
When you click Save, the editor first asks /dxpr_builder/csrf
for a fresh security token, then sends the page to
/dxpr_builder/ajax. If either request fails, you see this message
and nothing is saved. Open the browser's Network tab, click
Save again and read the status code of those two requests.
- 403, and nothing new in Recent log messages. A web
application firewall, mod_security rule or proxy rejected the
request before it reached Drupal. A typical sign: an empty page
saves, a long page does not. Ask your host to allowlist POST
requests to
/dxpr_builder/ajax. If a security or anti-spam module inspects every POST request, exclude that path. - 403 after the page was open for a long time. Your session ended, or your account lost Edit with DXPR Builder. Log in again in a new tab, come back and click Save. Your edits are still on the page.
- 500. PHP failed during the save. Reports > Recent log
messages (
/admin/reports/dblog) shows the error. For "Allowed memory size exhausted", raise PHPmemory_limit. - 404 or 400. You edit a language the content does not have. The log says "Attempted to save non-existent translation". Add the translation on the page's Translate tab first.
My layout is gone after I edited the node form
CKEditor on the node edit form rewrites builder HTML, and a restricted text format strips its classes and attributes.
- Go to Structure > Content types > (type) > Manage form display.
- Hide the body field from the form, or give it Full HTML as its default text format.
- Edit builder content only through the builder.
To get the layout back, open the page's Revisions tab and
revert to the revision before the form edit. Builder saves show
the log message Saved with DXPR builder.
I saved, but part of the page reverted
Each builder container on the page has its own Save button, for example a body field and a block. Save every container you edited before you leave the page. The browser warns that a field "might have unsaved changes" when you leave too early.
Undo stopped working
The editor shows "Failed to save history state, cannot undo and redo actions because the content item is too big." The undo history lives in the browser's local storage, which has a size limit. Clear the site data for this domain in the browser's settings. That removes the undo history only; saved content is not affected.
Confirm the fix
Click Save. The editor reports "Saved field" with the field
name, and the network tab shows a 200 on /dxpr_builder/ajax.
Reload in a private window: the change is still there.
What's next?
Saving content for how revisions and publishing interact with builder saves.