@emdash-cms/admin@1.5.0

Minor Changes

• #4628 1eedf99 Thanks @khoinguyenpham04! - Adds Settings > Sidebars, where each admin user hides and reorders entries in the admin navigation and sections in the content editor's settings sidebar. Every role can open it from the user menu. The layout is saved to the user's account, so it follows them to every browser, and it changes nobody else's sidebars.

  • Navigation entries move within their group or folder. Dashboard always stays first and visible. admin.hiddenNavItems still hides entries for everyone, and those entries don't appear on the page.
  • The editor sidebar order applies to every collection and to new entries. Publish can move but can't be hidden.
  • Reset restores a list's default and offers Undo.

  The editor settings sidebar no longer shows a drag handle on each section. A Customize sidebar link after the last section opens the new page, and a pencil at the bottom of the navigation does too. Section orders that the drag handles saved in a browser are not carried over, so every user starts from the default order.

  GET /_emdash/api/auth/me returns the stored layout as adminLayout, or null. POST /_emdash/api/auth/me accepts { "action": "setAdminLayout", "adminLayout": { ... } } to replace it, or "adminLayout": null to remove it. A layout is limited to 200 IDs per list and 16 KB.

  Browser tests that used the editor sections' "Drag to reorder …" buttons need to change, because those buttons no longer exist. Byline reorder handles are unchanged.

• #4731 84e173f Thanks @emdash-autofix! - Adds optional isVisible(ctx) checks to native content editor panels. Plugin authors can return a boolean or Promise<boolean> using the same collection, saved entry, and locale context as the panel component, for example isVisible: async ({ collection }) => isEnabledCollection(collection).

  The entire section stays hidden until its first check returns true, avoiding empty plugin headings when visibility depends on asynchronously loaded settings. Failed checks hide the panel and log its plugin and panel IDs without unmounting the editor. Panels without isVisible retain their existing behavior, and collections and minRole still filter panels before visibility checks run.

  The first check for a collection, entry ID, and locale keeps the section hidden until it returns true. Checks rerun when the saved entry changes, including after autosaves, saves, and publication. During these rechecks, the section keeps its last visibility decision so visible panels stay mounted and retain local state. A result other than true, a throw, or a rejection hides the section when the check settles. Superseded results and errors are ignored.

• #4573 8d0250c Thanks @khoinguyenpham04! - Updates blocks fields in the content editor so editors can scan a page of blocks, add, move or delete one without scrolling through every form, and edit an open block in the order the page shows it. Lists inside blocks take a shape that fits what they hold, and the admin checks block fields before saving. Every site with a blocks field gets the new editor; stored content, the API, block type schemas and how sites render blocks are unchanged.

  The block list

  • Blocks sit on one sheet and start closed when the edit screen opens. In a read-only entry, every block and list item shows open, since its controls can't be used there. A closed block shows its type's icon, its name, a one-line summary of its text or of its first list's items, and a thumbnail when it has a photo. "Collapse all" and "Expand all" sit next to the field's label, and an open block's header stays pinned while you scroll through its fields. Opening, closing, adding, duplicating, deleting and moving blocks and list items animate briefly, while Expand all, Collapse all and keyboard moves take effect at once. Reduced motion turns every animation off.
  • Each block's ⋯ menu has Add block above, Add block below, Duplicate, Move up, Move down, Move to top, Move to bottom and Delete. Its footer names the block type and version, such as "Hero · version 2", which replaces the "Version N" badge on every block. "Inactive version", "Retired" and "Unsupported" stay on the block as tags.
  • On screens at least 40rem wide with a mouse or trackpad, hovering a block shows +, which adds a block below (Alt-click adds one above), and a handle that drags the block or opens its menu. Both are for the pointer and stay out of the Tab order, so the handle no longer reorders blocks from the keyboard; the ⋯ menu has the same actions. On touch and phone-width screens, ⋯ is always visible. On touch screens, menu buttons, menu items, Expand all, Add item, photo actions and Undo have larger targets, and tapping Add block or a list item opens it without raising the on-screen keyboard.
  • Alt+Shift+Up and Alt+Shift+Down move a block or list item one place from its head or its ⋯ button, keeping focus on it, and a screen reader hears the new position.
  • The block picker opens next to where the block will go, keeps its search, categories and descriptions, shows each block type's icon, and works with the arrow keys and Enter. A block you add opens with its first field focused. A duplicate goes below the original, open or closed like the original, and takes focus.
  • Deleting a block shows a toast with Undo, which puts the block back in its place. While the toast shows, Cmd+Z (Ctrl+Z outside Apple platforms) does the same, unless focus is in a text field, which keeps its own undo. The toast stays for 6 seconds after a deletion made with the mouse, and for 15 seconds after one made with the keyboard, by touch or by assistive technology. Blocks of a retired type, an older version or an unavailable definition ask for confirmation instead and can't be undone, because the server doesn't accept them as new blocks once the deletion is saved.
  • At the field's maxItems, every add action and Duplicate are disabled, and the add buttons explain the limit. Duplicate is also disabled for blocks on an older version of their type, because the server only accepts new blocks on the active version.

  Fields inside a block

  • An open block shows its content first: one-line text, text areas, rich text, photos and lists, each under a small label. The block's headline is drawn larger, two or three one-line text fields in a row share a line, a photo's {image}_caption field sits under it, and text areas start one line tall and grow as you type.
  • Settings follow as rows under a divider, with the label beside the value: switches, choices, numbers, dates, files and links. A button's text and its link share one row, such as cta_label and cta_url. The section ID (anchor_id) waits in a closed Advanced row that shows its value. When the field is narrower than 440 px, each row puts its label above its value.
  • Fields have no box until you hover or focus them, and labels show as written. While a field with a length limit has focus, its character count shows on its label's line, or at the end of its own line in a settings row that sits beside its label. A value that doesn't match the field's pattern reads "Invalid link" in a link field and "Check the format" elsewhere.
  • Enter in a one-line field moves to the next text field in the block or list item instead of saving the entry.

  Lists inside a block

  • A list (repeater field) inside a block takes its shape from its sub-fields. A list with one string or url sub-field is a bulleted type-in list: Enter adds a line after the current one, Backspace on an empty line removes it, the arrow keys move between lines, and pasting several lines adds one item per line. Blank lines you add are never saved, and leaving the list removes them. A list with up to three string, url, number, integer, select or image sub-fields, at most one of them an image, is a table with a column per sub-field, and its image cells open the media picker. Every other list shows expandable items: a closed item shows its title, up to two more of its values and a thumbnail, and an open item edits its title in its row, with its other sub-fields laid out like a block's.
  • In a table, Enter moves down a column and adds a row after the last one, and the Up and Down arrow keys move within a column. A blank row added with Enter goes when focus leaves it.
  • A list with items shows its count next to its label. Hovering an item shows a drag handle and a ⋯ menu with Move up, Move down, Move to top, Move to bottom and Delete; an expandable item's menu also has Add item above, Add item below and Duplicate, in the same order as a block's menu. A duplicated item stays open or closed like the original. On touch and phone-width screens, ⋯ is always visible. Deleting an item, or removing a photo from a block, also shows a toast with Undo. The page has one Undo across its blocks fields, so only the latest deletion can be put back. "Add item" sits at the end of the list and is hidden at the list's maxItems, and Delete is disabled at its minItems.
  • A new list item leaves its sub-fields unset, so an empty link, choice or date sub-field no longer stops the entry from saving, and clearing a link writes null.

  The layout of fields and lists follows field types and slugs, never labels. The naming conventions, and how a list's sub-fields pick its shape and its items' titles, are listed in Build pages with blocks; a field that matches none of them gets a row of its own. Top-level repeater fields keep their current editor.

  Checks and autosave

  • The admin checks block fields with the server's rules: required fields, patterns, lengths, number ranges, whole numbers, choices, safe links, list sizes and required list sub-fields. An empty required field reads "Required". A problem shows in red once you save or publish; before that, a format, length or range problem shows when focus leaves the field, and "Required" turns red when you empty a required field and leave it. Tabbing through empty fields flags nothing. A problem shows on the field's label line, or at the end of a settings row's value, moving to its own line under the value when it doesn't fit. A closed block, list item or Advanced row with a problem shows a red dot.
  • Save and Publish show every block's problems, open the block, Advanced row and list item that hold the first problem on screen, focus it, and announce how many fields need attention. Until they're fixed, a "N to fix" button next to Expand all goes to the next problem with each press.
  • While a block field has a problem, autosave waits, as it does for an invalid URL, and once focus leaves that block, an "Autosave paused" notice names the block and field. Its Show button opens the block and focuses the field. Autosave resumes with your next change once every problem is fixed. A new block's switches start off, so a required switch is never missing.

  Block type icons

  Block types show their icon setting, a Phosphor icon name such as "sparkle" or "chart-bar", in the block list and the picker. A block type without an icon, or with a name that doesn't match a Phosphor icon, shows a generic block icon. The marketing and portfolio templates now give their block types icons. Sites created from those templates before this release keep their stored block types, which have no icons, so their blocks show the generic icon until each block type gets an icon, for example through PUT /_emdash/api/schema/block-types/{slug} or the schema_update_block_type MCP tool.

  The editor's scrollbar

  The content editor's scrollbar shows over the page while you scroll, and under the pointer at the page's edge, instead of taking a strip beside it. Where scrollbars take up room, as on Windows and Linux, the page now keeps its width and stays centered whether or not it scrolls, and no longer shifts sideways when it grows long enough to scroll. This applies to every entry, not only ones with a blocks field.

• #4695 22b87ed Thanks @khoinguyenpham04! - Adds real-time co-editing to the admin editor, off by default for now. With coEditing: true, in collections with revisions, several people can edit an entry at the same time: each person sees the others' avatars, the field each one is in and their cursors in rich text, concurrent rich-text edits merge, and undo reverts only your own edits. A room for each entry saves everyone's edits together, with the same permissions, validation, hooks and revisions as other saves, and changes from the REST API, MCP, the CLI, the visual editor and plugins appear in open editors.

  Without co-editing, opening an entry takes an edit lock, and everyone else can only Open read-only or Take over. With it on, edit locks apply only in single-editor mode, which the editor uses, for example, in collections without revisions, on hosts that can't run rooms, and in browsers that can't open WebSocket connections. Admin tabs opened before co-editing is turned on keep single-editor mode until they reload. Edit with other people describes what editors see.

  • Saved appears once a save holds all of your own edits. After 5 seconds without a connection, the button shows Offline: typing continues and merges on reconnect, and Preview, publishing and the other operations are disabled until then.
  • Publishing, scheduling, unpublishing, discarding changes, restoring a version and moving to Trash first save everyone's edits, then run.
  • Fields other than rich text keep one of two simultaneous changes, except bylines, reference fields and taxonomy terms, which keep what each person adds and removes. Turn into, dragging, deleting, wrapping, joining or indenting a block loses text someone else types inside it at the same moment.
  • Edits that can't merge are saved as a recovery revision.

  Public pages run no new queries, with co-editing on or off. Where rooms run, opening an entry adds a join request and a WebSocket connection. A room saves 2 seconds after the latest change, and at least every 10 seconds while people keep typing, however many people edit. Measured on Node.js with an in-memory SQLite database, saving a 2,000-word entry took 2.27 ms of CPU time at the median (3.83 ms at the 95th percentile), about two thirds of it the site's own draft save. Merging a write from outside the editor took 0.80 to 1.19 ms, and a notification with nothing to merge 0.67 ms (CPU time).

  What should I do?

  Nothing, unless you want co-editing. To turn it on, set the option and rebuild and deploy the site:

  emdash({
  	coEditing: true,
  });

  On Node.js with @astrojs/node, in standalone or middleware mode, co-editing runs in the site's own process and the site starts as before. Check these cases first, which Co-editing on Node.js covers in detail:

  • A reverse proxy must forward WebSocket upgrades on /_emdash/api/content/{collection}/{id}/room. Otherwise each browser session falls back to single-editor mode after three failed connections, and the server logs a [co-editing] warning.
  • Several processes on one database: route each room path to one process, for example by hashing the path, or leave co-editing off.
  • node:cluster workers, including PM2's cluster mode, keep single-editor mode.
  • Another WebSocket handler on the same server must leave room paths alone. Replace a ws server created with { server }, express-ws or @fastify/websocket with a ws server created with noServer: true that handles only your paths, or leave co-editing off.
  • On Node.js 22.16 to 22.20, 23, and 24.0 to 24.8, a server whose only upgrade listener is EmDash's answers upgrade requests on other paths, such as Upgrade: h2c, with 404. Node.js 22.21 and later, and 24.9 and later, serve them as before.
  • While rooms are open, EmDash handles SIGTERM and SIGINT and stops the process up to 5 seconds later. Give process managers a kill timeout over 5 seconds, such as PM2's kill_timeout, which defaults to 1.6 seconds.

  On Cloudflare, sites created from this release's templates already have the binding and the room exports, so they need only coEditing: true. For an existing site, also add the binding and the exports entry to wrangler.jsonc, as Co-editing on Cloudflare shows:

  "durable_objects": { "bindings": [{ "name": "EMDASH_ROOMS", "class_name": "EmDashRoom" }] },
  "exports": { "EmDashRoom": { "type": "durable-object", "storage": "sqlite" } }

  A Worker that uses the migrations array, which can't be combined with exports, adds { "tag": "emdash-rooms", "new_sqlite_classes": ["EmDashRoom"] } to it instead. Then re-export the room classes from the Worker entry point:

  import handler, {
  	createScheduledHandler,
  	EmDashRoom,
  	EmDashRoomSite,
  	PluginBridge,
  } from "@emdash-cms/cloudflare/worker";
  
  export { EmDashRoom, EmDashRoomSite, PluginBridge };
  
  export default {
  	...handler,
  	scheduled: createScheduledHandler(),
  } satisfies ExportedHandler;

  A Worker with its own fetch calls handleRoomUpgrade(request, env) first and returns its response when it isn't null. A site without the binding keeps single-editor mode.

  Changes for API clients and plugins

  These apply only on sites with co-editing on.

  • While people co-edit an entry, it has no edit lock: writes that got 409 ENTRY_LOCKED land and merge into the editor. Writers that send _rev can get 409 CONFLICT more often, because the room saves every few seconds, and MCP publish, unpublish, schedule and discard conflict while the room holds unsaved edits.
  • The lock route's POST deletes user locks while a room holds the entry, instead of granting one.
  • A room saves as one user, the actor, but a save can hold several people's edits. A hook that checks the actor's role before accepting content should check everyone in editedBy. In a room, content:beforeSave hooks get only the fields a save changed, as they do for visual-editor saves.
  • While a room is open, editor-draft requests skip the baseRevision check, and the editor refuses a plugin's patch only when a field it changes was edited after the capture.

  These apply on every site, with co-editing on or off:

  • PUT /_emdash/api/content/{collection}/{id} takes an optional expected object with the bylines and reference selections (references, every page of a field) that a change was based on, as a read returned them. POST /_emdash/api/content/{collection}/{id}/terms/{taxonomy} takes an optional expected list of term ids. When a stored list differs, nothing is written and the request fails with 409 LIST_CONFLICT: read the entry again, apply the change to the list it holds now, and retry. Requests without expected work as before.
  • POST /_emdash/api/content/{collection}/{id}/room joins an entry's room. It needs a signed-in session rather than an API token, and answers { "mode": "single-editor" } unless the site runs co-editing.
  • A migration adds the _emdash_rooms and _emdash_room_updates tables, which hold co-editing rooms. Site transfer never copies them.
  • GET and POST /_emdash/api/content/{collection}/{id}/lock responses include a room field, which is true only while a co-editing room holds the entry.

