Bug: Call to undefined function Geolocation\Provider\wp_tempnam()

ResolvedPlugin Contributor

(@toxicum)

Since 7.4.1, we get this fatal PHP error log on cron access:
I’m not sure if the other Geolocation posts for 7.4.1 are caused by this problem as well.
PHP 8.4, latest WP release.

===== PHP FATAL ERROR =====
Error: Uncaught Error: Call to undefined function SlimStat\Services\Geolocation\Provider\wp_tempnam() in wp-content/plugins/wp-slimstat/src/Services/Geolocation/Provider/DbIpProvider.php:65
Stack trace:
#0 wp-content/plugins/wp-slimstat/src/Services/Geolocation/GeolocationService.php(24): SlimStat\Services\Geolocation\Provider\DbIpProvider->updateDatabase()
#1 wp-content/plugins/wp-slimstat/wp-slimstat.php(1212): SlimStat\Services\Geolocation\GeolocationService->updateDatabase()
#2 wp-includes/class-wp-hook.php(341): wp_slimstat::wp_slimstat_update_geoip_database()
#3 wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#4 wp-includes/plugin.php(570): WP_Hook->do_action()
#5 wp-cron.php(191): do_action_ref_array()
#6 {main}
thrown in wp-content/plugins/wp-slimstat/src/Services/Geolocation/Provider/DbIpProvider.php on line 65
Request URI: /wp-cron.php?doing_wp_cron
Method: GET
Query String: doing_wp_cron

I’m not sure if the other Geolocation posts for 7.4.1 are caused by this problem as well:

https://wordpress.org/support/topic/geolocation-displays-unknown-in-the-dashboard-access-log/

https://wordpress.org/support/topic/after-updating-to-5-4-1-and-disabling-gdpr-no-longer-get-city-state-ip-in-log/

Viewing 5 replies - 1 through 5 (of 5 total)

Plugin Contributor Parhum Khoshbakht
(@parhumm)

2 weeks ago

Thanks for reporting this, @toxicum — and for the clear stack trace. That made it straightforward to track down.

You’re right, this is a confirmed bug. The DB-IP geolocation provider calls wp_tempnam() without first loading the WordPress admin file that defines it. During WP-Cron, those admin includes aren’t available, which triggers the fatal error you’re seeing.

We’ve identified the fix and it’s planned for the next release. You can follow progress here: https://github.com/wp-slimstat/wp-slimstat/issues/180

Appreciate you flagging this!

Plugin Contributor Parhum Khoshbakht
(@parhumm)

1 week, 4 days ago

Hi @toxicum,

Quick update — this bug is now fixed in version 5.4.2, which is available now. The crash during background geolocation database updates has been resolved, along with several other geolocation improvements.

Please update through your WordPress dashboard and the cron error should be gone. And yes, you were right that the other geolocation threads were likely related — v5.4.2 addresses those as well.

Thanks again for the detailed report and for connecting the dots on the related threads!

Plugin Contributor Parhum Khoshbakht
(@parhumm)

1 week, 2 days ago

Hi @toxicum ,

Just a quick follow-up — we’ve since released version 5.4.4, which includes additional stability and geolocation improvements on top of the original fix. If you haven’t already, we’d recommend updating to the latest version through your WordPress dashboard.

If the cron error is gone on your end, we’ll go ahead and mark this thread as resolved.

Feel free to reopen if anything comes up.

Thanks again for the report!

Plugin Contributor Parhum Khoshbakht
(@parhumm)

3 days, 15 hours ago

Hi @toxicum ,

One more update — we’ve just released version 5.4.6. Beyond the geolocation fix you reported, this release addresses several regressions introduced in the 5.4.x series: visitor counts dropping to zero, IPs being masked without permission, and a consent banner appearing on sites that never enabled it. After updating, your site should work the way it did before 5.4.0 — no manual steps required.

If you’re using a caching plugin (WP Rocket, W3TC, etc.), please clear your cache after updating.

Once you’ve updated, visit a few pages on your site and check the Access Log to confirm new data is being recorded. If anything looks off, we’re here to help.

Thanks again for the original report — it helped us track down several related issues.

Plugin Contributor toxicum
(@toxicum)

3 days, 9 hours ago

thanks for the quick fixes.

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

Tags