A small fix release: three bugs, all found on real sites. Uptime Kuma connects through proxies that block WebSockets, pull db stops leaving production URLs behind, and the media fallback works while a site is mid-conversion to Bedrock.
Fixed
- Uptime Kuma connects through proxies that block WebSockets. SpinupTUI was meant to fall back to plain HTTP when a WebSocket failed, but the fallback never actually ran. So a reverse proxy or CDN that doesn't pass WebSocket upgrades failed the whole connection, though Kuma also answers over HTTP. It now retries over HTTP. If both attempts fail, the error gives each one's real reason (e.g.
Expected 101 status code (WebSocket); HTTP 404 (polling)), where before it said onlywebsocket error. pull dbrewrites awww.site's URLs. The rewrite started from the SpinupWP domain. So a site whose domain isexample.combut whose WordPress home ishttps://www.example.comkept everywww.URL pointing at production, even though every step showed ✓. The pull now asks production for its home URL over the same SSH connection as the export, and rewrites that as well as the domain. Post-import hooks get the home URL's host asSYNC_REMOTE_HOST, and every rewritten host in the newSYNC_REMOTE_HOSTS.pull dbrewrites URLs in plugin tables too. wp-cli'ssearch-replacecovers only WordPress's core tables unless told otherwise. So Yoast's indexables (and with them the local copy's canonical and schema URLs), cache and log tables, and form entries all kept production URLs. The rewrite now covers every table with the site's prefix.- The production media fallback (
m) works when production runs a different stack. When a Standard WP site had been converted to Bedrock locally but production hadn't been switched yet, every missing image pointed at production's/app/uploads, which doesn't exist there, while the dialog said ON. The plugin (now v3) maps the local uploads path to production's, based on production's stack. Themdialog shows the mapping when the two differ. Pressuin themdialog to update an installed plugin.