• #4730 a17a4b3 Thanks @emdash-autofix! - Adds support for publishedAt, createdAt, and updatedAt as a collection's dateField, so editors can see and sort by publication dates without duplicating system timestamps in a custom field. Choose Date column source in the existing content type's settings, or set dateField through the collection update API or a seed file.

  Collections without a configured dateField still show and sort by last-updated. Entries with a missing or invalid configured date display their last-updated date, while sorting uses the configured source.

• #4791 cdfd98d Thanks @khoinguyenpham04! - Adds generated avatars for users without a profile picture. The header, the Users list, the user detail panel and the Authorize device page show a colorful avatar with the user's initials, chosen from their user ID so each user looks the same everywhere. Users without a name show the avatar without letters instead of their email's first letter. On phones, the header's user menu button is now named after the user for screen readers.

• #4729 006cfc0 Thanks @emdash-autofix! - Adds the no-scheduling collection support flag to disable creating or changing schedules in the content editor, calendar, and scheduling API. Scheduling remains enabled by default, and existing schedules continue to run and can be removed.

  To disable scheduling, add no-scheduling to the collection's supports in a seed file, or update an existing collection through PUT /_emdash/api/schema/collections/{slug} or the schema_update_collection MCP tool. For example, a collection with drafts and revisions can use:

  { "supports": ["drafts", "revisions", "no-scheduling"] }

  Preserve the collection's other support values when updating its list. There is no Content Type editor checkbox for this flag, but saving in that editor preserves it.

  If you previously omitted scheduling expecting scheduling to be disabled, add no-scheduling instead. The legacy scheduling value is deprecated and has no effect; it remains accepted for compatibility and can be removed from seed files. If both values are present, no-scheduling takes precedence. Sites that want to keep scheduling enabled do not need to change anything.

  WordPress imports into a collection with no-scheduling keep future-dated posts as drafts and report a scheduling error for each such post.

• #4637 c9696af Thanks @khoinguyenpham04! - Fixes autosave deleting versions saved with Save, and names everyone who edited each version in revision history.

  • An autosave replaces the previous version only when that version is also an autosave. A version saved with Save, or one EmDash creates itself, such as the draft copy an unpublish leaves, stays in Revisions.
  • Each version names everyone who edited it since the version before it, such as "Ana, Ben, and 1 other person", and marks its changes in a neutral color when several people edited it. The publish confirmation names everyone who edited the entry since the published version.
  • GET /_emdash/api/content/{collection}/{id}/revisions and the MCP revision_list tool return editedBy on each version: the people who edited it, latest first, as { id, name }, with null for an account that no longer exists. null means the version names only its author.
  • GET /_emdash/api/content/{collection}/{id}/revisions/editors?since={revisionId} returns everyone who edited the entry in the versions newer than since, newest first and once each, in the same shape. Without since, it returns everyone who edited the entry. It requires content:read_drafts.
  • content:beforeSave and content:afterSave events include editedBy, the IDs of the users whose edits the save holds, latest first. A save with an actor lists only that user. A hook that checks the actor's role before accepting content should check everyone in editedBy.

  A migration adds two nullable columns, kind and edited_by, to the revisions table. Existing versions are not backfilled: they name only their author, and autosave never replaces them. Site transfer leaves both columns out, so transferred versions also name only their author. Once a site has run the migration, earlier EmDash versions can't export it or import into it with site transfer.

• #3716 284fa80 Thanks @swissky! - Adds a staging mode that keeps a site out of search engines until it goes live. Sites created through setup, whether in the setup wizard or by a script that calls the setup API, start in staging:

  • Pages that render <EmDashHead> get a noindex, nofollow robots tag, which overrides SEO panel and plugin robots values. Templates without <EmDashHead> don't get the tag.
  • /robots.txt keeps its usual content so crawlers can read the tag, and isn't cached while the site is in staging.
  • The admin header shows a Staging badge.

  To go live, an administrator selects Go live in Settings > General > Site Status, sends { "staging": false } to the settings API, or uses the MCP settings_update tool. Switch back to staging hides the site again. Staging is visibility only: visitors can still open every page.

  Existing sites are not affected: a site without the setting is live. Site transfer and emdash export-seed don't copy the staging status.

• #2156 25574da Thanks @swissky! - Adds a built-in SMTP email provider. It delivers through any standard SMTP server, such as Brevo, Office 365, Fastmail, Amazon SES or a self-hosted Postfix, on Node and on Cloudflare Workers with the nodejs_compat flag.

  Configure

  Choose SMTP under Settings → Email, or set environment variables:

  • Required: EMAIL_SMTP_HOST, EMAIL_SMTP_USER and EMAIL_SMTP_PASS.
  • Optional: EMAIL_SMTP_PORT (587 when empty), EMAIL_SMTP_SECURE, EMAIL_SMTP_FROM, EMAIL_SMTP_FROM_NAME, EMAIL_SMTP_FROM_EMAIL and EMAIL_SMTP_REPLY_TO.

  Without a sender address, the username is used as the sender, so the admin requires a sender email when the username is not an email address (for example an Amazon SES or SendGrid key). Settings saved in the admin take precedence over environment variables and apply without a restart. Saving them requires EMDASH_ENCRYPTION_KEY, which encrypts the password in the database. Changing the host or username requires entering the password again.

  Port 465 uses implicit TLS and port 587 uses STARTTLS. The provider verifies the server certificate, never signs in before TLS is established, and signs in with AUTH PLAIN or AUTH LOGIN, whichever the server offers. Port 25 is refused. Invalid environment variables are ignored with a warning in the server log.

  Provider selection

  Settings → Email now has a provider dropdown that lists SMTP and any installed email plugins. When its environment variables are set, SMTP delivers email unless an email plugin is active or another provider is selected. Without them, SMTP is used only after you select it. A site with a single email plugin still selects that plugin automatically. In astro dev, the console provider is used only when no other email provider is active, and that choice is no longer saved to the database.

  Send test email now shows the SMTP server's error, for example a rejected login, instead of a generic failure.

  API

  GET /_emdash/api/settings/email also reports the SMTP settings, without the password. The new PUT /_emdash/api/settings/email saves SMTP settings together with the selected provider, or selects a plugin provider. PUT with { "provider": "smtp" } and no settings selects SMTP from its saved settings or environment variables. Sending a test email with POST /_emdash/api/settings/email returns SMTP delivery errors with status 502.

