Thread Starter
dimal
(@dimalifragis)
If of any help, i see this when i temporarily DEactivate the plugin and i REenable it.
Hi @dimalifragis ,
Thanks for reporting this. This warning does not mean WP-Cron generally is not working. Version 1.4 checks for IP Location Block’s specific database-update event, ip_location_block_cron.
Could you please try:
- Open IP Location Block → Advanced → Local databases.
- Disable automatic updates and save.
- Enable automatic updates and save again.
- Refresh Diagnostics.
If the warning remains, please send:
- Whether this is WordPress multisite.
- Which local provider is selected.
- A WP Crontrol screenshot showing ip_location_block_cron, including its arguments and next run.
- Whether the warning remains immediately after a manual database update.
I cannot reproduce the issue yet, so these details will help determine whether the event is genuinely missing or the new diagnostic is reporting a false warning.
Thanks!
Thread Starter
dimal
(@dimalifragis)
I did try your suggestion to disable and reEnable still same issue.
– No MultiSite
– After Manual Update the Error is GONE
I will try to understand and provide the next 2 details
Thanks
Thread Starter
dimal
(@dimalifragis)
Ok,
More.
– GeoLite2 (IP)
and
GeoLite2 (ASN)
and
ip_location_block_cache
Edit | Run now | Pause this hook | Delete
In 11 hours 47 minutes
Tomorrow at 4:30 am Non-repeating None (Help)
ip_location_block_cron
View arguments
Edit | Run now | Pause this hook | Delete
In 1 month
September 30th at 7:09 pm
Schedulele
Non-repeating None (Help)
Hi,
Thanks, this confirms the schedule is now healthy.
The manual database update recreated the missing event:
ip_location_block_cron
Next run: September 30
Status: non-repeating “Non-repeating” is expected.
IP Location Block creates a single event and schedules the next one after each successful database update. The additional few days beyond one month are intentional scheduling variance. No further action is required.
I will investigate why disabling and re-enabling automatic updates did not recreate the event, but the manual update successfully repaired it.
Please let me know if the warning returns while ip_location_block_cron is still listed.
Best Regards,
Darko
Thread Starter
dimal
(@dimalifragis)
Ok. disabled and re-enabled the plugin.
The error/notice is shown.
And the CRONS (2 of them) are there, as i posted them.
Thanks !