1.5.0

What changed since 1.4.0:

• WooCommerce shops report how the shop is running. On a site where WooCommerce is active, the hourly report now also says when the last order came through, how many orders came through or failed in the last day (the failed ones counted by payment gateway), and how many are pending payment, on hold or processing. Spottlab can then tell you when the site is up but nobody can buy. There is nothing to switch on.
• It also reports how the shop is set up. Which payment gateways are switched on and which say they are in test mode, whether WooCommerce's database update is waiting, whether the shop is in "coming soon" mode, and whether its shop, cart, checkout or account page is missing. It also reports how many scheduled actions are late or failed, how many of the shop's webhooks WooCommerce has switched off, how many products are out of stock or low on it, and which of the theme's WooCommerce templates are out of date.
• Counts, times and settings only. It never reports an order itself: not what was bought, what it came to, or who bought it. Like everything else in the plugin, it only reads.
• Nothing changes on a site without WooCommerce.

Test mode is asked of each gateway in the usual ways gateways keep that setting, so a gateway that keeps it some other way is not noticed. A live gateway is never reported as testing.

Sites on 1.3.0 or later update from the Plugins page as usual. Older ones take this one by hand: download spottlab-connector.zip below and upload it under Plugins → Add New Plugin → Upload Plugin.

1.4.0

What changed since 1.3.3:

• Updates show up within hours of a release. WordPress only knows about plugin and theme updates from its last check with WordPress.org. WP-Cron runs that check twice a day, or never on sites where cron doesn't run, such as a site behind a password, or one with DISABLE_WP_CRON and no system cron. Now, when Spottlab asks for its hourly report and WordPress's last check is more than two hours old, the plugin has WordPress check again first, as Dashboard → Updates does.
• A failed check doesn't affect the report. If WordPress.org can't be reached, Spottlab still gets the same plugin and theme versions and the updates WordPress already knew about. It also gets the reason the check failed and the time the list last came in. The check gets ten seconds at most, and nothing Spottlab sends can make it run more often.

Sites on 1.3.0 or later update from the Plugins page as usual. Older ones take this one by hand: download spottlab-connector.zip below and upload it under Plugins → Add New Plugin → Upload Plugin.

1.3.3

What changed since 1.3.1 (1.3.2 was never released here):

• Installs with Composer. In a Bedrock project, or any site with composer/installers: composer require spottlab/wordpress-connector. It lands in the plugins directory under the plugin's own folder, spottlab-connector, as the zip does.
• The repository is now Spottlab/wordpress-connector. Updates are checked here from this version on; GitHub forwards the old name.
• Tested up to on the Plugins page names the newest WordPress release in the tested branch, not only its first.
• An icon on the Plugins page and in the update details.

Sites on 1.3.0 or later update from the Plugins page as usual. Older ones take this one by hand: download spottlab-connector.zip below and upload it under Plugins → Add New Plugin → Upload Plugin.

1.3.1

The first release on GitHub, with what changed since 1.2.1:

• Updates from WordPress. New versions show on the Plugins page like any other plugin's, and can update on their own. Each one is signed by Spottlab and installs only if it is the exact file that was signed.
• Called the Spottlab connector in WordPress: its settings are under Settings → Spottlab connector.
• Fixed: on WordPress 7.1 the full report failed (get_home_path() was not loaded), so Spottlab could not see the site's updates.

Sites on 1.2.1 or older need this one update by hand: download spottlab-connector.zip below and upload it under Plugins → Add New Plugin → Upload Plugin.