Patch Changes

• #3066 c108e7b Thanks @zaochih! - Accepts BMP images in the Media Library. Uploads through the admin, the media API, and the MCP media_upload tool no longer fail with File type not allowed. BMP files show as thumbnails in the upload dialog, are included in the "Images" preset of the allowed file types editor, and are displayed in the browser instead of downloaded. Fields with their own allowedMimeTypes can list them as .bmp.

• #4520 7bce592 Thanks @khoinguyenpham04! - Updates the Comments inbox table in the admin to match the content list's look, and fits it on phones.

  • The Author and Comment columns are now one Comment column, with each author's name and email above their comment. Clicking the author's name or the comment opens the comment's details. Approve stays on each row that can be approved, and Mark as spam, Trash, and, for admins, Delete permanently move into the row's "…" menu.
  • On right-to-left pages, each author's name and comment keeps its own text direction, so an English comment's closing punctuation stays at its end.
  • When the table is narrower than 42rem (672px), such as on phones and portrait tablets, the Content and Date columns fold away and show under the comment instead. When the table is narrower than 28rem (448px), such as on phones, the author's email is hidden too.
  • The bar that appears when comments are selected matches the content list's: it wraps on narrow screens instead of running off the edge, has a Clear button, and disables its buttons while a moderation request is running. Its Delete button now asks for confirmation before permanently deleting the selected comments. When a bulk action fails, the selection is kept for a retry, and a failed permanent delete, from the bar or a comment's menu, keeps its confirmation open with the error.

  Browser tests that clicked a row's "Mark as spam", "Trash", or "Delete permanently" button need to open the "Actions for comment by {author}" menu first, where those are menu items with the same names. The row's Approve button keeps its name. The select-all checkbox is now named "Select all on this page", and the author's name is a button named after the author alone instead of one that also held their email. The "Author" column header is gone, so tests that locate a columnheader named "Author" need to change. The "Actions" column header is now visually hidden and keeps its accessible name.

• #4174 3d4faaf Thanks @danielmlr! - Fixes the admin continuing to show or hide actions based on a user's old role after an administrator changes that role. The admin now reloads the signed-in user's role when the server refuses a request and when the user returns to the admin tab, instead of keeping the old role for up to five minutes.

• #4495 76f0f53 Thanks @khoinguyenpham04! - Fixes how admin dialogs handle mistakes, slow requests and stray clicks, so each dialog says what is wrong and typed input is not lost by accident.

  In form dialogs, such as the field, relation, byline, menu, section, taxonomy, redirect, folder, domain and invite dialogs, the main action stays available instead of being disabled without a reason. Pressing it with missing or invalid input marks each field that needs attention with a message and moves focus to the first one, and each message clears as its field is corrected. The checks match what the server accepts, so most mistakes are caught before anything is sent, and a name or slug that is already taken is reported on its field in the admin's language. A new select field also needs at least one option, and a new blocks field at least one block type when the site has any, because editors could not fill in either field without them. The field dialog's length and item limits must be whole numbers: before, a limit of 2.5 was saved as 2, and text that isn't a number, such as 1e, saved the field with no limit. Enter submits these dialogs, a double click sends one request, and a dialog with typed input no longer closes when you click outside it or swipe it down on a phone. Cancel and Escape still close it.

  Confirmations that send a request, such as deleting a content type, field, comment or entry, discarding draft changes, replacing an image with its crop, or taking over an entry someone else is editing, now stay open while the request runs, show its progress, and show a failure inside the dialog instead of closing first. A failure shown in a dialog is no longer also reported in a toast, apart from a failed save of the entry's unsaved edits before scheduling or changing its publication date.

  A few dialogs also behave more predictably:

  • Adding a term whose name is already used under another parent suggests a free slug, such as accessories-1, instead of saving it under a different slug than the one shown.
  • A file type typed into a media field's allowed types but not added is saved with the field.
  • A plugin install that asks for more permissions lists them without reporting a failure.
  • Deleting a redirect that was already deleted closes the confirmation instead of showing an error.

  Browser tests

  Tests that expected a dialog's action to stay disabled until its form was valid should press it and check the field's error instead. Tests that waited for failure toasts such as "Failed to delete" or "Failed to schedule" should look for the error inside the dialog. New toasts such as "Term created" and "Invitation sent to …" use the dialog role, so locate dialogs by name.

• #4495 76f0f53 Thanks @khoinguyenpham04! - Updates the admin's confirmation, form and notice dialogs to Kumo's LayerDialog design. Each dialog keeps its title in a fixed header, scrolls its content in a card, and puts Cancel and the main action in a tray along the bottom. On phones, dialogs open as bottom sheets, and most can be swiped down to dismiss. Block Kit button confirmations on plugin admin pages use the same design.

  Inside dialogs, groups of fields share one section heading style, selects fill the width of their column, and paired fields stack on phones. Explanations that used to sit under fields, such as "Slugs cannot be changed after the field is created.", are behind an info button beside the label, which opens on hover, keyboard focus or a tap. Errors, warnings about what an action will do, and format rules the dialog does not check stay visible. Screen readers read an info button's note as the button's description, without opening it.

  Dialogs with Cancel and an action no longer show a separate close (×) button; Cancel and Escape behave as before. In the byline and media folder dialogs, Delete moves from the bottom bar to a row at the end of the dialog that says what deleting does, and the byline avatar shows as a small circle with its actions beside it. Creating a relationship from the field dialog opens it in a second dialog on top, whose Back button returns to the field, and the relation form no longer says it cannot generate a slug before both side names are filled in. A confirmation's message sits under its title and is the dialog's description for screen readers. Form dialogs, such as the field, menu item and schedule dialogs, now also say what they are for under the title, and screen readers read that sentence instead of the whole form. The media picker, media details, media upload, bulk tagging, content picker and section picker dialogs keep their previous layout.

  Browser tests that clicked a dialog's "Close" button should click "Cancel" or press Escape instead. A dialog now takes focus itself when it opens, unless one of its fields takes focus, so press Tab to reach its first control. The plugin permissions and uninstall dialogs are now named by their titles, such as "Plugin Permissions" and "Uninstall Gallery?", instead of "Capability consent" and "Uninstall confirmation". A label locator such as getByLabel("Slug") can also match the new "More information about Slug" button, so pass { exact: true } or locate the field by its role. An info button's note is also in the page as the button's hidden description, so locate the open note with getByRole("tooltip") rather than by its text.

