This plugin must have read/write permission at the certain places outside of the plugin folder. But in some cases, you might find the error message related to the permission because of your server’s security configurations.
When you meet those cases, you have to configure something related to the WordPress file system by your own hand.
Geolocation API library
Configuring file system
If your host is running under a special installation setup involving symlinks, or certain installations with a PHP FTP extension, you’ll see the following error message when you install and activate this plugin for the first time:
In this case, as of the instruction in this document at codex, you have to configure some symbols in your wp-config.php
something like this:
If you have some reasons you can’t do this, please follow the next instruction.
Installing Geolocation API library
When you’ll see the following when you jump to the option page of this plugin:
In this case, you should install ip-geo-api
that includes geolocation API library named IP-Geo-API for Maxmind and IP2Location under one of the following folders:
/wp-content/
/wp-content/uploads/
/wp-content/plugins/ip-location-block/
You can download the ZIP file and upload ip-geo-api
in the unzipped folder onto the above 1. or 2 with a proper permission using FTP.
ip-geo-api
into 3. is not recommended, because it will be removed at every time this plugin is updated. Here’s a final tree view after uploading ip-geo-api
to 1.
ip-geo-api
and the following folders (ip2location
and maxmind
) a proper permission. It may be 755
but should be confirmed by consulting your hosting administrator. Force to load WP core
When you enable “Force to load WP core” options, this plugin will try to configure .htaccess
in your /wp-content/plugins/
and /wp-content/themes/
folder in order to protect your site against the malicous attacks targeted at the OMG plugins and themes.
If you encounter an “Unable to write” message for plugins, you should put the following directives into your /wp-content/plugins/.htaccess
manually instead of enabling this option:
The absolute path /wp-content/plugins/
should be changed according to your site configuration. And here’s an example directives in /wp-content/themes/.htaccess
: