wpsnoop: fix WP Geofence plugin conflicts, errors & issues

When the plugin WP Geofence conflicts or throws a PHP error we hope wpsnoop can help you to fix the issue quickly.


Discover which shortcodes wp-options PHP functions database tables and files are created by WP Geofence, plus learn which plugins and/or themes could be in conflict with WP Geofence.


Troubleshooting theme and plugin conflicts is easier when you know what WP Geofence leaves behind after uninstalling it from a WordPress installation, there is a list down below for your convenience.

Expert advice is recommended if you are not technically proficient with PHP, MySQL etc. View support options for WP Geofence

Get professional support for WP Geofence here

When you need professional help with WordPress: get help here


What does WP Geofence version 1.0 add to WordPress? Answers Here.

This is an automatically generated report - it is possible for WP Geofence to perform differently in your installation, previous versions before 1.0 may have created a different set of shortcodes, used different function names or could have created entirely different database tables to store settings and operate. This is not an exhaustive list but shows how version 1.0 of WP Geofence behaves when installed and removed on a clean installation of WordPress.

We have not tested individual shortcodes, features or settings of this plugin but instead have concentrated on the potential for obvious errors and conflicts which can occur, if you need help with the plugin in your local installation you can get WordPress help and support for WP Geofence by clicking here.

Our testing covered the free version of this plugin there may or may not be a paid version or premium version available for purchase that unlocks additional features and could behave in a slightly or very different manner.

Which new files does WP Geofence add to WordPress?

This section will populate with a table showing an icon, size and filepath.

Type & Path Size Conflicts
wp-content/plugins/wp-geofence/ 1.34MB No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/.gitignore 257.00B No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/GeoIP.dat 1.24MB No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/geoip.inc 30.97kB No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/index.php 28.00B No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/LICENSE 17.93kB No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/README.md 883.00B No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/readme.txt 2.26kB No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/screenshot-1.png 17.79kB No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/screenshot-2.png 16.65kB No known conflicts with other themes or plugins.
wp-content/plugins/wp-geofence/wp-geofence.php 10.50kB No known conflicts with other themes or plugins.

Which new shortcodes does WP Geofence add to WordPress?

ShortCode   Known Plugin or Theme conflicts
[local] The local shortcode doesn't have any known conflicts with other themes or plugins.

Note: We have not yet checked to see if these shortcodes work as expected in pages, posts, sidebar widgets, or when set as the page title, in content, in the excert, in menus or anywhere else within a WordPress installation. A shortcode could produce errors due to parameters added when it is used, or if the plugin is updated and the format of the shortcode has changed.

Which new database tables are created by the WordPress plugin WP Geofence?

Which new options are added to the wp-options table by WP Geofence?

What new PHP functions does WP Geofence declare when it is active?

Function   Conflicts Common Errors
_common_get_org 15 conflicts Fatal error: Cannot redeclare _common_get_org()
_geoip_seek_country 18 conflicts Fatal error: Cannot redeclare _geoip_seek_country()
_geoip_seek_country_v6 15 conflicts Fatal error: Cannot redeclare _geoip_seek_country_v6()
_get_org 19 conflicts Fatal error: Cannot redeclare _get_org()
_get_org_v6 16 conflicts Fatal error: Cannot redeclare _get_org_v6()
_get_region 18 conflicts Fatal error: Cannot redeclare _get_region()
_setup_segments 18 conflicts Fatal error: Cannot redeclare _setup_segments()
geoip_close 18 conflicts Fatal error: Cannot redeclare geoip_close()
geoip_country_code_by_addr 18 conflicts Fatal error: Cannot redeclare geoip_country_code_by_addr()
geoip_country_code_by_addr_v6 15 conflicts Fatal error: Cannot redeclare geoip_country_code_by_addr_v6()
geoip_country_code_by_name 18 conflicts Fatal error: Cannot redeclare geoip_country_code_by_name()
geoip_country_code_by_name_v6 15 conflicts Fatal error: Cannot redeclare geoip_country_code_by_name_v6()
geoip_country_id_by_addr 18 conflicts Fatal error: Cannot redeclare geoip_country_id_by_addr()
geoip_country_id_by_addr_v6 15 conflicts Fatal error: Cannot redeclare geoip_country_id_by_addr_v6()
geoip_country_id_by_name 18 conflicts Fatal error: Cannot redeclare geoip_country_id_by_name()
geoip_country_id_by_name_v6 15 conflicts Fatal error: Cannot redeclare geoip_country_id_by_name_v6()
geoip_country_name_by_addr 18 conflicts Fatal error: Cannot redeclare geoip_country_name_by_addr()
geoip_country_name_by_addr_v6 15 conflicts Fatal error: Cannot redeclare geoip_country_name_by_addr_v6()
geoip_country_name_by_name 18 conflicts Fatal error: Cannot redeclare geoip_country_name_by_name()
geoip_country_name_by_name_v6 15 conflicts Fatal error: Cannot redeclare geoip_country_name_by_name_v6()
geoip_load_shared_mem 18 conflicts Fatal error: Cannot redeclare geoip_load_shared_mem()
geoip_name_by_addr 14 conflicts Fatal error: Cannot redeclare geoip_name_by_addr()
geoip_name_by_addr_v6 15 conflicts Fatal error: Cannot redeclare geoip_name_by_addr_v6()
geoip_open 18 conflicts Fatal error: Cannot redeclare geoip_open()
geoip_org_by_addr 18 conflicts Fatal error: Cannot redeclare geoip_org_by_addr()
geoip_region_by_addr 19 conflicts Fatal error: Cannot redeclare geoip_region_by_addr()
getdnsattributes 13 conflicts Fatal error: Cannot redeclare getdnsattributes()
init_plug 0 conflicts Fatal error: Cannot redeclare init_plug()

Using WP Geofence from the command line with WP-CLI

The following commands are provided for convenience and should only be used if you understand how WP-CLI works. These commands refer to a single WordPress instance and may need to be modified if you are working with a Multisite installation.


How to install WP Geofence from the command line with WP-CLI

Navigate to the root of your WordPress installation and type the following command:

wp plugin install wp-geofence


How to activate WP Geofence from the command line with WP-CLI

To immediately activate WP Geofence after WP-CLI downloads the latest version you can use the following command:

wp plugin install wp-geofence --activate


How to reinstall WP Geofence from the command line with WP-CLI

To force a reinstallation of WP Geofence which overwrites the current plugin without asking for confirmation you can use the following command:

wp plugin install wp-geofence --force


How to update WP Geofence to the latest version from the command line with WP-CLI

wp plugin update wp-geofence


How to delete WP Geofence from the command line with WP-CLI

wp plugin delete wp-geofence

Where can you download earlier versions of WP Geofence?

Whenever possible you should use the latest version of plugins and themes, however if you have recently updated and discovered that you need to install an earlier version you may be able to download other versions of WP Geofence from the WordPress repository by visiting this link.

Please note that installing earlier versions of a theme or plugin is not generally a recommended course of action for most users and could re-introduce security, stability or other issues in WP Geofence

About our testing enviroment

Tests were conducted using Apache 2.4.29, PHP 7.2 on Ubuntu 18.04, MySQL 5.7.33 and WordPress 5.9

It is very possible that different versions of PHP such as PHP 8.0, PHP 7.4, or PHP 7.3 could behave differently with WP Geofence. Different versions of WordPress could implement the features of this plugin in slightly different ways as well.