• #4527 5a8c620 Thanks @khoinguyenpham04! - Updates the Media Library's list view to match the content list's look, and fits it on phones.

  • Each file's name is a button, so keyboard users can reach it with Tab and press Enter to open the file's details. Clicking anywhere else on the row still opens the details, and rows can still be dragged onto folders. The open file's row takes the table's selection color instead of a brand tint.
  • When the table is narrower than 42rem (672px), such as on phones and portrait tablets, the Type, Size, and Alt text columns fold away and show under each file's name instead. Long filenames, file types, and folder names wrap or truncate instead of widening the table, and each folder row keeps its name and Edit button in view.

  In list view, browser tests can find a file's name as a button named after the file, such as getByRole("button", { name: "photo.jpg" }). Rows keep their data-media-draggable, data-media-folder-drop-target, and data-drop-active attributes, and the folder controls keep their "Open folder {name}" and "Edit folder {name}" names. A file's type, size, and alt text status are now in the row twice, under its name and in their own columns, with one copy hidden at any width, so tests that look up that text need to scope it to a cell, such as getByRole("cell", { name: "image/png" }).

• #4462 968a23e Thanks @khoinguyenpham04! - Updates the Users and Bylines tables in the admin to match the content list's look.

  On the Users page, clicking a user's name opens their details. The name is a button, so it can be reached with the keyboard now, and clicking elsewhere in the row no longer opens the details.

  On the Bylines page, clicking a byline's name opens the edit dialog, and the Edit button moves into the row's "…" menu next to Delete byline.

  Browser tests that open "More actions for {name}" on the Bylines page should open "Actions for {name}" instead. The byline's name now has the "Edit {name}" accessible name that the Edit button had, so tests that click "Edit {name}" still open the edit dialog. The Bylines panel in the content editor still uses "More actions for {name}". Tests that clicked a row of the Users table should click the user's name.

• #4494 b42176d Thanks @khoinguyenpham04! - Fixes the content list, Users, and Bylines tables running past the edge of phones and other narrow screens, which hid each row's "…" menu until you scrolled sideways. Each table now folds its less important columns away while the table itself is narrow, including when the sidebar leaves it little room, and brings them back when there is room. Tables 42rem (672px) and wider still show every column they showed before.

  • On the content list below 42rem, such as on phones and portrait tablets, each entry's status, locale, and date show under its title, and a sort menu replaces the hidden sortable headers. Columns from the collection's list settings and from plugins are hidden there. The Trash tab shows each entry's locale and deleted date under its title the same way.
  • On the Users page below 28rem (448px), the role shows under the email, with Disabled for a disabled user. Last Login and Passkeys are hidden below 42rem.
  • On the Bylines page below 28rem, the byline type shows under the bio or slug. Website is hidden below 42rem, and now shows on any table that wide instead of only on screens 1024px and wider.

  Hidden values still show when you open the entry, user, or byline, except values that only a plugin column displays. Long emails and slugs wrap, long words in titles break on narrow tables, and long bios truncate, instead of widening the table. The content list and Users page headers move their button to its own line when a long translation leaves no room beside the title.

• #4528 8ce12b7 Thanks @khoinguyenpham04! - Updates the Redirects page's redirect and 404 tables to match the content list's look, and fits them on phones.

  • Each redirect shows its destination under its source, after an arrow, and its group under that, after a folder icon, at every width. Long paths and group names wrap instead of being cut off. A 410 or 451 rule, which has no destination, skips the arrow line. Clicking a redirect's source opens it for editing, and Edit and Delete move into the row's "…" menu. The enable switch, the loop warning, and the "auto" badge stay on the row, and disabled redirects still look faded.
  • When a table is narrower than 42rem (672px), such as on phones and portrait tablets, the Code and Hits columns fold away and show under each redirect, and the 404 table's Last seen column folds under each path. Below 28rem (448px), such as on phones, the 404 table's Hits column folds under each path too. A folded hit count reads like "12 hits". Nothing scrolls sideways on a 320px screen.
  • The 404 table's Create redirect and Mark as Gone (410) buttons match the admin's other buttons and keep their names, their tooltips, and the Mark as Gone (410) button's description for screen readers.

  Browser tests that clicked a redirect's "Delete redirect {source}" button need to open the "Actions for redirect {source}" menu first, where Delete is a menu item with that name. "Edit redirect {source}" now names the source path itself, which is a button, so button[aria-label^="Edit redirect"] finds the source. The Source, Destination, and Group headers are one column header, named "Source Destination Group". The 404 buttons no longer have a title attribute: their tooltips are popups, and the Mark as Gone (410) button's explanation is its accessible description through aria-describedby. A redirect's code and a 404's last seen date are in the row twice, under the path and in their own column, with one copy hidden at any width, so tests that look up that text need to scope it to a cell. A hit count shows as a bare number in the Hits column and as, for example, "12 hits" or "1 hit" under the path.

• #4497 e34b8fe Thanks @khoinguyenpham04! - Updates the Content Types, Block types, Relations, and Byline Schema tables in the admin to match the content list's look, and fits them on phones.

  • On the Content Types page, Edit and Delete move into each row's "…" menu, and code-defined collections offer Edit only. Block types now show as a table below content types.
  • On the Relations page, clicking a relation's slug opens it for editing, and Edit and Delete move into the row's "…" menu.
  • On the Byline Schema page, clicking a field's label opens it for editing, and Edit, Move up, Move down, and Delete move into the row's "…" menu.

  On narrow screens, the buttons in the Content Types, Relations, and Byline Schema page headers move onto their own line instead of running off the edge or crowding the page title. On narrow tables, slugs, sources, types, and link, field, and version counts show under each row's name, and the less important columns fold away.

  Browser tests that clicked a row's own Edit or Delete button, such as "Delete Posts", now need to open the "Actions for Posts" menu first. The Delete items keep their "Delete {name}" names, and the Content Types Edit item keeps "Edit {name}". On Relations and Byline Schema, "Edit {name}" now names the row's slug or label button, which opens the editor without the menu. The byline field reorder items are named "Move up" and "Move down" instead of Move "{label}" up and Move "{label}" down.

• #4537 c2a6857 Thanks @khoinguyenpham04! - Fixes keyboard focus jumping to the top of the page when the row holding it leaves an admin table, for example after deleting a redirect from its "…" menu, moving an entry to the trash, or approving a comment in the Pending tab. Focus moves to the same control in the row that takes its place, so keyboard and screen-reader users can carry on down the list. When no row takes its place, such as when the last row leaves, focus moves to the "…" button of the row above it instead of a control that would act on a row you didn't choose. Focus stays where you put it when you move it elsewhere, such as into a search box or by clicking, and a mouse or touch press cancels a move that is still waiting for a menu or dialog to close.

  On the Redirects page, changes such as toggling a redirect or marking a 404 path as Gone no longer replace the tables with a loading or empty message and drop keyboard focus. After a change, the list still goes back to its first page. Each redirect's switch is now named after its redirect, such as "Disable redirect /old-page", so browser tests that find a switch by its exact name need to include the source path.

