Skip to content
TMXIO Support

Common Tasks

Outcome

Section titled “Outcome”

You will know where to find the plugin tasks customers use most often after the site is connected: the recovery action when a site looks degraded, the settings panel for the active connection, and the optional features that change what TMXIO can see and do on the site.

Each task below is presented as a short ordered procedure rather than a paragraph. Use the order described — most of these tasks are forgiving, but a few are easier to get right the first time than to recover from.

Test Connection Stable

Section titled “Test Connection ”

Test Connection runs the same code path as a regular heartbeat. It is the fastest customer-visible way to confirm whether the plugin can still reach TMXIO normally, and it is the first action to try when a site looks degraded or disconnected in the dashboard.

  1. Sign into WordPress admin as an administrator on the affected site.
  2. Open the TMXIO plugin from the left-hand admin menu.
  3. Click the Test Connection button on the plugin’s main settings page.
  4. Read the result. A success means the next scheduled heartbeat will almost certainly land. A failure shows you the specific failure mode (DNS, TLS, credential rejection, edge auth, timeout) and is enough to point at the right troubleshooting section.

If Test Connection succeeds but the dashboard still reports a degraded or disconnected status, wait one or two minutes for the next heartbeat to clear the previous miss count before assuming something is still wrong.

Manage Connection Settings Stable

Section titled “Manage Connection Settings ”

Once a site is connected, the plugin exposes a small set of customer-facing controls. These are not deployment knobs — they are everyday settings that change how the site is represented in TMXIO.

  1. Open the TMXIO plugin in WordPress admin.
  2. Locate the connection summary at the top of the settings page. It shows the connected site, the account context, and the workspace the site belongs to.
  3. Use the link back to the TMXIO account if you need to manage subscription, billing, or team access. The plugin does not duplicate those screens; it opens them in TMXIO.
  4. Use the feature toggles below the summary to enable or disable Error Monitoring and 1-Click Access. Both are described in their own sections below.

The connection summary is the canonical view of what the WordPress side believes about the connection. If WordPress and TMXIO disagree about which workspace a site belongs to, the summary is where you confirm what the plugin actually saved.

Error Monitoring Stable

Section titled “Error Monitoring ”

Error Monitoring lets TMXIO collect operational error data from the WordPress install so support can help diagnose problems without asking you to dig through log files. It is opt-in and can be turned off at any time.

  1. Open the TMXIO plugin in WordPress admin.
  2. Find the Error Monitoring toggle on the plugin’s settings page.
  3. Enable it. The plugin records the change and TMXIO starts accepting error data on the next heartbeat.
  4. If you ever want to stop sending error data, toggle the setting back off. Existing data already received is unaffected; only new data stops flowing.

For the privacy and data-collection policy behind this feature, see What Information Do We Collect?. Read that page before enabling Error Monitoring in environments with regulatory restrictions on outbound data.

1-Click Access Stable

Section titled “1-Click Access ”

1-Click Access lets a TMXIO operator open WordPress admin from the TMXIO dashboard without typing a username or password. It is convenient for support workflows and for teams that manage many sites, and it is opt-in.

  1. Open the TMXIO plugin in WordPress admin.
  2. Find the 1-Click Access toggle on the plugin’s settings page.
  3. Enable it. The plugin records the change and TMXIO starts allowing the 1-Click Access flow for users who have access to the site in the dashboard.
  4. Confirm the result by initiating a 1-Click Access from TMXIO. Your operator should land directly inside the WordPress admin area without an interactive login prompt.

If you disable 1-Click Access later, existing sessions in WordPress are not invalidated, but no new 1-Click Access entries can be opened against the site. For the customer-facing explanation of the feature, see Understanding TMXIO 1-Click Access.

Disconnect a Site Stable

Section titled “Disconnect a Site ”

Use this when you intentionally want a site removed from the active TMXIO connection. Disconnecting does not delete the WordPress site or its data; it only removes the link between WordPress and TMXIO.

  1. Open the TMXIO plugin in WordPress admin on the site you are removing.
  2. Confirm in the connection summary that you are about to disconnect the correct site and workspace. Disconnecting the wrong staging environment by mistake is the most common avoidable error here.
  3. Use the disconnect action in the plugin first. Plugin-first disconnect keeps the WordPress-side state and the TMXIO-side record aligned.
  4. Refresh both the plugin page and TMXIO. The plugin should drop back to the connection-choice screen and the site should disappear from the active connected-sites list in TMXIO.

For full coverage of disconnect and reconnect scenarios (host moves, key rotation, plugin reinstall, decommissioning) see Disconnect and Reconnect.

Update the Plugin Stable

Section titled “Update the Plugin ”

The TMXIO WordPress Plugin updates the same way as any other WordPress plugin. There is no separate update flow.

  1. In WordPress admin, open Plugins and find the TMXIO WordPress Plugin in the list.
  2. If a new version is available, click the update link inline with the row. WordPress downloads the new package and replaces the existing files.
  3. After the update completes, open the TMXIO plugin and confirm the site is still connected. Updates do not require a reconnect.
  4. Run Test Connection once to confirm the heartbeat path is healthy after the update.

If the plugin’s reported version in TMXIO is older than expected after a successful update, wait for the next heartbeat. The reported version is refreshed on the next heartbeat, not at the moment of update.

Section titled “Related Pages”