Install and Connect

Outcome

You will install the TMXIO WordPress Plugin on a self-hosted WordPress site, connect the site to a TMXIO workspace, and confirm that the connection is healthy. By the end of this guide the plugin should report the site as connected, the site should appear in TMXIO, and the Test Connection action should return successfully without retries.

This page is the plugin-side companion to Connect a WordPress Site. Either page is a reasonable starting point — this one assumes you are working from inside WordPress admin, while the other is written from the TMXIO dashboard perspective.

Prerequisites

Make sure all of the following are true before you start:

• WordPress 5.8 or newer. Older WordPress versions are missing REST API features the plugin relies on. Update WordPress core first if you are below 5.8.
• PHP 7.4 or newer. The plugin uses language features and crypto libraries that require at least PHP 7.4. PHP 8.1+ is recommended on new hosts.
• cURL available on the WordPress host. The plugin issues outbound HTTPS calls through cURL. If cURL is not compiled into PHP, the plugin will refuse to save a connection.
• WordPress admin access. Editor and contributor roles are not enough; the plugin’s settings page is admin-only.
• Access to the correct TMXIO workspace. You either need a TMXIO login that can reach the right workspace, or an API key generated by someone who can.

If you do not know whether cURL is available, the plugin will tell you on first load. There is no need to check ahead of time.

Installing the Plugin

1. Install and activate the plugin in WordPress.

   Install the TMXIO WordPress Plugin in WordPress and activate it. The plugin can be installed from the WordPress plugin directory the same way as any other plugin. Once it is active, open the TMXIO area in WordPress admin from the left-hand sidebar.

2. Choose the modern connection path.

   The current plugin flow centers on either creating a TMXIO account from WordPress, or entering an existing TMXIO API key. Use the account-creation path when the person installing the plugin does not yet have a TMXIO login. Use the API-key path when the account already exists and a key has been provided.

   If the account belongs to more than one TMXIO workspace, the plugin may ask you to select the correct workspace before the site is saved. Pick the workspace the site should belong to; this becomes a load-bearing choice for every later report.

   Behind HTTP auth?

   If your site sits behind HTTP Basic Auth or Cloudflare Access, TMXIO cannot reach the API. Either whitelist TMXIO’s IPs or temporarily disable auth on /wp-json/. The plugin’s first save call goes through the WordPress REST API surface, so anything that blocks /wp-json/ will block the connection. Re-enable the auth wall after the connection is established if you need it for the staging environment.

3. Save and validate the connection.

   Save the connection from WordPress admin. After a successful save, use the visible Test Connection action to confirm that the site can communicate with TMXIO end to end. A green result here is the strongest signal that the install is good.

Legacy Connection Path

Older internal notes and older versions of the plugin may refer to a “workspace token” as the primary connection path. Treat that as legacy or fallback language and do not use it as your default flow for new setups. The current plugin centers on a TMXIO account plus an API key, and that is what support will troubleshoot from.

If you are stuck on an older plugin version that only offers the workspace-token path, update the plugin before continuing. Connection flow improvements are not backported.

What Success Looks Like

• The plugin shows the site as connected, with the linked account context visible.
• The site appears in the correct TMXIO workspace, with a recent last-seen timestamp.
• Test Connection succeeds without a retry.
• The site’s first scheduled heartbeat arrives within a few minutes of the initial save.

After Connecting

Once the site is connected you can enable optional features (Error Monitoring, 1-Click Access, and so on) from the plugin’s settings page. See Common Tasks for what those features do and when to turn them on. See Heartbeat and Status for what TMXIO is checking on the site once it is connected.

Related Troubleshooting

• If the site is protected by HTTP auth, see the HTTP Auth tab in Troubleshooting.
• If the connection fails after a save, see the Connection tab in Troubleshooting.
• If the connection saves but the site reports as disconnected within minutes, the heartbeat path is failing rather than the credential exchange. See Heartbeat and Status.