Before 1.7.7 the Abilities tab had a Save changes button at the bottom and four more buttons on its cards: Save content types, Save meta keys, Save user meta keys and Save term meta keys. If you edited an exposed meta key or a content type and pressed only the main Save, the edit was lost. In 1.7.7 there is one Save changes button, and it saves every section on the tab.
Nothing about what is exposed has changed. This release changes how you save the choices, and what the Activity Log says when those choices move.
How the one button behaves
The button sends only the sections you changed, in a single request. While edits are pending, an “Unsaved changes” note appears beside it, and the browser warns you if you try to leave the page.
If a section fails to save, the page names it and leaves your edits where they are. The message reads like this: “Not saved: Exposed meta keys (Content). Everything else was saved.” Sections that did save stay saved, so you retry only the one that failed.
A failed section can hold back changes that would expose more
When one section fails, any section that would widen access is held back instead of written. Adding an ability, a content type or an exposed meta key counts as widening, and so does removing a deny entry. The held section reports “was not saved because another section on this page failed.”
Changes that restrict still save. Turning an ability off, removing a content type or adding a deny entry all go through, and a failed section does not stop them. A section that both widens and narrows is held as a whole. The save writes every restricting section first and the widening ones afterward.
The Activity Log notes when an exposed list changes
Changing the exposed content types, or the exposed post, user or term meta keys, now adds a row to the Activity Log. The row gives the list name and how many keys were added and removed, for example “Exposed post meta keys changed: 2 added, 1 removed”. It never lists the keys themselves.
No row is written when nothing actually changed. That keeps the log readable, and it matches the rule in what the Activity Log actually stores: identifiers and counts, not content.
A small log fix
The Activity Log table used to scroll sideways when a value was long, such as the detail JSON on a row. The columns now share the page width and long values wrap inside their cells.
What did not change
The catalog is still 179 abilities, 85 in core and 94 across the integrations.
This release sits between two others. 1.7.6 confined OAuth tokens to the MCP route, and 1.7.8 fixed bridged tools that never showed in the tool list. The full history is on the changelog.