{
    "name": "Fiat Insight Dashboard",
    "slug": "fiat-dashboard",
    "version": "5.16.0",
    "download_url": "https://updates.fiatinsight.com/fiat-dashboard-5.16.0.zip",
    "homepage": "https://fiatinsight.com",
    "author": "<a href=\"https://fiatinsight.com\">Fiat Insight</a>",
    "author_homepage": "https://fiatinsight.com",
    "requires": "6.0",
    "tested": "6.8",
    "requires_php": "7.4",
    "last_updated": "2026-09-25 00:00:00",
    "icons": {
        "svg": "https://updates.fiatinsight.com/assets/fiat-logo.svg",
        "1x": "https://updates.fiatinsight.com/assets/fiat-logo-circle.png"
    },
    "sections": {
        "description": "Your site's direct line to Fiat Insight: file support tickets and see your plan and account details right from the dashboard, while we keep your site's caching tuned behind the scenes.",
        "changelog": "<h4>5.16.0 (September 25, 2026)</h4>\n<ul>\n<li>Added protection against a common password-guessing attack that uses WordPress&#039;s older XML-RPC interface. Most sites do not use it, so it is now switched off automatically. Sites that use Jetpack keep it, since Jetpack depends on it, and it can be turned back on from the plugin settings if you need it.</li>\n</ul>\n<h4>5.15.0 (September 23, 2026)</h4>\n<ul>\n<li>Added privacy hardening that prevents WordPress from publishing the list of account names on your site. WordPress does this by default, and while knowing a username is not access on its own, it turns a blind guess into a targeted one. This release installs the protection in monitoring mode first, so nothing changes on your site yet; we enable it site by site once we have confirmed it affects nothing you rely on.</li>\n<li>Added a lightweight counter for anonymous requests to WordPress&#039;s built-in content API, so we can see automated scraping activity against your site and respond to it.</li>\n</ul>\n<h4>5.14.1 (September 16, 2026)</h4>\n<ul>\n<li>Behind-the-scenes reliability fix to how the plugin records plugin and theme updates, so the update activity we track for your site reflects updates that actually completed rather than every routine check. No change to how your site works.</li>\n</ul>\n<h4>5.14.0 (September 10, 2026)</h4>\n<ul>\n<li>The plugin now re-checks its Cloudflare caching rule against your account twice a day instead of trusting what it last recorded. If the rule has been changed, switched off, or removed since it was set up, the plugin notices within a day and puts it back, rather than continuing to report everything as fine.</li>\n<li>Because of that, the &quot;caching is active&quot; status on your dashboard now reflects a rule the plugin has actually confirmed is in place, not one it set up at some point in the past.</li>\n<li>Safer clean-up: when caching is switched off or the plugin is deactivated, it now re-identifies its own rule before removing anything. On accounts where two websites share one Cloudflare zone, this makes it impossible for one site&#039;s clean-up to remove the other site&#039;s rule.</li>\n</ul>\n<h4>5.13.0 (September 10, 2026)</h4>\n<ul>\n<li>Tracking-parameter stripping is now on by default on sites connected to Cloudflare. Links from ads and email campaigns carry a unique code per click, which used to make every visit look like a brand-new page and send it all the way to your server. Setting those codes aside at the network edge means far more visitors are served instantly from cache. Your analytics and embedded forms still see the codes as before, and the setting can be turned off at any time.</li>\n<li>Campaign tags such as utm_source are now left alone. They are the same for everyone who clicks a given campaign link, so those pages already cache well on their own, and leaving the tags in place keeps any form field or report that reads them working normally.</li>\n<li>If a Gravity Forms field on your site fills itself in from a link&#039;s tracking code, the plugin now spots that and leaves the setting switched off until someone decides how to handle it, rather than quietly emptying the field.</li>\n<li>Clearer wording throughout the plugin&#039;s settings and status panels. Notes are shorter and say what to do, not just what was found.</li>\n</ul>\n"
    }
}