tr
TryGhost
GitHub
Ghost
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
Ghost
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
30285
1789c159 Changed settings screens to read the framework data hooks no ref GlobalDataProvider re-fetched settings/config/site/currentUser into a settings-only context, but those are the same react-query cache entries the admin shell already warms at boot. A thin SettingsDataGate keeps the existing loading-orb and error-rethrow UX at the settings root, and the screens below it now read the framework query hooks directly through small assert helpers (useLoadedSettings/Config/Site/CurrentUser) that throw if rendered outside the gate, instead of carrying the data through a context. SettingsAppProvider slims to UI state (search, sorting, offers archive toggle, scroll spy); the never-supplied upgradeStatus plumbing and its dead About-modal banner are removed. The settings-local Pintura hook merges onto the root usePinturaEditor, which resolves URLs via the framework's usePinturaConfig. Ported in the merge: the window.pintura type declaration moved to the root hook, and the two SEO image save handlers now surface upload failures via useHandleError, which the settings hook previously did for every consumer. The settings copy's Sentry captures were dropped - Sentry is not initialised in this app, so they never reported.
by Steve Larson
S
Previous
Next