Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
74fdd42561 | ||
|
|
1e4806457e | ||
|
|
da9237171a |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"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",
|
||||
"version": "7.23.34",
|
||||
"released_at": "2026-08-12T15:34:17+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.34/argus-wordpress-defence-7.23.34.zip",
|
||||
"sha256": "f0290f62814a3893724280fa3d6025b1ad12101901b032fa99a972d0298f272e",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"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=="
|
||||
"summary": "* Overview now shows how many days are left on your active Premium license alongside the\n renewal/expiry date, matching what the trial state already showed.",
|
||||
"signature": "PLlLm5ggjlbdXIf/gd60TKFXq6nAgyk8MhjcoyBydp68gjSifii0fHvMuMCDlxnRaUyD7hlUYtTWe+EhlQ8AAw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user