{"id":34,"date":"2021-05-11T00:28:29","date_gmt":"2021-05-11T00:28:29","guid":{"rendered":"http:\/\/iplocationblock.test\/2021\/05\/11\/shortcode-for-geo-filtering\/"},"modified":"2021-05-11T11:55:33","modified_gmt":"2021-05-11T11:55:33","slug":"shortcode-for-geo-filtering","status":"publish","type":"post","link":"https:\/\/iplocationblock.com\/shortcode-for-geo-filtering\/","title":{"rendered":"Shortcode for Geo Filtering"},"content":{"rendered":"

I started to develop IP Location Block<\/a> as a security purpose plugin so as to protect the back-end of the site. And since version 3.0.0, it has been equipped with the functionality of front-end protection based on this suggestion at the support forum<\/a>.<\/p>\n

This helped to greatly improve the protection ability<\/a> of this plugin against attacks via the front-end of the site.<\/p>\n

<\/p>\n

Need for content filtering by country<\/h3>\n

Meanwhile, this also helped to make the purpose of this plugin ambiguous. Because the function of this plugin to specifying the validation target with the page, post type, category, and tab is not enough for a user who wants to manage contents by Geo-blocking<\/a>.<\/p>\n

\"Front-end<\/p>\n

For example, this discussion<\/a> indicated that not only categories or tags but also custom taxonomies<\/a> are needed to specify the targets.<\/p>\n

\"WP-Property\"<\/a><\/p>\n

But I don\u2019t like to extend the functionality in this direction because I prefer to keep this plugin simple.<\/p>\n

Then what’s the solution?<\/p>\n

Shortcode for Geo Filtering<\/h3>\n

Well, this plugin has much extendability enough to satisfy the demand. You can embed the following snippet for shortcode<\/a> into your functions.php<\/code> to manage the content:<\/p>\n

\n
<?php<\/span>\nif<\/span> (<\/span> class_exists<\/span>(<\/span> 'IP_Location_Block'<\/span> )<\/span> )<\/span> {<\/span>\n    function<\/span> my_filter_content<\/span>(<\/span> $args<\/span>,<\/span> $content<\/span> =<\/span> null<\/span> )<\/span> {<\/span>\n\n        \/\/ get settings and the geolocation of visitor\n<\/span>        $settings<\/span> =<\/span> IP_Location_Block<\/span>::<\/span>get_option<\/span>();<\/span>\n        $geo<\/span> =<\/span> IP_Location_Block<\/span>::<\/span>get_geolocation<\/span>();<\/span>\n\n        \/\/ return alternative content when the contry code IS NOT in the white list\n<\/span>        if<\/span> (<\/span> FALSE<\/span> ===<\/span> strpos<\/span>(<\/span> $settings<\/span>[<\/span>'public'<\/span>][<\/span>'white_list'<\/span>],<\/span> $geo<\/span>[<\/span>'code'<\/span>]<\/span> )<\/span> )<\/span> {<\/span>\n\n            \/\/ set alternative content for not whilelisted countries\n<\/span>            extract<\/span>(<\/span> shortcode_atts<\/span>(<\/span> array<\/span>(<\/span>\n                'alt'<\/span> =><\/span> \"<p>Sorry, but you can't access this content.<\/p>\"<\/span>,<\/span>\n            ),<\/span> $args<\/span> )<\/span> );<\/span>\n\n            return<\/span> wp_kses_post<\/span>(<\/span> $alt<\/span> );<\/span>\n        }<\/span>\n\n        \/\/ return content when the contry code IS in the white list\n<\/span>        return<\/span> $content<\/span>;<\/span>\n    }<\/span>\n\n    add_shortcode<\/span>(<\/span> 'ip-location-block'<\/span>,<\/span> 'my_filter_content'<\/span> );<\/span>\n}<\/span><\/code><\/pre>\n<\/figure>\n
The usage of the shortcode [ip-location-block]<\/code> is as follows:<\/p>\n
\n
[<\/span>ip-location-block alt=\"<img src='\/image\/alternative.png' alt='This content is not allowed in your country.'>\"<\/span>]<\/span>\n\n<p>This is a content for whitelisted countries.<\/p><\/span>\n\n[<\/span>\/ip-location-block<\/span>]<\/span><\/code><\/pre>\n<\/figure>\n
And there\u2019s a tweak to keep the whitelist or blacklist of country code in \u201cFront-end target settings<\/strong>\u201d. You need 2 steps to do this:<\/p>\n
    \n
  1. Check \u201cBlock by country<\/strong>\u201d and specify the others. Then \u201cSave Changes<\/strong>\u201d.<\/li>\n
  2. Uncheck \u201cBlock by country<\/strong>\u201d and \u201cSave Changes<\/strong>\u201d once again.<\/li>\n<\/ol>\n
    \"Front-end<\/p>\n
    Have fun \ud83d\ude04
    <\/span><\/p>\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    I started to develop IP Location Block as a security purpose plugin so as to protect the back-end of the site. And since version 3.0.0, it has been equipped with the functionality of front-end protection based on this suggestion at the support forum. This helped to greatly improve the protection ability of this plugin against […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-34","post","type-post","status-publish","format-standard","hentry","category-general"],"_links":{"self":[{"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/posts\/34","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/comments?post=34"}],"version-history":[{"count":6,"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/posts\/34\/revisions"}],"predecessor-version":[{"id":508,"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/posts\/34\/revisions\/508"}],"wp:attachment":[{"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/media?parent=34"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/categories?post=34"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/iplocationblock.com\/wp-json\/wp\/v2\/tags?post=34"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}