Every time you need to change a couple of settings, the same thing happens: pick a namespace in one filter, pick an area in a second filter, page through the pager, double-click the «Value» cell, miss, click again, type the value, press Enter and wait for the row to save. Then the next one. And the setting's description hides behind a plus sign you have to click as well.

EasySettings shows the same settings as a form: name, description and key on the left, a field of the right type on the right. Change as many values as you like and save them all in one press.

The page URL, the menu item and the permissions stay the same, and the page does not look out of place: the same tabs, buttons, windows and colours as MODX 3 or MODX 2.

No more double-clicking

Every setting is a row, the field is editable straight away and matches the type: a Yes/No toggle, a number, a password with a «Show» button, JSON with validation, a textarea that grows. Core combo boxes become a list with the same options; third-party settings with their own xtype are rendered by their own ExtJS component.

Core text settings that really have a fixed set of values — log_level, link_tag_scheme, friendly_alias_translit and others — are shown as lists too. No more opening the docs to recall whether it was abs or full.

A whole area, no pagination

On the left is a MODX-style tree of namespaces and areas. An area opens as its own page with its own URL (&ns=core&area=site): Back and Forward work, the link opens in a new tab, and unsaved edits survive navigation. Expanded folders and tree scrolling are remembered between loads.

An area's settings load when you open it, so on a site with thirty extras the page opens as fast as on a clean install.

Batch saving

Changed rows are marked and a «Cancel» / «Save» bar appears at the bottom. Or Ctrl+S, which works in any keyboard layout. Leaving the page with unsaved edits asks for confirmation.

Each setting is saved by a core processor, so all of the MODX logic still runs: config reload, URI recalculation when friendly_urls changes, permission checks. If one setting fails to save, the rest still save.

Search that finds more than the core one

By name, key, description and value, across every namespace at once, with matches highlighted. It also finds translations from lexicon files, which core search does not see. Press / or Ctrl+K to jump into the search field.

Sorting by key, name or modification date — handy when you need to recall what exactly you changed last week.

Right-click is still there

On a row it opens a menu just like a MODX grid: Edit, Copy key, Revert to saved value, Delete. Right-clicking an input leaves the browser menu alone — you still need to paste from the clipboard.



The edit window changes everything: field type, namespace, area, name, description and value. Name and description are written into the lexicon in the manager's language, and only when they were actually changed.

System Events tab

Events by group with the plugins attached to them, search, and sorting by plugin count. Custom events can be created and deleted; core events, as before, cannot.

If you want the old way back

The «Classic view» button opens the stock grid, and there — next to Help! — a «Convenient view» button appears to bring you back. The component can be switched off entirely with the easysettings.enabled setting.

About ExtJS

The interface is written in Svelte. ExtJS appears only where nothing else will do: third-party fields with their own xtype are rendered by their own components, and confirmations and notifications use the manager's own windows. The interface bundle is about 160 KB, under 50 KB gzipped over the wire.

Interface strings come from the MODX lexicon in the manager's language; the component's own strings are translated into English, Russian and Tajik.