Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
904bf52960 | ||
|
|
8ea7b9f5be | ||
|
|
804a1aae58 | ||
|
|
76e585139e | ||
|
|
f871592d27 | ||
|
|
f1375d3d7d | ||
|
|
72fa8e8901 | ||
|
|
efa84723ee | ||
|
|
39616478c9 | ||
|
|
c1969d4293 | ||
|
|
524b893e65 | ||
|
|
303f31e869 | ||
|
|
20a2a84ee8 | ||
|
|
9127b06836 | ||
|
|
19cb788556 | ||
|
|
e52046437b | ||
|
|
5d36e1058f | ||
|
|
b79ead3dcf | ||
|
|
b0102ea518 | ||
|
|
1b8d7950f5 | ||
|
|
56284b5d20 | ||
|
|
037c2b8cc6 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.23.8",
|
||||
"released_at": "2026-08-09T23:29:08+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.8/argus-wordpress-defence-7.23.8.zip",
|
||||
"sha256": "ae70d35da7dfaebecaefa4ffefc86f2bec72b1e850d7a91c7efcdbc0810d52bb",
|
||||
"version": "7.23.31",
|
||||
"released_at": "2026-08-12T15:21:11+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.31/argus-wordpress-defence-7.23.31.zip",
|
||||
"sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "The Premium panel now clearly shows Connected -- Premium or Connected -- Trial with your real expiry date, persistently. Fixed a bug where an empty license field could wipe your active license, and fixed getting stuck on Connecting... after activating. Updates now check every 5 minutes.",
|
||||
"signature": "t2a97trTH9isBNZkRSt0E7sUfVZN0lJLBBH/E42MnnBkJdG0cS+7oRmQ3oWUs3za/syJGu2Pm8hrnSMzX0cZCw=="
|
||||
"summary": "* Fixed: right after ARGUS checked for updates, its own health check could momentarily read that\n timestamp before it was refreshed and report \"hasn't checked for updates\" -- the two checks now\n run in the correct order.\n* The health-check findings for scanner/update/intelligence timing now explain the most common\n real cause specifically -- WordPress's own scheduled-task system (WP-Cron) not firing reliably,\n common on low-traffic sites or hosts without a real system cron configured -- instead of a\n generic \"contact support.\"",
|
||||
"signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user