nudnavda

Hi Danny, I’m afraid I’ve been premature in my enthousisam.
Things don’t work out the way we intended, it seems:

1 – I adjusted the IP-address in the script (see above).
2 – Installed the code in my regular Snippets plugin, and activated it.
3 – Activated on my desktop Proton VP to change IP address
4 – Purged caches (WP admin, local Chrome)
5 – Public version of Koko-analytics appears in Chrome (in stead of homepage).

Now, I don’t know if you want to further investigate.
If so, I can mail you a screenshot of the Koko settings, showing the two different IP addresses: the one excluded from analysing, and the actual Vpn address.

Please let me know.
Thanks and greetings,
ad

Hi Danny,

sorry for continuing this thread – I think it is indeed related to my initial question.
And the plugins I found did not help in this specific case.
I’ll try to explain.

Koko uses an url for standalone view: https://YOUR-DOMAIN/?koko-analytics-dashboard=1
This is a useful option which can be viewed (or not) publicly.
It would be nice to have an option to restrict the viewing to my own IP-address.
So my question was: would this be possible?

On Stackexchange I found the following code (but I’m afraid it only works for pages, not for a query like your settings page url):

function page_ip_restriction() {
    if(is_page('yourpage'))
    {
        // Whitelist
        $whitelist = array(
            'x.x.x.x',
        );

        // Check if current user IP is out of the whitelist, then redirect to home
        if(!in_array($_SERVER['REMOTE_ADDR'], $whitelist))
        {
            wp_redirect(home_url(), 403); // 403 -> Forbiden access
            exit();
        }
    }
}
add_action('init', 'page_ip_restriction', 10);

Maybe this illustrates what I’m looking for.
Hope it’s not too much of a hassle ;-(
Thanks again!

Hi Peter,
just a message to ask if you could extract any useful information from the diagnostic or if it’s still being investigated?
This could be quite relevant for the GP-developpers.
Kind regards.

Great – thanks for the direct reply!
Best wishes,
ad

Thanks so much, Sybre, for your support!
I integrated your filter on the site, so the comments-message has been cleared.
Then, I concentrated on delivering a working rss-link – which for most rss- and podcast-readers should be fine now, I hope 😉

I really appreciate your help!
All the best,
ad

Listen, Deepak,, I find this annoying, quite frankly: you make this unnecessarily complicating.
I gave you my feedback as a potential, moderately experienced client who indicates a substantial objection against your inbuilt procedure for installing this plugin.

Don’t ask me to sharpen and refine my reading abilities – just prevent me from getting into troubles. Simply put: make your intentions and its possible consequences MUCH clearer, please. Insert a button, add a ribbon: warn me!

Hope this helps 😉
Thanks.

Thanks for reminding me 😉