Skip to content
Help centre

What the WordPress connector does

Check-ins and wake-ups, what the plugin reports, how it updates sites one at a time, the feedback widget, one-click login, MailPoet and self-updates.

The OpsDash Connector is how OpsDash talks to a WordPress site. Here's what it does, and what it doesn't.

Check-ins

The plugin checks in about every five minutes. Each check-in reports the site's WordPress and PHP versions, its plugins and themes (with available updates), any PHP error on its pages, and its administrators (for one-click login). OpsDash replies with anything waiting: an update run to start, a setting change, a repair.

Check-ins rely on WP-Cron, WordPress's built-in scheduler, which only runs when someone visits the site. Quiet sites can miss check-ins.

Wake-ups

When something's waiting (an update run, for example), OpsDash wakes the site by calling it, so it checks in straight away rather than waiting for a visitor. Plugin 1.3.1 or later can be woken at any time; older versions only while an update run waits.

If a site has WP-Cron switched off (DISABLE_WP_CRON), it only checks in when OpsDash wakes it or a server cron loads wp-cron.php. The plugin's settings page and the site's page in OpsDash both say so. For the most reliable check-ins on such sites, set up a server cron that loads wp-cron.php every few minutes.

Check now in OpsDash asks the site to check in; Check in now on the plugin's settings page in WordPress does the same from the site.

Updates

During an update run, the plugin:

  1. backs up the database once for the run, a little at a time (so hosts that stop PHP early or give it little memory can still finish), unless the site is set to Files only because the host keeps database backups,
  2. updates one package at a time, keeping that package's own files and settings first,
  3. checks the site is healthy after each one (OpsDash also checks it from outside),
  4. rolls a package back if it broke the site, telling OpsDash why.

A PHP error the site already had before an update doesn't count against that update. See backups and restores and what the run messages mean.

Other things it does

  • Feedback widget: adds the website feedback widget when OpsDash says so (plugin 1.2.0 or later). Switch it off, or set it to staging only, on the site's page in Site health.
  • One-click login: signs your agency's staff in to wp-admin with a one-time link that OpsDash confirms first, where you've switched it on. It never creates users. See one-click WordPress login.
  • MailPoet: when MailPoet is active, it sends OpsDash the site's lists and newsletter results from the last 180 days once an hour, and new unsubscribes (email address and when) once a MailPoet connection uses this site. No other subscriber details leave the site.
  • Self-updates: it updates itself from OpsDash, so new fixes arrive without anyone logging in.
  • Database repair: it finds, and when asked repairs, values damaged by restores made with plugin versions before 1.3.4.

The plugin's settings page

In WordPress, Settings › OpsDash shows the version, the OpsDash address and site token, Check in now, recent one-click logins, and notes about the feedback widget and MailPoet.

Emergency stop

Owners and admins can stop all updates, backups and restores at once with Pause all WordPress updates and restores in Settings › Site health. Check-ins carry on; nothing is changed on the sites.

These open in OpsDash. You’ll be asked to sign in first if you aren’t already.