emdash-cms/emdash @emdash-cms/admin@0.33.0

on GitHub

Minor Changes

• #2267 e8048e4 Thanks @DavidPivert! - Adds an explicit sidebar order for collections. Drag the rows on the Content Types screen, or set sortOrder in a seed file, and the admin sidebar follows that order instead of sorting alphabetically by slug. Collections without a sortOrder keep the alphabetical order and are listed after the ordered ones, so existing sites look the same until someone reorders. reorder is now a reserved collection slug.

• #2264 741c40c Thanks @DavidPivert! - Adds a hidden flag to collections that omits their auto-generated entry from the admin sidebar. Hidden collections keep working everywhere else — REST API, MCP, plugin hooks, and their editor at /_emdash/admin/content/<slug> — so a plugin that owns a collection end to end can point editors at its own admin UI instead of a raw CRUD list. Set it in a seed file ("hidden": true) or via the schema API.

• #2353 ea4c39b Thanks @MA2153! - Adds manual ordering for taxonomy terms. Move terms up and down from the Taxonomies screen, and term listings — getTerms() and the terms REST endpoint — return them in that order. The terms attached to a single entry are still listed alphabetically.

  Existing terms keep the order they display in today, now stored explicitly instead of derived from their labels. Terms added afterwards go to the end of their sibling group rather than slotting in alphabetically — if you want a taxonomy alphabetical, order it that way once and it stays.

  A term's position is shared by all of its translations, so ordering a taxonomy in one locale orders it everywhere. On upgrade that means each taxonomy keeps the alphabetical order of the locale its terms were first written in, and other locales are re-sorted to match; reorder once from the Taxonomies screen if you want something different. Sites that need a genuinely different order per language should use separate taxonomies.

  Also fixes moving a term to a new parent only taking effect in the locale you moved it in, which left the term nested in that locale and still at the top level in the others. Moving a term now moves it in every locale, and terms already split this way are repaired on upgrade.

Patch Changes

• #2363 6215e93 Thanks @danielmlr! - Fixes the publish button not appearing after an autosave on sites without i18n configured. The edit was saved, but the editor kept showing the entry as fully published until a reload.

• #2366 28b17fd Thanks @edrpls! - Fixes silent save failures when creating content in the admin: a rejected create — for example a slug that already exists in the collection — now shows a "Failed to save" toast with the server's message instead of doing nothing.

• #2258 d9b76be Thanks @thefrana! - Adds Czech (Čeština) to the admin UI. Select it from the language picker on the
  login page or in Settings.

• #2348 640da63 Thanks @khoinguyenpham04! - Fixes numbered lists restarting at 1 after intervening content blocks in the editor and rendered pages.

• #2301 e61cb63 Thanks @ankit-fastcurveservices! - Enables Hindi (हिन्दी) locale in the admin UI

• #2401 6e47033 Thanks @danielmlr! - Fixes the status badge and status filter labeling published content "Publish" instead of "Published". Existing translations of "Published" now apply there too.

• #2406 1cf2811 Thanks @ascorbic! - Fixes the redirects screen so all redirects can be loaded beyond the first 100 results.

• #2236 2400a3e Thanks @bimsonz! - Shows the derived title and description as placeholders in the SEO panel. getSeoMeta already falls back to an entry's own data.title and data.excerpt when the panel is empty, but the panel gave no sign of it, so empty inputs read as "unset". Editors either retyped the page title into the SEO title or concluded the page had no SEO at all. The SEO Title and Meta Description fields now show the value that will actually be used, so an empty field reads as inheriting it. No change to the generated meta.

• Updated dependencies []:

  • @emdash-cms/blocks@0.33.0