• #4503 52b430c Thanks @khoinguyenpham04! - Updates the term list on the Categories, Tags, and custom taxonomy pages to the content list's table layout, which fits phones.

  • Clicking a term's name opens it for editing, and the term's other actions sit in its row's "…" menu. On Categories and custom taxonomies, that menu holds the Edit, Move, Translate, and Delete buttons that were in each row; on Tags, the Edit button moved into it.
  • A term that is the only one under its parent, or the only top-level term, no longer shows Move up and Move down. A term whose parent has no translation in the current locale shows them disabled, and its menu says why, on touch screens and to screen readers too.
  • Deeply nested terms keep their "…" menu in view on phones, and the header buttons on Categories and custom taxonomy pages wrap onto a new line on narrow screens instead of running off the edge.

  Browser tests that clicked a term's Move, Translate, or Delete button need to open "Actions for {name}" first, and tests that opened "More actions for {name}" on a tag open "Actions for {name}" instead. In that menu, Delete is named "Delete {name}" on every taxonomy, and the other items are "Move up", "Move down", and "Translate". The term's name is the button "Edit {name}", which opens the editor without the menu.

• #4495 76f0f53 Thanks @khoinguyenpham04! - Fixes the info buttons beside admin field labels doing nothing when tapped on a phone or tablet. In the content editor, the content list's byline filter, and the filename, alt text and focal point fields in media details, a tap now shows the help, which stays open until the next tap, a tap elsewhere, or Escape. Hovering over or focusing an info button still shows its help, and a mouse click now keeps it open the same way.

• #4151 6d5a10d Thanks @khoinguyenpham04! - Fits the admin calendar's month view to the screen.

  • The month grid fills the window with one-line entries and shows as many per day as fit, folding the rest into "+N more".
  • On wide screens the entry panel sits beside the calendar instead of covering it, and clicking empty space closes it. On phones it is a bottom sheet that swipes down to close.
  • The page title and description give their space to the month. The view switcher and Filter sit above the month's name, which has Today and the month arrows beside it.

  Agenda rows show times in the site's time zone; the side panel and entry tooltips also show the viewer's own time. Month cells no longer draw the red line marking the present; the agenda and the lists of a day's entries still do.

• #4570 e737608 Thanks @emdash-autofix! - Fixes admin pages crashing on missing or unparseable timestamps in imported or legacy data, including publication and scheduling dates in the content editor. Invalid dates now render as empty text, and revision times omit the machine-readable date when it is invalid.

• #4716 b766773 Thanks @emdash-autofix! - Fixes the preview path for Cloudflare Stream videos stuck at 0:00 in the Media Library detail panel. The panel uses Stream's hosted player instead of the browser's native HLS/DASH support. Stream preview URLs ending in /watch are converted to the embeddable /iframe URL. Media providers can supply an optional playerUrl for admin video previews; providers without one keep native video playback.

  If you use Astro's content security policy, allow the Stream player host in frame-src so the preview can load. EmDash's default admin policy already allows HTTPS frames.

• #4595 213904f Thanks @swissky! - Makes Buttons blocks editable in the rich text editor. Imported WordPress button groups now open a form for their layout and for each button's text, URL and style, and /buttons inserts a new group. Saving a group clears a link URL that an earlier editor stored on the group itself, so its card no longer shows that link. Sites with a plugin that registers its own buttons block keep using that plugin's editor.

• #4629 2237d52 Thanks @dmythro! - Fixes the content editor's back button naming its list with the collection's singular label. Screen readers now hear "Back to Posts list", matching the "Posts" link beside it, and translations that name the list get its plural label.

• #4477 cada545 Thanks @emdash-autofix! - Fixes uploads into Media Library folders: empty folders offer an upload action, completed picker uploads stay visible in their destination, and queued or retried files keep their original folder. Each upload into a folder creates a new media item, even if the same file already exists in that folder or elsewhere, rather than reusing or moving existing media. Main-library uploads retain duplicate detection and keep reused items visible in the picker even when the existing item belongs to a folder.

• #4305 d891305 Thanks @iNerdStack! - Fixes the WordPress import review screen labeling the SEO toggle "SEO settings (Yoast)" regardless of which SEO plugin the source site uses. The label now reads "SEO settings", consistent with the rest of the admin and accurate for sites using Rank Math or other SEO plugins.

• #4733 612569b Thanks @emdash-autofix! - Fixes admin browser tabs to show the current page and Site Title, falling back to configured admin branding and then EmDash when Site Title is empty. Content editor tabs include the collection type and entry title and update during client-side navigation.

• #4718 c38a5d5 Thanks @danielmlr! - Completes the German admin translations so German-speaking editors see localized text in the SMTP email settings, the blocks field and its block menu, the Buttons block, field and byline field settings, the site status and domain change settings, the content list's sort menu, comments, redirects, menus, widgets, sections, taxonomies, media folders, user invitations, publishing schedules, the personal sidebar layout settings, the Atmosphere sign-in, the editor's save status, the content type's date column, the dashboard's notice about scheduled content that wasn't published, and the browser tab titles.

• #4545 871cbfa Thanks @danielmlr! - Completes the German admin translations so German-speaking editors see localized text in the forms plugin's digest, autoresponder and field condition settings, the dialogs for deleting a menu item or a widget, the content list's row actions, the redirect group filter and its empty results, the search engine verification settings, empty media folders, the welcome dialog and the hint under "Hide from navigation". The redirect search placeholder is shorter so it is no longer cut off.

• #4535 46e0a54 Thanks @CacheMeOwside! - Adds missing Hindi admin translations and uses Hindi transliteration for authentication terminology.

• #4308 4df65eb Thanks @khoinguyenpham04! - Updates @cloudflare/kumo to 2.15.0. These packages now require exactly @cloudflare/kumo@2.15.0, so sites and plugins that install Kumo themselves should upgrade to that version to match the admin's prebuilt styles. Update emdash and the Forms, Field Kit, AI Moderation and AI Search plugins together: their earlier releases require Kumo 2.6.0, and these plugin releases need an emdash release with this change. Updating only one side leaves Kumo 2.15 next to an admin built for 2.6.

  In the admin, Select menus now open below their field instead of over it, and text sized text-base or text-lg has a taller line (1.5), so labels and headings take slightly more height. Kumo's DropdownMenu now spaces item icons itself, so plugin admin pages should remove any margin classes such as me-2 from the elements they pass as an item's icon.

• #4213 caca761 Thanks @emdashbot! - Reduces CPU usage during image upload confirmation by generating placeholders from small browser thumbnails instead of decoding full-resolution originals. For browser-decodable images, the admin now sends thumbnails fitting a 64-pixel box with both signed and direct uploads, and the visual-editing toolbar sends one with every direct upload. This also enables blurhash and dominant-color placeholders for browser-decodable formats such as WebP and AVIF, which previously had none. New uploads and imports no longer generate placeholders for transparent images, including PNGs, so placeholder backgrounds do not show through transparent areas. Existing media keeps its stored placeholders. Image dimensions, upload validation, content hashing, and responsive image variants remain unchanged.

  Adds the imagePlaceholders configuration option, defaulting to true on every runtime, including Cloudflare Workers. This is one site-wide switch for every upload and import: setting it to false skips all blurhash and dominant-color generation, including from client thumbnails. WordPress imports, MCP uploads, plugin uploads, and custom clients without thumbnails still decode originals when placeholders are enabled, so sites with constrained CPU budgets may choose to turn this switch off.

  Custom clients can send an optional { thumbnail: { contentType, data } } in POST /_emdash/api/media/{id}/confirm. Confirm thumbnails accept JPEG or PNG, at most 32,768 base64 characters and 4,096 decoded pixels. Unusable thumbnails omit the placeholder rather than falling back to decoding the original. Thumbnails also work when originals exceed the 8 MiB download cap; supply the original width and height to record dimensions in that case.

