Update signed manifest to 7.23.27

manifest.json

@@ -1,11 +1,11 @@
 {
-    "version": "7.23.14",
+    "version": "7.23.27",
-    "released_at": "2026-08-10T10:42:30+00:00",
+    "released_at": "2026-08-10T20:18:36+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.14/argus-wordpress-defence-7.23.14.zip",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.27/argus-wordpress-defence-7.23.27.zip",
-    "sha256": "6b2365b173bd8e583a5d04021d205c773f927217b4870fc3ebff8c298c53367b",
+    "sha256": "6a0a76fe0d3a366b1df62fc351841f91f8e52f19aacbe032a911ca4f0eaeffcb",
     "min_php": "7.4",
     "min_wp": "6.0",
-    "critical": true,
+    "critical": false,
-    "summary": "* Fixed a serious bug: the Firewall could block ordinary visitors just for arriving from an\n  everyday link -- for example, a link shared on Facebook, whose own redirect URL happened to\n  match a pattern the Firewall treated as suspicious. The underlying cause was broader than that\n  one case: 132 of the Firewall's 137 protection rules were checking a visitor's Referer,\n  User-Agent, and X-Forwarded-For information -- values a visitor doesn't control -- when they\n  should only ever have been checking what a visitor actually submits (search terms, form fields,\n  comments, and similar). Those three values are now excluded everywhere except the handful of\n  rules that specifically need them (Log4Shell-style attacks are delivered through exactly those\n  values, so detection there is unchanged). No settings change needed; this takes effect\n  automatically.",
+    "summary": "* Reverted the dashboard's visual redesign (sidebar navigation, larger ring cards) back to the\n  familiar layout while keeping the real fixes that came with it:\n  - The dashboard no longer scrolls the whole WordPress admin page -- the ARGUS header and\n    navigation stay in place while only the dashboard content scrolls.\n  - An active Premium license no longer shows \"0 days left\" next to a correct future renewal\n    date.\n  - The Blocked Requests chart's hover tooltip no longer fails on the most recent data point and\n    no longer renders off-screen near the chart's edge.\n  - IPs Tracked, ANIS Protections, and Global Network cards explain what a \"0\" means (not\n    connected, still connecting, or genuinely clean) instead of showing a bare number, and the\n    Global Network panel now shows correct instance/indicator/feed numbers instead of always\n    showing 0.",
-    "signature": "l3gHdqDlNbkuk88XuJpVOMiAbAMNVoht7lVJ0UgkgvcLgDUTmcnaYS9g6XoHqH6sPTkmLA6TL2SYe3d2d1NOCA=="
+    "signature": "ZSRLTPI5fTv0f81GbB58HCxRYt2QhQSWUZUFVfdeK96zLJ0cGKmbDLC/94sz7HePQqAP1cTKiQFIdghYPhS6Aw=="
 }