Changelog
Was ist neu in Relvato
Jedes Update der Relvato-App und des WordPress-Plugins, neueste zuerst.
Relvato-Appv1.3.6
WordPress-Pluginv1.77.2
WordPressWP 7.1.3Getestet bis WP 7.1
Die Relvato-App aktualisiert sich automatisch – beim Öffnen hast du immer die neueste Version. Das WordPress-Plugin wird über WordPress aktualisiert, automatisch oder manuell, je nach den Update-Einstellungen deiner Website. Es kommt von WordPress.org.
- Changed: Relvato is now on WordPress.org, and the plugin updates from there like any other. Sites that installed it from relvato.com move over with this version; nothing to do.
- Fixed: wp-config.php is checked for malware patterns again (only the pattern's name is reported; 1.77.0 skipped it along with its hash).
- Readme: says exactly what Relvato's requests can create or change — only its own test data, including how the test customer is signed in.
- Changed: Relvato never applies a fix or changes a plugin on its own. Fixes, plugin updates, rollbacks, deactivations and their undo are applied by an administrator under "Relvato suggests" in WordPress → Relvato (each needs the matching WordPress permission); the plugin then tells Relvato, which re-runs its monitors to verify the change. The routes Relvato's service used to apply them are removed.
- Changed: during quarantine mode, pausing plugin and theme auto-updates is a tick box in WordPress → Relvato, set by an administrator.
- Changed: Relvato's scheduled update window no longer runs on sites with this version; WordPress's own automatic updates keep working, and an update that breaks a monitor is offered as a one-click rollback in WordPress → Relvato.
- Security: the plugin no longer reads the values of your WordPress keys and salts, and wp-config.php is no longer part of the file fingerprint. Every admin page is escaped as it's printed. The activity log and quarantine record a file-editor save only with WordPress's own check for that save.
- Changed: "Tested up to" is declared only in this readme, no longer in the plugin file's header, as WordPress.org now requires.
- Fixed: the Runs list heading ("The latest 5 runs") now translates correctly in languages whose singular form also covers numbers like 21.
- Changed: on setup's last step, the activity log and real-user Web Vitals start unticked; only the switches you tick go on with your monitors. Test login and form tests stay ticked.
- Changed: backups of plugins that aren't from WordPress.org are kept only once the site is connected.
- Changed: the description and the dashboard group "Legal & accessibility" no longer say "legal compliance": Relvato reports what it finds on your legal pages, cookie banner and accessibility; it doesn't certify anything.
- New: suggested privacy-policy text for the real-user speed script and the activity log (Settings → Privacy → Policy Guide).
- Fixed: with two copies of Relvato in two plugin folders, activating the second no longer stops with a fatal error.
- Readme: the FAQ and External services now say exactly what Test login sends, and when plugin backups are made.
- Fixed: a monitor still collecting data (Real-user Web Vitals before enough page views) no longer counts as "couldn't run" on the Overview's "Monitors passing" row. It's ready — Ready to run says so — and the row now shows it as "1 collecting data", with a note that it's counted once there's enough.
- New: the Overview's "Monitors passing" row now says how many monitors passed and how many it leaves out — e.g. "26 of 27 passing · 3 couldn’t run". Monitors that couldn’t run or haven’t run yet aren't in the percentage, so a 100% that covers only part of your monitors now says so. "Ready to run" shows why each one is left out.
- Changed: the Overview's "Site health" card is now "Monitors passing" — it was always the share of your monitors whose latest run passed, not a score for the whole site. "Health over time" is now "Passing over time". Nothing about how it's counted changed.
- Fixed: switches ticked on setup's last step — Test login, form tests, the activity log — weren't saved (only Real-user Web Vitals was), so Customer login and Logged-in checkout still reported Test login as off. They're saved now. If you set up with 1.74.0, turn Test login on in Relvato → Settings.
- New: setup's "When should they run?" step lists the plugin switches your chosen monitors need — Test login, Real-user Web Vitals, form tests, the activity log — with what each does, ticked. They go on with your monitors (untick any first), so Customer login, Logged-in checkout and real-user Web Vitals run from the start instead of waiting for you in Settings.
- Fixed: right after setup, every group read "All clear" and Site health 100% while the monitors were still waiting for their first run. Groups now say "First run in progress" (or "All clear so far" with how many are still to come), each monitor shows Queued or Running, and Site health waits until every monitor has a first result.
- New: the header shows how many runs are in the queue and about how long until they're through, updated while you watch.
- Changed: the dashboard keeps up with Relvato while runs are in progress (it used to show a snapshot up to 5 minutes old).
- Changed: "Connect your search accounts" says what connecting Google and Bing is for.
- Change: verified against WooCommerce 11.2. Relvato runs its plugin inside a real WordPress on every release, so this is a result rather than a claim.
- Fixed: "Connect Google Search Console or Bing" during setup opened Relvato's own setup in the new tab, asking you to set the site up again. It now opens a page that only connects the accounts, and the setup screen in WordPress shows what's connected when you come back to it.
- Changed: the free plan can now run monitors weekly, and Pro daily. "How often" names the plan that adds the next schedule ("Daily scheduled monitors are on the Pro plan and up.").
- Changed: "Run them again after updates to" reads "Relvato automatically re-verifies what it could have broken."
- New: on the free plan, an "Upgrade to Pro" link beside the plan name opens the pricing page.