Skip to content

SynaptikCMS v1.2

Choose a tag to compare

@synaptikcms synaptikcms released this 27 Jun 04:16
081008d

[1.2] — 2026-06-26

Added

  • Added a built-in translation editor: edit any locale's strings directly from the admin panel, and create new locales by duplicating en.json with one click — accessible from Tools → Translations and from the Settings → General language selector.
  • Admin language can now be different from front-end language, both can be set from the Settings section.
  • Replaced the CSS-only theme editor with a full Template Editor: browse and edit every file of the active theme (PHP, CSS, JS, JSON) from a single grouped file dropdown, with per-file backups and adaptive stats (lines, rules/variables for CSS, functions/comments for PHP & JS).
  • New themes: Downloadable Here
  • Theme SynaptikDocs
  • Theme Atrium
  • Theme Myelin
  • Theme Axion

Changed

  • Admin interface improvements: now fully responsive
  • Modified sidebar to display flyouts for all sections when collapsed
  • Editor sidebar is now collapsible to focus on content writing / edition
  • Modified admin tabs style to be more visible
  • Modified Alt-text-assistant and Seo-overview to display tabs in the same style as settings
  • Moved SEO Overview to the Tools section of sidebar
  • Improved header scripts, added async to the JS files to improve load speed even more.
  • Architecture Changes:
  • Tags are now stored as slugs in item files ("tags": ["my-tag"] instead of "tags": ["My Tag"]). Display names are resolved at render time from tags.json. Renaming a tag now only requires updating tags.json — no item files are touched when only the display name changes; item files are updated only when the slug itself changes.
  • Categories follow the same pattern: item files now store the category slug ("category": "anatomie" instead of "category": "Anatomie"). Display names and parent relationships are resolved from categories.json. Renaming a category only rewrites item files when the slug changes.
  • Creating a tag or category inline from the content editor (without going through the dedicated management pages) now automatically upserts the new entry into tags.json / categories.json, keeping the stores always in sync with actual content.
  • Moved static assets (/css, /js) into /assets/css and /assets/js, and front-end locale files into /lang/front/ for a cleaner root directory structure.

Fixed

  • Fixed CSS display issue in file manager list view, which was hiding the folder name. Replaced folder icon with SVG that fits the admin design better.
  • Fixed a tag duplication bug in the content editor where renaming a tag (e.g. "Themes" → "themes") would leave the old display string in existing item files, causing both versions to appear in the tag input suggestions.
  • Fixed missing categories in data/categories.json: some were used by content items but absent from the store, causing getCategoryPath() to fail silently and breaking hierarchical URLs for those categories and their children.