{"id":392686,"date":"2026-10-27T10:30:32","date_gmt":"2026-10-27T10:30:32","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/tracewise-status-monitoring\/"},"modified":"2026-10-27T11:21:43","modified_gmt":"2026-10-27T11:21:43","slug":"tracewise-status-monitoring","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/tracewise-status-monitoring\/","author":23592602,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.1.0","stable_tag":"1.1.0","tested":"7.1.4","requires":"6.7","requires_php":"7.4","requires_plugins":null,"header_name":"TraceWise Status & Monitoring","header_author":"RazorSoft, Inc.","header_description":"Show public TraceWise status pages in WordPress, and manage monitors with an API key that stays on the server.","assets_banners_color":"c7cfd7","last_updated":"2026-10-27 11:21:43","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/www.tracewise.dev","header_author_uri":"https:\/\/razorsoft.us","rating":0,"author_block_rating":0,"active_installs":0,"downloads":67,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.1.0":{"tag":"1.1.0","author":"razorsoftinc","date":"2026-10-27 11:21:43","revision":3768340}},"upgrade_notice":{"1.1.0":"<p>The display name is TraceWise Status &amp; Monitoring. Translations use the text domain tracewise-status-monitoring. Existing settings, blocks, shortcodes, and the stored API key remain in place.<\/p>","1.0.0":"<p>Show a public TraceWise status page with blocks or shortcodes. No API key is required.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3768340,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3768340,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3768340,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3768340,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"tracewise-status\/indicator":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"tracewise-status\/indicator","title":"TraceWise Status Indicator","category":"tracewise-status","icon":"marker","description":"Show a status dot and label for a public TraceWise status page. Leave the slug blank to use the default page.","keywords":["status","indicator","tracewise"],"textdomain":"tracewise-status-monitoring","attributes":{"slug":{"type":"string","default":""},"theme":{"type":"string","default":""},"showUptime":{"type":"boolean","default":false},"showLabel":{"type":"boolean","default":true},"refresh":{"type":"string","default":""},"align":{"type":"string","default":""}},"supports":{"html":false,"multiple":true,"reusable":true,"align":["left","center","right","wide","full"]},"editorScript":"file:.\/index.js","editorStyle":"file:.\/index.css"},"tracewise-status\/history":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"tracewise-status\/history","title":"TraceWise Uptime History","category":"tracewise-status","icon":"chart-bar","description":"Show daily uptime for a public TraceWise status page. Leave the slug blank to use the default page.","keywords":["uptime","history","tracewise"],"textdomain":"tracewise-status-monitoring","attributes":{"slug":{"type":"string","default":""},"theme":{"type":"string","default":""},"showUptime":{"type":"boolean","default":false},"period":{"type":"string","default":""},"refresh":{"type":"string","default":""},"align":{"type":"string","default":""}},"supports":{"html":false,"multiple":true,"reusable":true,"align":["left","center","right","wide","full"]},"editorScript":"file:.\/index.js","editorStyle":"file:.\/index.css"},"tracewise-status\/badge":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"tracewise-status\/badge","title":"TraceWise Status Badge","category":"tracewise-status","icon":"yes-alt","description":"Show the current overall status for a public TraceWise status page. Leave the slug blank to use the default page.","keywords":["status","uptime","tracewise","badge"],"textdomain":"tracewise-status-monitoring","attributes":{"slug":{"type":"string","default":""},"theme":{"type":"string","default":""},"showUptime":{"type":"boolean","default":false},"refresh":{"type":"string","default":""},"align":{"type":"string","default":""}},"supports":{"html":false,"multiple":true,"reusable":true,"align":["left","center","right","wide","full"]},"editorScript":"file:.\/index.js","editorStyle":"file:.\/index.css"},"tracewise-status\/incidents":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"tracewise-status\/incidents","title":"TraceWise Incident List","category":"tracewise-status","icon":"list-view","description":"Show recent incidents for a public TraceWise status page. Leave the slug blank to use the default page.","keywords":["incidents","status","tracewise"],"textdomain":"tracewise-status-monitoring","attributes":{"slug":{"type":"string","default":""},"theme":{"type":"string","default":""},"limit":{"type":"string","default":"5"},"showResolved":{"type":"boolean","default":true},"refresh":{"type":"string","default":""},"align":{"type":"string","default":""}},"supports":{"html":false,"multiple":true,"reusable":true,"align":["left","center","right","wide","full"]},"editorScript":"file:.\/index.js","editorStyle":"file:.\/index.css"},"tracewise-status\/card":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"tracewise-status\/card","title":"TraceWise Status Card","category":"tracewise-status","icon":"id","description":"Show a status card for a public TraceWise status page. Leave the slug blank to use the default page.","keywords":["status","card","tracewise"],"textdomain":"tracewise-status-monitoring","attributes":{"slug":{"type":"string","default":""},"theme":{"type":"string","default":""},"showUptime":{"type":"boolean","default":false},"refresh":{"type":"string","default":""},"align":{"type":"string","default":""}},"supports":{"html":false,"multiple":true,"reusable":true,"align":["left","center","right","wide","full"]},"editorScript":"file:.\/index.js","editorStyle":"file:.\/index.css"}},"tagged_versions":["1.1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3768239,"resolution":"1","location":"assets","locale":"","width":1200,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3768239,"resolution":"2","location":"assets","locale":"","width":1200,"height":900},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3768239,"resolution":"3","location":"assets","locale":"","width":1200,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3768239,"resolution":"4","location":"assets","locale":"","width":1200,"height":900},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3768239,"resolution":"5","location":"assets","locale":"","width":1200,"height":900}},"screenshots":{"1":"The Public Status Widgets screen, where you set the default status page, theme, refresh interval, uptime period, and an optional link to the full status page.","2":"The block inserter with the five TraceWise blocks: Status Badge, Status Indicator, Status Card, Uptime History, and Incident List.","3":"A Status Badge block in the editor, with sidebar settings for the status-page slug, theme, uptime, and refresh interval.","4":"A published page showing the badge, indicator, card, uptime history, and incident list together.","5":"The same page with the Dark theme selected, so the status card and incident list use the dark colors."}},"plugin_section":[262246],"plugin_tags":[4121,261616,409,29148],"plugin_category":[],"plugin_contributors":[288904],"plugin_business_model":[],"class_list":["post-392686","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-blocks","plugin_tags-incidents","plugin_tags-status","plugin_tags-uptime","plugin_contributors-razorsoftinc","plugin_committers-razorsoftinc"],"banners":{"banner":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/banner-772x250.png?rev=3768340","banner_2x":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/banner-1544x500.png?rev=3768340","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/icon-128x128.png?rev=3768340","icon_2x":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/icon-256x256.png?rev=3768340","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/screenshot-1.png?rev=3768239","caption":"The Public Status Widgets screen, where you set the default status page, theme, refresh interval, uptime period, and an optional link to the full status page."},{"src":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/screenshot-2.png?rev=3768239","caption":"The block inserter with the five TraceWise blocks: Status Badge, Status Indicator, Status Card, Uptime History, and Incident List."},{"src":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/screenshot-3.png?rev=3768239","caption":"A Status Badge block in the editor, with sidebar settings for the status-page slug, theme, uptime, and refresh interval."},{"src":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/screenshot-4.png?rev=3768239","caption":"A published page showing the badge, indicator, card, uptime history, and incident list together."},{"src":"https:\/\/ps.w.org\/tracewise-status-monitoring\/assets\/screenshot-5.png?rev=3768239","caption":"The same page with the Dark theme selected, so the status card and incident list use the dark colors."}],"raw_content":"<!--section=description-->\n<p>Show visitors whether your service is up, degraded, or down, and what has happened recently, on any WordPress page.<\/p>\n\n<p><a href=\"https:\/\/www.tracewise.dev\/\">TraceWise<\/a> is a hosted uptime and status service from RazorSoft, Inc. This plugin places a published TraceWise status page on your site as five widgets. Visitors see the current status, recent uptime, and incidents. You add them from the WordPress editor.<\/p>\n\n<p>Public widgets work without a TraceWise account and without an API key. They read a status page that is already public, including the <code>demo<\/code> page. Publishing your own status page is done in TraceWise, on the plan you choose there. This plugin does not include paid TraceWise features for free.<\/p>\n\n<ul>\n<li><strong>Status Badge<\/strong> shows the overall status. Uptime is optional.<\/li>\n<li><strong>Status Indicator<\/strong> shows a status dot and label. The label can be hidden.<\/li>\n<li><strong>Status Card<\/strong> shows a short summary and a link to the full status page.<\/li>\n<li><strong>Uptime History<\/strong> shows daily reliability for 7, 30, or 90 days.<\/li>\n<li><strong>Incident List<\/strong> shows 5, 10, or 20 recent incidents. Resolved incidents can be hidden.<\/li>\n<\/ul>\n\n<p>Use them as Gutenberg blocks or as shortcodes: <code>[tracewise_status]<\/code>, <code>[tracewise_indicator]<\/code>, <code>[tracewise_card]<\/code>, <code>[tracewise_history]<\/code>, and <code>[tracewise_incidents]<\/code>. Gutenberg, the Site Editor, the Classic Editor, and builders that run shortcodes all work. A Custom HTML block does not run shortcodes.<\/p>\n\n<p>Save the status page you use most often under TraceWise \u2192 Public Status Widgets. Widgets that leave the slug blank use that page. A block or shortcode can name a different public status page. How many public status pages a workspace can publish depends on the TraceWise plan.<\/p>\n\n<p>An API key is optional. Paste one under TraceWise \u2192 Connection when you want to view or manage monitors from WordPress. The TraceWise menu also includes Overview and Monitors, and administrators see a Dashboard widget for overall health. Those screens use the key. The key is encrypted in WordPress and is used only for server-side requests. It is not added to pages, blocks, JavaScript, or REST responses. Public widgets keep working if you never connect a key.<\/p>\n\n<p>TraceWise plan limits still apply. Those limits include how many monitors a workspace can create, the shortest check interval, how many public status pages it can publish, and the API rate limit. This plugin shows those limits when TraceWise returns them. It does not raise them or change TraceWise prices.<\/p>\n\n<h4>Get started<\/h4>\n\n<ol>\n<li>Install and activate TraceWise Status &amp; Monitoring.<\/li>\n<li>Open TraceWise \u2192 Public Status Widgets. Save <code>demo<\/code> to preview, or paste the slug of a published status page.<\/li>\n<li>Edit a page, insert a TraceWise block, or add a shortcode such as <code>[tracewise_status]<\/code>.<\/li>\n<li>Optional: create an API key in TraceWise and paste it under TraceWise \u2192 Connection to view or manage monitors.<\/li>\n<\/ol>\n\n<h4>Display options<\/h4>\n\n<p>Each block and shortcode can set <code>slug<\/code>, <code>theme<\/code>, <code>show_uptime<\/code>, <code>show_label<\/code>, <code>period<\/code>, <code>limit<\/code>, <code>show_resolved<\/code>, and <code>refresh<\/code>. Leave <code>slug<\/code> off to use the default status page.<\/p>\n\n<pre><code>auto follows the visitor's color scheme. `light` and `dark` set the status colors. Leave `refresh` empty to use the saved setting, use `0` to load once, and use at least `60` to poll. To match a theme, add CSS variables such as `--tw-status-operational` and `--tw-status-surface` on a parent. See the [component documentation](https:\/\/www.tracewise.dev\/docs\/components).\n<\/code><\/pre>\n\n<h4>External service and privacy<\/h4>\n\n<p>TraceWise Status &amp; Monitoring contacts <code>https:\/\/www.tracewise.dev<\/code>, an external service operated by RazorSoft, Inc.<\/p>\n\n<ul>\n<li>Public widgets send the status-page slug to the hosted embed, <code>https:\/\/www.tracewise.dev\/embed\/status.js<\/code>, in the visitor's browser. The embed then requests the published status page. No API key is included. Visitors of a page that contains a widget also receive that script from TraceWise. A page with no TraceWise widget does not load it. Several widgets on one page still load it once. The block editor loads it so the preview can run. The plugin does not accept a custom API URL.<\/li>\n<li>Optional monitoring management sends the API key from the WordPress server to <code>https:\/\/www.tracewise.dev\/api\/v1<\/code>. The browser does not receive the key. Responses used on the admin screens are cached briefly in WordPress. A key that can only read monitors can still open the monitor list. Create, edit, and delete stay hidden until TraceWise confirms <code>monitors:write<\/code>. Manual checks stay hidden until TraceWise confirms <code>checks:run<\/code>.<\/li>\n<li>The plugin stores the public widget settings and the encrypted API key in WordPress options. It does not send WordPress user accounts, comments, or post content to TraceWise.<\/li>\n<li>Uninstall deletes the plugin settings, the encrypted key, and cached monitor views. It does not delete WordPress content and it does not delete the TraceWise account. Deactivation leaves the settings and the key in place.<\/li>\n<li>Terms of Service: https:\/\/www.tracewise.dev\/terms<\/li>\n<li>Privacy Policy: https:\/\/www.tracewise.dev\/privacy<\/li>\n<\/ul>\n\n<h4>Translations<\/h4>\n\n<p>The text domain is <code>tracewise-status-monitoring<\/code>. PHP, block metadata, and the block editor scripts use that domain. The plugin directory, option names, block names, and shortcodes stay <code>tracewise-status<\/code> so existing sites keep working. The plugin does not ship translation files.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>tracewise-status<\/code> folder to <code>\/wp-content\/plugins\/<\/code>, or install <code>tracewise-status-monitoring-1.1.0.zip<\/code> through Plugins \u2192 Add New \u2192 Upload Plugin. The zip contains <code>tracewise-status\/tracewise-status.php<\/code>.<\/li>\n<li>Activate TraceWise Status &amp; Monitoring on the Plugins screen. Updating from 1.0.0 keeps the same plugin, the saved settings, and the stored API key.<\/li>\n<li>Open TraceWise \u2192 Public Status Widgets and save the default status-page slug. Widgets that leave the slug blank use that page. A block or shortcode can name another public status page.<\/li>\n<li>Edit a page, insert a TraceWise Status block, or add a shortcode such as <code>[tracewise_status]<\/code>.<\/li>\n<li>Optional: open TraceWise \u2192 Connection and paste an API key to view or manage monitors.<\/li>\n<\/ol>\n\n<p>No Docker, Node.js, or Composer is required on the WordPress site. The block editor source is included in <code>src\/<\/code>. Node.js and <code>npm run build<\/code> are only needed to rebuild the files in <code>build\/<\/code>.<\/p>\n\n<p>WordPress.com sites need a plan that allows uploaded plugins, such as Business or Commerce. The plugin uses the WordPress options and HTTP APIs. It does not create custom database tables. The plugin needs WordPress 6.7 or newer and PHP 7.4 or newer.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"is%20an%20api%20key%20required%3F\"><h3>Is an API key required?<\/h3><\/dt>\n<dd><p>No. Public status widgets read a published status page and do not use an API key.<\/p>\n\n<p>An API key is only for optional monitoring management. Create one in TraceWise and paste it under TraceWise \u2192 Connection. WordPress encrypts it and does not show it again. Disconnect removes it. Public widgets stay the same.<\/p><\/dd>\n<dt id=\"what%20features%20are%20free%3F\"><h3>What features are free?<\/h3><\/dt>\n<dd><p>The plugin is free. Showing a public status badge, indicator, card, uptime history, or incident list does not require an API key or a paid plugin upgrade.<\/p>\n\n<p>TraceWise is a separate hosted service with its own plans. Monitor limits, the shortest check interval, how many public status pages you can publish, and API rate limits come from that plan. Connecting a key does not add paid TraceWise capacity, and this plugin does not include paid TraceWise features for free.<\/p><\/dd>\n<dt id=\"how%20do%20i%20display%20a%20status%20widget%3F\"><h3>How do I display a status widget?<\/h3><\/dt>\n<dd><p>Open TraceWise \u2192 Public Status Widgets and save a default status-page slug. Edit a page and insert a TraceWise block, or paste a shortcode:<\/p>\n\n<ul>\n<li><code>[tracewise_status]<\/code> for the badge<\/li>\n<li><code>[tracewise_indicator]<\/code> for the indicator<\/li>\n<li><code>[tracewise_card]<\/code> for the card<\/li>\n<li><code>[tracewise_history]<\/code> for uptime history<\/li>\n<li><code>[tracewise_incidents]<\/code> for the incident list<\/li>\n<\/ul>\n\n<p>Leave the slug blank to use the default status page. If you do not have a public status page yet, create one at https:\/\/www.tracewise.dev\/sign-up and enable it under Dashboard \u2192 Settings \u2192 Status page. The public <code>demo<\/code> slug previews the widgets before that.<\/p><\/dd>\n<dt id=\"can%20i%20use%20different%20status%20pages%3F\"><h3>Can I use different status pages?<\/h3><\/dt>\n<dd><p>Yes. Save the page you use most often as the default. Set the slug on a block or shortcode when that widget should show a different public status page. How many public status pages a workspace can publish depends on the TraceWise plan. This plugin does not add a WordPress setting for every status page.<\/p><\/dd>\n<dt id=\"does%20it%20work%20with%20gutenberg%20and%20shortcodes%3F\"><h3>Does it work with Gutenberg and shortcodes?<\/h3><\/dt>\n<dd><p>Yes. Gutenberg and the Site Editor use the blocks. The Classic Editor, a Text widget, and builders that run shortcodes, including the Elementor Shortcode widget, use the shortcodes. A Custom HTML block does not run shortcodes. Paste a shortcode into a Shortcode or Text element instead.<\/p>\n\n<p>The plugin needs WordPress 6.7 or newer and PHP 7.4 or newer. WordPress.com sites need a plan that allows uploaded plugins, such as Business or Commerce.<\/p><\/dd>\n<dt id=\"how%20do%20i%20connect%20monitoring%20management%3F\"><h3>How do I connect monitoring management?<\/h3><\/dt>\n<dd><p>Open TraceWise \u2192 Connection and paste an API key from your TraceWise workspace. Only an administrator with <code>manage_options<\/code> can open or save that screen.<\/p>\n\n<p>A key that views monitors needs <code>monitors:read<\/code> and <code>incidents:read<\/code>. Creating, editing, and deleting monitors also needs <code>monitors:write<\/code>. Manual checks need <code>checks:run<\/code>. If a scope is missing, WordPress hides those actions and explains why. A key that can only read monitors can still open the monitor list. Test the connection again after you add a scope in TraceWise. The plugin does not treat a successful monitor list as permission to change monitors.<\/p>\n\n<p>The key is sent only from the WordPress server to <code>https:\/\/www.tracewise.dev\/api\/v1<\/code>. It is not placed in page HTML, blocks, or browser JavaScript. WordPress stores it encrypted and shows only the last four characters.<\/p><\/dd>\n<dt id=\"what%20data%20is%20sent%20to%20tracewise%3F\"><h3>What data is sent to TraceWise?<\/h3><\/dt>\n<dd><p>Public widgets send the status-page slug from the visitor's browser to <code>https:\/\/www.tracewise.dev\/embed\/status.js<\/code>. That script then requests the published status page. No API key is included. A page with no TraceWise widget does not load the script.<\/p>\n\n<p>If you connect an API key, WordPress sends that key from the server to <code>https:\/\/www.tracewise.dev\/api\/v1<\/code>. The browser does not receive the key. The plugin does not send WordPress user accounts, comments, or post content.<\/p>\n\n<p>Terms of Service: https:\/\/www.tracewise.dev\/terms\nPrivacy Policy: https:\/\/www.tracewise.dev\/privacy<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20uninstall%3F\"><h3>What happens when I uninstall?<\/h3><\/dt>\n<dd><p>Uninstall deletes the widget settings, the encrypted API key, and cached monitor views. It does not delete your pages or posts, and it does not delete the TraceWise account. Deactivating the plugin leaves the settings and the key in place.<\/p><\/dd>\n<dt id=\"do%20tracewise%20plan%20limits%20still%20apply%3F\"><h3>Do TraceWise plan limits still apply?<\/h3><\/dt>\n<dd><p>Yes. TraceWise enforces monitor caps, minimum check intervals, duplicate URLs, how many public status pages a workspace can publish, and API rate limits. This plugin shows those errors. It does not raise the limits or change subscription prices.<\/p><\/dd>\n<dt id=\"how%20do%20i%20match%20my%20theme%3F\"><h3>How do I match my theme?<\/h3><\/dt>\n<dd><p>Choose Auto, Light, or Dark. Auto follows the visitor's color scheme. A block or shortcode can override the default. For brand colors, add the <code>--tw-status-*<\/code> variables in Additional CSS or the theme stylesheet. The widgets use normal document flow and shrink to the content width. See the <a href=\"https:\/\/www.tracewise.dev\/docs\/components\">component documentation<\/a>.<\/p><\/dd>\n<dt id=\"does%20an%20update%20keep%20my%20settings%3F\"><h3>Does an update keep my settings?<\/h3><\/dt>\n<dd><p>Yes. Version 1.1.0 uses the same plugin file, options, blocks, and shortcodes as 1.0.0. An existing API key stays in place. You do not need to paste the key again unless WordPress can no longer decrypt it.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Show the plugin as TraceWise Status &amp; Monitoring. The text domain is tracewise-status-monitoring. The install path, options, blocks, and shortcodes stay tracewise-status.<\/li>\n<li>Encrypt API keys with AES-256-GCM. Keys stored by 1.0.0 keep working and are rewritten on the next read.<\/li>\n<li>Hide create, edit, and delete when TraceWise says the key lacks monitors:write. Hide manual checks when it lacks checks:run.<\/li>\n<li>Document the external TraceWise service, public status requests, and the server-side API key.<\/li>\n<li>Describe the saved slug as the default status page. Blocks and shortcodes can name another public status page.<\/li>\n<li>Name the install archive tracewise-status-monitoring-1.1.0.zip. The plugin directory inside it remains tracewise-status.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Add TraceWise \u2192 Public Status Widgets for the public slug, theme, refresh interval, uptime period, and optional status page link.<\/li>\n<li>Add five blocks and five shortcodes that render through the public TraceWise embed. Each one can target a different public status page, and a page loads the embed script once.<\/li>\n<li>Add a TraceWise menu for public widgets, connection, monitor health, uptime, incidents, diagnostics, and monitor create, edit, check, and delete.<\/li>\n<li>Add a WordPress Dashboard widget for administrators.<\/li>\n<li>Store the API key encrypted on the server. Public widgets remain usable without a key.<\/li>\n<\/ul>","raw_excerpt":"Show visitors live uptime and incident status in WordPress. Public widgets need no API key.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/392686","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=392686"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/razorsoftinc"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=392686"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=392686"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=392686"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=392686"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=392686"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=392686"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}