• #4485 faeca6c Thanks @emdash-autofix! - Fixes the content editor toolbar on mobile with a four-column action grid that keeps actions visible without horizontal scrolling. Removes the persistent visible Saved label and shows save failures in a dismissible banner beneath the header at all widths. Preserves screen-reader save announcements. On phones, Settings offers Save draft for collections with drafts and revisions. Tablet and desktop retain their horizontal action layout, and error toasts remain available when the header has scrolled out of view.

• #4421 2bd4a39 Thanks @danielmlr! - Fixes the "not found" errors for themes, marketplace plugins, collections, revisions, and users, which stayed in English in an admin set to another language. They can now be translated like the rest of the admin.

• #3913 252934b Thanks @edrpls! - Fixes failed uploads in the media library upload dialog and the media picker showing only "Upload failed". The server's reason, such as a file over the size limit, now appears under the file, as it already does when uploading into an empty image field.

• #4454 5a9f1bd Thanks @khoinguyenpham04! - Fixes deleting a menu item on SQLite, libSQL, and Cloudflare D1 so the items nested under it are deleted too, as they already were on PostgreSQL. Before, the nested items stayed behind: the site showed them as top-level menu items, but the menu editor no longer listed them, so they could not be edited or removed.

  When a menu item has nested items, the menu editor's delete confirmation now says they will be deleted too.

  Upgrading moves every menu item whose parent is missing from its menu to the top level, where the site already shows it, so the menu editor lists it again.

  What should I do?

  After upgrading, review your menus in the admin. Items left behind by an earlier delete now appear at the top level, where your site was already showing them. Delete any you no longer want.

