Yes. Enable Delete plugin data on uninstall<\/strong> in Settings before deleting the plugin. The default is to preserve data so an accidental uninstall does not erase operational history.<\/p><\/dd>\nWhich languages are available?<\/h3><\/dt>\nThe interface is fully translatable and follows your WordPress language, both the site setting and the per-user setting under Users \u2192 Profile. Danish is included; other languages can be contributed through translate.wordpress.org.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.17<\/h4>\n\n\n- Removes the site read-only lock. The two maintenance actions that change something, clearing expired transients and running one overdue cron event, now run for anyone with the Operations capability, behind the same preflight and explicit confirmation as before.<\/li>\n
- Removes the frozen free-baseline option, its signature check and the diagnostics row that reported it.<\/li>\n
- Removes the build-variant marker and the rows and REST fields that reported it.<\/li>\n
- The section order no longer reserves places for sections this plugin does not provide.<\/li>\n
- Removes styling for screens that are not part of this plugin.<\/li>\n
- Setup and the dashboard describe what this plugin does, without referring to an add-on.<\/li>\n<\/ul>\n\n
1.0.16<\/h4>\n\n\n- Links, redirects and filter forms inside Operations carry a view nonce, and filters and notices are only read after it is verified. Form handlers verify their action nonce inside the same helper that reads the submitted values.<\/li>\n
- The debug-log check finds the web root with get_home_path() and the log file from PHP's own error_log setting; drop-ins are detected through get_dropins().<\/li>\n
- One prefix family: the setup class is Inhab_Operations_Onboarding, the script data object is inhabOperations, and the unused NimblePlugins constant and class aliases are removed.<\/li>\n<\/ul>\n\n
1.0.15<\/h4>\n\n\n- The plugin and author URIs are no longer the same address. The plugin now points at its own page; the author link stays on nimbleplugins.com.<\/li>\n<\/ul>\n\n
1.0.14<\/h4>\n\n\n- English is now the plugin's own language and its default. It no longer changes because an administrator's WordPress profile is set to something else, which is how a screen could show English navigation above Danish incident text. Danish and \"follow WordPress\" remain available under Settings.<\/li>\n
- Fixed three places that kept light colours in the dark theme: the locked maintenance card, which painted itself almost white and hid its own heading, the status pill, and the two notices.<\/li>\n<\/ul>\n\n
1.0.13<\/h4>\n\n\n- wp-admin\/includes\/upgrade.php is now loaded immediately before dbDelta() rather than at the top of the method. The file was always used, but a review tool that looks for the call right after the include cannot see that across a hundred and fifty lines of table definitions.<\/li>\n<\/ul>\n\n
1.0.12<\/h4>\n\n\n- Removes the Operations Pro licence client, the licence screen and all licence storage from the free plugin. Licensing now lives entirely in the commercial Pro add-on; nothing in the free plugin is gated, checked or limited.<\/li>\n
- The Pro sections are shown when the Pro add-on registers them, rather than being filtered by an entitlement check inside the free plugin.<\/li>\n
- Easy Setup asks the add-on whether scheduled monitoring is available instead of asking about a licence.<\/li>\n
- Uninstall still clears any licence options left behind by an earlier version.<\/li>\n
- Requires Operations Pro 0.6.0 or newer if the Pro add-on is installed.<\/li>\n<\/ul>\n\n
1.0.11<\/h4>\n\n\n- Renames four filters from nimble_operations_* to nimbleplugins_operations_*, matching the prefix the rest of the plugin already uses. These four were only ever used inside this plugin, so nothing external depends on them.<\/li>\n
- Clears the remaining Plugin Check warnings.<\/li>\n<\/ul>\n\n
1.0.10<\/h4>\n\n\n- The whole interface is now properly internationalised. 61 hardcoded English\/Danish string pairs and 175 untranslated strings were converted to standard WordPress translation functions, taking the translatable surface from 92 strings to 297.<\/li>\n
- Removes the plugin's own language setting. The interface follows the WordPress site language and the per-user language under Users > Profile, like the rest of the admin.<\/li>\n
- Stops shipping compiled translations. Danish now comes from translate.wordpress.org, where it cannot drift out of step with the code.<\/li>\n
- The licence screen no longer presents an unreleased add-on as a missing one, and the key field appears only once Operations Pro is installed.<\/li>\n
- Corrects the Contributors username.<\/li>\n<\/ul>\n\n
1.0.9<\/h4>\n\n\n- Replaces the placeholder mark with the real Nimble logo across the plugin, in the\nproduct's own colour so the WordPress admin menu stays readable when several\nNimble plugins are installed side by side.<\/li>\n
- No behaviour change.<\/li>\n<\/ul>\n\n
1.0.8<\/h4>\n\n\n- Replaces the generic WordPress scan-complete notice with a compact Operations status component.<\/li>\n
- Keeps the confirmation visually consistent in dark and light mode, responsive on small screens and keyboard accessible.<\/li>\n<\/ul>\n\n
1.0.7<\/h4>\n\n\n- Adds a three-step Easy Setup for first-time users with an explicit Skip option.<\/li>\n
- Lets administrators define the site context, choose monitoring defaults and start the first read-only scan.<\/li>\n
- Keeps WordPress visibility, wp-config.php and third-party plugin settings unchanged unless the administrator acts in the owning system.<\/li>\n
- Shows detected optional Nimble and cache integrations without treating missing products as issues.<\/li>\n
- Makes Easy Setup available again from Operations Settings without resetting operational history.<\/li>\n<\/ul>\n\n
1.0.6<\/h4>\n\n\n- Adds an explicit expected search-visibility policy for production, staging and private sites.<\/li>\n
- Treats an intentionally discouraged staging\/private site as informational and non-scoring while keeping the state visible.<\/li>\n
- Reopens the issue if the live WordPress visibility later drifts from the selected expectation.<\/li>\n<\/ul>\n\n
1.0.5<\/h4>\n\n\n- Expands page-cache diagnostics from the WP_CACHE flag to configuration, drop-in, provider and response-header evidence.<\/li>\n
- Exposes a bounded cache-diagnostics contract for Operations Pro without reading cache contents or provider configuration.<\/li>\n
- Keeps cache diagnostics informational and the public Free package site-state read-only.<\/li>\n<\/ul>\n\n
1.0.4<\/h4>\n\n\n- Replaces absolute post-revision thresholds with a site-size-aware evaluation.<\/li>\n
- Treats a finite WP_POST_REVISIONS cap of up to 50 revisions per content item as managed and non-scoring.<\/li>\n
- Evaluates revisions per revision-enabled content item together with revision storage footprint when no conservative finite cap is active.<\/li>\n
- Keeps historical revision cleanup optional unless the database footprint is genuinely disproportionate.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Reclassifies large post-revision counts as medium-priority database hygiene instead of a high-severity operational incident.<\/li>\n
- Keeps the existing revision thresholds and remediation guidance while aligning the health-score deduction with the actual risk.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First public WordPress.org release.<\/li>\n
- Adds the complete 47-check monitoring baseline, Site Speed gauge, incidents, reports, diagnostics and operational timeline.<\/li>\n
- Adds a full-width responsive administration interface with per-user dark and light modes.<\/li>\n
- Keeps the public distribution site-state read-only and free of frontend assets or telemetry.<\/li>\n
- Moves internal test and site-specific Pro entitlements out of the public Free package.<\/li>\n
- Aligns the public text domain and release metadata with the requested
nimble-operations<\/code> WordPress.org slug.<\/li>\n<\/ul>\n\nEarlier development milestones are listed in changelog.txt<\/code>.<\/p>","raw_excerpt":"Monitor WordPress health, performance and incidents from one lightweight, privacy-conscious operations dashboard.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/371643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=371643"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/nimbleplugin"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=371643"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=371643"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=371643"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=371643"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=371643"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=371643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}