Changelog
Nouveautés de Relvato
Chaque mise à jour de l’app Relvato et du plugin WordPress, de la plus récente à la plus ancienne.
- Fix: the new Relvato Dashboard page fataled ("call to undefined method is_connected()") on 0.2.24.
- Add: the plugin now announces its connection to Relvato outbound (a signed "hello" on connect), so setup detects it within seconds even on sites whose REST API isn't reachable from Relvato (plain permalinks, a security plugin, or a host catch-all). Relvato also now reaches your plugin's endpoints via the permalink-independent form automatically, so a store on plain permalinks connects without any configuration change.
- Add: Relvato now has its own top-level admin menu (instead of living under Settings), with two pages: Dashboard — a read-only overview of this site's checks (journeys, statuses, pass rates, recent runs, mirrored from your Relvato dashboard) plus a prominent link to the full app — and
- *Settings** (unchanged).
- Fix: Logged-in checkout email delivery. The dedicated verification user's WooCommerce BILLING email is now kept in sync with the verification inbox, so a logged-in test order's confirmation email reaches the inbox and delivery can be verified. Previously a logged-in checkout (which hides the checkout email field behind the saved address) sent the confirmation to a stale saved billing address, showing a false "email not delivered".
- Change: Clicking "Check again" on Dashboard → Updates now bypasses the plugin's own update cache, so a newly-shipped Relvato version appears immediately instead of after up to 6 hours.
- Fix: WordPress core update version reporting. A core update now reports the correct new version (e.g. "7.0.2 → 7.1"). Previously the version was read during the update request, when WordPress still had the OLD version in memory, so it could report a stale/wrong "to" version. Core changes are now detected on the next page load, where the version is authoritative.
- Change: Relvato moved to its own domain (app.relvato.com). This only affects the default used by the "Connect with Relvato" button and update checks on sites that aren't connected yet — already-connected sites keep working unchanged (they use the endpoint from your connect token).
- Add: store-info now reports your site's CAPABILITIES — a categorized summary of your theme and active plugins (e.g. "WooCommerce + Elementor + Contact Form 7"), NOT the raw plugin list. Relvato uses this to recommend the checks that fit your store instead of making you pick from a long list. Only capability categories are sent; the individual plugin names/versions never leave your site.
- Add: the plugin now updates itself. WordPress shows a normal "update available" notice and a one-click update on the Plugins screen when a new Relvato version ships, served securely from Relvato (not the wordpress.org directory). Note: this self-update capability starts working from 0.2.20 onward, so this one release must be installed manually; every version after it updates in place.
- Fix: The plugin no longer reports changes to ITSELF — activating, deactivating, or updating Relvato won't trigger a verification run (previously an activation fired a "plugin changed" event and kicked off journeys). Relvato's server also ignores self-only plugin events, so this is fixed even on older plugins.
- Add: token-gated endpoint that triggers WordPress's password-reset email for the dedicated verification user (server-side, no login form / CAPTCHA). Powers Relvato's new "Password reset" journey, which confirms the store still SENDS the reset email and that it DELIVERS to the inbox. Only touches the non-admin verification user; the reset link goes to the verification inbox and is never used, so the user's password is unchanged.
- Add: token-gated login-credential endpoint so Relvato's new "Customer login" journey can exercise the REAL login form (not just the trusted-cookie shortcut). It vends a one-time random password for the dedicated verification user — rotated on every call, so the previous one is instantly invalid — and only ever touches that non-admin user. No customer password is stored or handled.
- Add: store-info now reports the store's canonical page URLs (shop, cart, checkout, account) plus a sample product category. Relvato's new visual-regression journey uses these to snapshot the right pages without guessing.
- Fix: Serialize the debounced change-event buffer with a MySQL advisory lock, so simultaneous updates (a plugin activating while another finishes updating) can no longer clobber each other's entry and drop an event. The dispatch drain now holds the same lock, so an event queued at the moment of dispatch can't be deleted unsent.
- Add: change events now carry per-target detail — the human name and the from→to version — so a run triggered by an update shows exactly what changed (e.g. "WooCommerce updated 8.1.0 → 8.2.0", "Yoast SEO activated"). Versions are diffed against a one-time snapshot of installed plugin/theme/core versions. This powers the run's "What changed" panel, making it easy to pinpoint which update a new failure lines up with.
- Add: store-info now reports checkout capabilities for onboarding calibration — whether guest checkout is enabled, and the store's base country/state/city/postcode. Relvato uses these to drive an arbitrary store's checkout deterministically (a valid sample address for the store's own country instead of a hardcoded region), and to know whether guest checkout is available without guessing.
- Fix: MailPoet auto-confirm now also handles an already-existing unconfirmed verification subscriber (MailPoet's public API can only create one as confirmed, not flip an existing one). So the robot inbox stays deliverable and email checks confirm delivery on MailPoet stores without any manual step.
- Add: Email "dispatch" signal — the plugin now records when WooCommerce generates the customer order-confirmation email for a verification order, exposed via a token-gated endpoint. Relvato can confirm your store *sends* order emails even when they don't reach the verification inbox (e.g. MailPoet won't email a non-subscriber), so email checks are robust across every email setup.
- Add: When MailPoet is active, the verification address is marked as a confirmed subscriber automatically, so MailPoet's double opt-in doesn't silently stop delivery to it. Best-effort.