• #4491 6331f6b Thanks @emdash-autofix! - Fixes uploads into image and file fields inside blocks ignoring the nested field's allowedMimeTypes. Allowed Word documents and other types outside the default upload list can now be uploaded directly from a block's media picker.

  API clients uploading into a block field can send blockType (the block type slug) and blockVersion (the block's version number) with the composite fieldId (<outerFieldId>:<blockKey>:<fieldSlug>) to POST /_emdash/api/media or POST /_emdash/api/media/upload-url. Use the database ID of the collection's blocks field for outerFieldId, and send blockVersion as a string in multipart requests or a number in upload-URL JSON requests. Without the block context, the default upload allowlist still applies.

• #4720 935cdc7 Thanks @danielmlr! - Updates the SMTP Host placeholder in Settings → Email to smtp.example.com, so the form no longer suggests a particular email provider.

• #4235 d6c56fc Thanks @danielmlr! - Fixes Croatian (hr), Russian (ru) and Serbian Latin (sr-Latn) admin messages that described counts such as 21 or 101 as a single item. In Croatian, for example, screen readers now announce "Izbrisan 21 redak" after 21 table rows are deleted, instead of "Redak izbrisan" (row deleted).

• #4708 752cbcd Thanks @emdash-autofix! - Fixes site transfer imports failing with TRANSFER_TARGET_NOT_EMPTY after an interruption while removing starter collections created during setup. Resuming the import now continues that cleanup instead of treating the collection as existing content.

  Settings → Transfer now identifies collections whose deletion failed and explains how to retry them before importing. Deletions that are still in progress do not block a new import; the importer advances their cleanup.

  What should I do?

  If your import was interrupted, reopen Settings → Transfer to continue it, or run emdash site import resume <operation-id>. If the import or a collection deletion failed, follow the guide's retry and recovery steps before starting another import.

• #4742 b8886d9 Thanks @danielmlr! - Fixes WXR imports publishing password-protected WordPress posts for anyone to read on the imported site. The admin import and emdash import wordpress now bring in a post with a WordPress password as a draft, whatever its WordPress status, and list each one on the Import Complete screen and in the CLI output.

  Imports through the EmDash Exporter plugin are unchanged: the exporter does not send post passwords, so a published, password-protected post still arrives published.

  What should I do?

  If you imported a WXR file before this release, or import through the EmDash Exporter, find the entries that WordPress marks as "Password protected" on its Posts, Pages and custom post type screens, and unpublish them in EmDash if they should stay private.

• #4291 40c7657 Thanks @danielmlr! - Fixes the Revisions and Outline sections and the "Created and updated" dates in the content editor sidebar ignoring the reduced-motion preference when they expand or collapse.

• #4413 88e00fe Thanks @emdash-autofix! - Fixes sandboxed content editor panels giving no feedback during slow button actions or form submissions. Panels keep their controls visible and show a pending indicator while interactions run. Additional interactions run in order instead of cancelling the active request, and consecutive duplicates of a running or queued interaction are ignored. Editing the entry allows a new draft-aware action even while the same button’s earlier request is pending. Saved-version refreshes run in the background without replacing the panel with a skeleton, and superseded loads are cancelled so the latest refresh can start promptly.

• #4481 5652829 Thanks @emdash-autofix! - Fixes saved redirect groups being hidden in the admin Redirects list. Editors can now see each redirect's group and filter by an exact group name, including groups outside the currently loaded page.

• #4385 830578b Thanks @Stormster! - Fixes required file, image and reference fields in the content editor showing "This field is required" (or "Select at least one entry.") as soon as the form opens. The message now appears after the editor tries to save or publish, or when they empty a field they had filled, and is announced to screen readers and linked to the field's button.

• #4479 d4d149d Thanks @danielmlr! - Fixes saving content when an optional select or URL sub-field in a repeater row is left empty or cleared. The save failed with "… has a value that is not one of its options." or "… must be a valid URL."

  What should I do?

  An entry with a repeater row that was saved empty before this release can still fail with these messages. Fill in that sub-field, or fill it in and clear it again, then save.

• #4625 5bcccb8 Thanks @swissky! - Fixes Select sub-fields in the repeater field dialog: you can now enter their choices (one per line) when you create or edit a repeater, and saving a repeater no longer erases the choices of Select sub-fields defined through the API, the CLI or seed files.

• #4263 d3e3021 Thanks @henshaw! - Fixes the content editor's and publishing calendar's Preview buttons opening a new browser tab on every click. Previewing an entry again now reloads and brings forward its preview tab when that tab is still open; previews of different entries keep their own tabs.

• #4418 34fc9e0 Thanks @khoinguyenpham04! - Fixes the content editor saving outdated rich text over newer content. When the editor picked up a newer version of an entry, for example after a save from another tab, a plugin, or the API, rich text fields and rich text inside blocks kept the old text, and the next keystroke saved it over the newer version without a conflict notice. Discard changes left the discarded text in place the same way. A read that finished after an autosave could also undo it, so a later edit saved the earlier text.

  Rich text typed while a save is in progress counts as unsaved and goes out with the next save, which shows the conflict notice if the entry changed elsewhere in the meantime.

• #4695 22b87ed Thanks @khoinguyenpham04! - Fixes read-only rich text fields so screen readers announce them as read-only instead of as editable text boxes.

• #4485 faeca6c Thanks @emdash-autofix! - Fixes title and other collection-data edits being reverted when a manual save's refresh finishes. Newly edited collection data is retained while untouched collection fields receive refreshed server values.

• #4640 8b484aa Thanks @swissky! - Makes the first save of a new entry clearer in collections with drafts. The content editor labels the button Save draft, keeps that label visible in narrow editor bars, and the settings sidebar now shows the Publish section with a note that the entry stays off the site until it is published after the first save.

• #4585 372bafa Thanks @khoinguyenpham04! - Fixes the calendar in the scheduling and publication date dialogs (Schedule publication, Schedule changes, Change schedule, and Change publication date) so each day sits centred under its weekday name. The days used to sit at the start of their columns, out of line with the weekday names above them.

• #4782 9db2de8 Thanks @eisenbruch! - Fixes a scheduled entry that publishing refuses staying overdue forever. When the scheduler's publish fails with a validation error or a slug conflict, the entry is now unscheduled and the dashboard lists it with the error message, as it already does when a plugin rejects a scheduled publish. Before, the error went only to the server log, the scheduler retried it on every run, and the calendar said scheduled publishing might not be running.

  ScheduledPolicyRejection.pluginId is now optional, and the record gains an optional code: a record written for a refused publish has no pluginId and carries the publish error's code instead. Code that reads emdash:scheduled-policy-rejection:* records, or narrows with isScheduledPolicyRejection, should handle a missing pluginId.

• #4534 532e78b Thanks @khoinguyenpham04! - Fixes the default SEO title ignoring a collection's titleField. When an entry's SEO title is empty, getSeoMeta() now takes the page title from the collection's title field for entries from getEmDashEntry() and resolveEmDashPath(), and falls back to the title field when the collection sets no titleField or the entry leaves that field empty. The SEO Title placeholder in the editor shows the same value. Before, both read only the title field, so a collection that keeps its titles in a headline field got an empty page title.

  What should I do?

  If a collection's titleField names a field other than title and the collection also has a title field, its pages now take their title from the titleField value. To keep using the title field, pass it as the default title:

  const seo = getSeoMeta(post, { defaultTitle: post.data.title });

• #4717 089716d Thanks @danielmlr! - Fixes non-admin users being able to open admin-only screens in the admin UI. A non-admin who opens a site-level settings page, Users, WordPress import, or a plugin's settings page by its URL now sees an "Access denied" message instead of a screen that fails to load or cannot save. The Settings screen stays open to every role and lists only the pages that role can use.

  Changes for Editors

  Editors could previously open Settings → General, Social Links, and SEO and read their values, although saving them already required an administrator. They can no longer open these pages.

• #4558 c0930c3 Thanks @Yusaku01! - Completes the Japanese admin translation catalog, including form settings, dialog descriptions and validation messages, content management actions, and redirect controls.

• #3008 a3fc555 Thanks @marks-zyz! - Fixes the sidebar active state for a plugin admin page declared with path: "/". The nav target for such a page carries a trailing slash (/plugins/<id>/) while the router navigates without it, so the exact comparison in isItemActive never matched and the item stayed unhighlighted. This affected the shipped forms plugin's "Forms" page. Both sides are now normalized before comparing, and the admin root keeps its exact match.

• #4510 1cf644e Thanks @emdash-autofix! - Replaces the Change domain error "does not serve this site yet" with "Could not verify that … serves this site" when the server cannot verify a domain, including Cloudflare Workers Custom Domains. The dialog now explains that a Worker may be unable to reach its own domain and asks you to confirm the new address shows your site in a browser before using it without the check.

• #4632 96945d3 Thanks @khoinguyenpham04! - Fixes rich text block keys changing on every save. Blocks added in the editor now keep the same _key from save to save, so saving the same content twice gives identical Portable Text. Saving also stops changing a few stored shapes:

  • List items that start at a nested level keep their level.
  • Line breaks inside table cells keep their spans.
  • A span marked both subscript and superscript keeps subscript.
  • Two links that share a mark definition keep their own destinations.
  • An empty last line, such as the one the editor adds after a final image, isn't saved.

  If a plugin block is deleted while its edit dialog is open, the dialog now stays open, keeps what you typed, and says the changes can't be saved. Before, it closed and dropped the input.

• #4752 a5223a9 Thanks @kegren! - Translates the Swedish admin strings added since 1.2, including the revision history, email settings, block fields, site visibility and the forms plugin.

• #4401 e21e01e Thanks @emdash-autofix! - Fixes responsive table widths in the admin editor with Tiptap 3.32.0. Gives both editors' textboxes accessible names for screen readers.

  Pins the editor's Tiptap dependencies to exactly 3.32.0 so installations use the version covered by the editor tests. Code-block highlighting keeps its existing lowlight extension version. Sites or plugins that share Tiptap dependencies with EmDash should align them to 3.32.0 to avoid installing multiple copies.

  Links applied at an empty caret now end when you type a space, following Tiptap's updated behavior. In the visual editor, typing a space at the end of an existing link also ends the link. Text typed after that space is not part of the link.

• #4600 eefe351 Thanks @emdash-autofix! - Fixes the entry editor's taxonomy picker showing an enabled create button with no name entered. The picker now explains that the input can search or create terms, disables creation for an empty name, and shows a hint to type a name first.

• #4379 65b1679 Thanks @Yusaku01! - Fixes category and tag pickers creating or selecting terms when Enter confirms an IME composition.

• #4533 bb15813 Thanks @khoinguyenpham04! - Fixes the rows widget option on text fields having no effect in the content editor. A text field that sets options.rows to a positive whole number now renders a textarea with that many rows, so fields that already set it change height after upgrading. Text fields without the option keep the 10-row default.

• #4776 98d16d8 Thanks @emdash-autofix! - Fixes the content editor silently overwriting another editor's changes after a background refresh followed by undoing unsaved edits. The next save now reports a conflict instead of sending older field values with the newer revision token.

• #4759 93ad617 Thanks @emdash-autofix! - Fixes the content editor's Publish now, Publish changes, and Unpublish buttons to show a spinner and stay disabled while the request is in progress.

• #4613 a3da98d Thanks @dmythro! - Completes the Ukrainian admin translation, so Ukrainian-speaking editors see every admin screen in Ukrainian. Existing Ukrainian texts that left "passkey", "magic link" or "handle" in English, or had grammar and wording mistakes, are corrected.

• #4666 652d957 Thanks @dmythro! - Fixes WordPress export file (WXR) imports leaving out menus. The admin said the WXR path imports menus, but the import created none, and the review screen didn't list them. The review screen now lists a file's menus by their names in WordPress, with the switch that exporter imports already have, and the import creates them with their nesting and with links to the imported pages and posts. An item without its own label shows the linked entry's title, as in WordPress. On a site translated with Polylang or WPML, each menu takes the language of the pages it links to. An item that links to a post type archive links to the archive of the collection that the post type was imported into. Items that link to a category or tag archive, to content the import left out, or to one of several pages that share a slug in the same collection and language are skipped and counted in the import result. So is a Polylang language switcher, which only Polylang can turn into language links. A menu that already exists under the same name and language is left as it is.

• Updated dependencies [76f0f53, 7d48e95, 4df65eb, 4e95f4f, 34ff31a]:

  • @emdash-cms/blocks@1.5.0
  • @emdash-cms/plugin-types@0.6.1
  • @emdash-cms/registry-lexicons@0.7.1
  • @emdash-cms/registry-client@0.7.2