EmDash 1.4: fewer lost edits. What changed for your site

The short answer
Do you need to do anything about EmDash 1.4? No, unless someone runs your site and the Media usage tracking screen asks for a repair after the update. EmDash 1.4, released on October 29, 2026, is a release of fixes, most of them about not losing work, and it has no database migrations.
- Your edits are safer. If you click away right after typing, the editor now sends your edits before it leaves, and warns you if it can't.
- Two saves no longer overwrite each other in silence. If two tools save the same version of a page at once, the second one is now refused instead of quietly replacing the first.
- You can hide admin areas you don't use, such as comments or widgets. Hiding tidies the menu. It doesn't lock anything.
- Some sites need one repair after upgrading. Whoever updates the site opens Settings → Media usage tracking and repairs it if it shows Needs attention.
EmDash's own post has the full list: EmDash 1.4: fewer lost edits and many small refinements. By EmDash's count it brings 75 changes from 22 contributors. This post covers only the ones an owner or an editor would notice, and what to do about each.
What you'd notice
Most of 1.4 fixes something you already use rather than adding something new. EmDash calls it "a release of refinements." Here is what changes on screen, and whether it asks anything of you.
What changed | What you'd see | Do you need to act? |
|---|---|---|
Edits are sent before you leave the editor | Follow a link right after typing and your edits go with you. If they fail, the next page shows "Autosave failed". If they can't be sent at all, the editor asks before you leave | No |
Switching entries during an autosave keeps your work | Jumping to another entry and back no longer brings an older copy back over your latest edits | No |
Two saves of the same version | The second save is refused with a conflict instead of silently replacing the first. This mostly affects AI assistants or scripts editing at the same moment | No. If a tool reports a conflict, reopen the entry and make the change again |
Menus on D1, Cloudflare's database, save completely or not at all | A menu translation that fails partway no longer leaves an empty translated menu behind | Only if one failed before 1.4: delete the empty menu and translate it again |
Admin areas you don't use can be hidden | A shorter sidebar, if whoever set up your site turns the option on | No. It's optional |
A tidier editor and clearer scheduling | Even spacing between blocks, no empty caption lines under images, and a scheduling dialog that opens on the next whole hour and says what's wrong when a date is missing | No |
Each row's actions sit in one menu | In the content list, Edit and Move to trash sit under a "…" menu. Clicking an entry's title still opens it | No |
Cached pages update after you delete or unpublish | On Cloudflare, a page you remove or unpublish stops showing a stale copy | No, unless your developer relies on caching headers (see below) |
The admin in three more languages | Simplified Chinese, Brazilian Portuguese and Turkish are now complete | No |
The Forms plugin, now 0.2.12 | Editors can now view forms and their submissions. A reply to an instant notification email now reaches the person who filled in the form | Check which of your staff are Editors and which are Admins |
The edit fixes are the ones that matter day to day. Before 1.4, EmDash says, edits to an existing entry "were lost if you followed a link before autosave ran." Now the editor sends them first, and tells you if it couldn't.
The save-conflict fix matters more if you let AI assistants work on your site. Every EmDash site has a built-in connection that lets assistants such as Claude or ChatGPT draft posts and update pages, within the permissions you give them (EmDash docs). Before 1.4, two of them saving the same version of an entry could both report success while one quietly lost its change. On D1, Durable Objects and PostgreSQL, the second save now returns a conflict, in the release post's words, "as a save based on an outdated version already did."
What you need to do, by situation
What you do depends on who runs your site. For most owners the answer is one question to one person.
Someone looks after your site
Ask them one question: "Have you moved us to EmDash 1.4, and did Media usage tracking show Ready afterward?"
If the answer is yes, you're done. If they haven't updated yet, there's no need to rush. EmDash doesn't describe 1.4 as a security release, and under its versioning rules a minor release "carries backwards-compatible features" (EmDash docs). It is a sensible update to make soon, not an emergency.
Sites we host get this update as part of hosting, once it's checked.
If your site uses the Forms plugin, it's also a good moment to check who on your staff holds which role. In 0.2.12, Editors can view forms and submissions, while changing or deleting them, the export and the webhook address stay with Admins.
You or your developer run it
Read the Upgrade notes in EmDash's release post before you start, then follow EmDash's Update EmDash guide. The guide covers a dry run, the update itself, the work order it writes for your project, and the build. Four things in 1.4 are worth knowing first:
- No database migrations. The release post says so plainly.
- A repair after upgrading, on some sites. Collections with a reference field named
titleornamerecorded no media usage when entries were saved. After upgrading, open Settings → Media usage tracking and wait until it shows Ready. If it shows Needs attention, the release post gives the repair for each affected collection. - Two narrower repairs. One covers a searchable reference field that fails to save. The other covers the empty translated menu a failed translation left behind on D1. Both are in the release post's "Repairs after upgrading" list.
- Caching headers. Pages that use EmDash cache hints no longer send an automatic
Last-Modifiedheader, and some lose an implicitCache-Control: no-cacheheader. A developer who relied on either sets their own, as the release post explains.
One more thing an owner should know: the updater changes EmDash's own packages, not your site's design. EmDash's guide says it "leaves the site's application and configuration files" alone, so the layouts and styles your site was built from stay as they are.
You're still on WordPress
Nothing to do. EmDash releases don't touch a WordPress site. What 1.4 can tell you, if you're deciding whether to move one day:
- EmDash ships often. It published five releases in October 2026 alone, by npm's dates: 1.1 on October 1, 1.2 on October 6, 1.3 on October 15, 1.3.1 on October 18 and 1.4 on October 29.
- Someone still applies updates. EmDash's update guide is written for "site operators", the people who run a site. A move to EmDash changes what upkeep looks like. It doesn't remove it.
- The fixes are about the basics. Not losing edits, not overwriting a colleague's save, menus that don't half-save. That is the kind of release you'd hope to see from a young platform.
If you want the bigger picture first, start with EmDash vs WordPress: what changes for a small business site, or what EmDash is, in plain English.
When to stay on WordPress
If your WordPress site works, costs you little to keep up and you're happy editing it, stay where you are. A release like this one isn't a reason to move on its own. Stay put as well if your site's core is a store, a member area, an online course or a plugin feature you rely on every day. Those sites are not a fit for a move yet.
What EmDash 1.4 didn't change, and what isn't proven
Four limits are worth keeping in mind, because a release post describes what its makers intended, not what every site will see.
- Hiding an admin area doesn't lock it. In EmDash's words, "Hiding an area only removes the links to it." The pages and their addresses stay the same, so anyone with the URL and the required role can still open them. To control who can change what, use roles, not hidden menus.
- The conflict protection applies where EmDash says it does: on D1, Durable Objects and PostgreSQL.
- The new AI Search plugin is optional. It is new in this release, and it does nothing to your site unless someone installs it.
- The counts are EmDash's own. The 75 changes and 22 contributors come from the release post.
We cover EmDash releases for owners as they ship. For the last EmDash news before this one, read what the EmDash Build alpha does and doesn't do yet.
If you want your current site on EmDash
If you want your existing WordPress site on EmDash and Astro, with your pages, URLs and forms intact, that is a verified move, and it is what we do. Before launch, we check every URL, redirect, form, title, description, canonical and schema against your live site, and your WordPress site stays live until you approve the new one. Our fit guide says which sites should move and which should wait.
The conversion starts at $790 for up to 25 pages, as listed on our pricing. To see whether your site is a good fit and what it would cost, check your site for free.
Frequently asked questions
What is new in EmDash 1.4?
EmDash 1.4, released October 29, 2026, is mostly fixes. Edits are sent before you leave the editor, two saves of the same version no longer overwrite each other silently, and menu changes on Cloudflare's D1 database save completely or not at all. Admin areas you don't use can be hidden. It has no database migrations.
Do I need to update to EmDash 1.4 right away?
There's no rush for most sites. EmDash doesn't describe 1.4 as a security release, and under its versioning rules a minor release adds backwards-compatible features. Whoever runs your site should update when convenient, then check that Media usage tracking shows Ready.
Will updating to EmDash 1.4 change how my site looks?
It shouldn't. The updater changes EmDash's own packages, not the layouts and styles your site was built from. The editor inside the admin looks tidier, with even spacing between blocks, but visitors see the same site.
What does Needs attention in Media usage tracking mean?
It means EmDash's record of which entries use which images is incomplete for some collections, a gap 1.4 fixed for one kind of field. Whoever runs your site repairs each affected collection using the step in EmDash's release post. The repair rebuilds that record. It doesn't touch the images themselves.
Does hiding an admin area keep people out of it?
No. Hiding removes the link from the sidebar and the command palette, but the page stays open to anyone with the address and the right role. To control who can change what on your site, use roles, not hidden menus.
Should EmDash 1.4 make me move off WordPress?
Not on its own. If your WordPress site works and you're happy editing it, stay. EmDash shipped five releases in October 2026, and 1.4 fixes basics like lost edits. That is a reason to keep watching, not to rush. Stores, member areas and online courses are not a fit yet.