ralfkerkhoff

Hi Dinesh,
may i ask for an update?

Thanks
Ralf

I have sent you another mail with the file.

HI
it looks like your mailserver blocked my mail:

[email protected]

host gmail-smtp-in.l.google.com [64.233.166.26]

SMTP error from remote mail server after end of data:

552-5.7.0 This message was blocked because its content presents a potential

552-5.7.0 security issue. To review our message content and attachment content

Please let me know when you find the time to have a look -i will then re-enable wp-armour.
Due to claims of visitors i have de-activated it for now.

Hi Jordy,
sounds great – especially adding the field “keywords” ??

Hi,
i have exactly the same problem. Just purchased the extended version, tested a contact form and my own IP has getting blocked.

If there is a way to whitelist the own ip that would be cool.

Ralf

Hi,
yepp – that’s what I waslooking for ??

Hi Jan,

“delete all first party cookies after opt-out” did the trick.

Sorry for my late “thank you” – the flue has got me in the last days.

Ralf

Hi Jan,
one additional question:
After the visitor consents, a cookie is set with:
<script>
if (window.koko_analytics) window.koko_analytics.use_cookie = true;
</script>

Is there a way to delete the cookie if the user removes his consent via the privacy settings?
At the moment no visits are counted when the user removes his consent – but the cookie is still there.

Cheers
Ralf

Hi Jan,
i am looking forward for the new service template ??

I think the “problem” is that Koko does not record any hits when DNT is set. That is different from Statify (visits are counted with DNT set).

Without the addition to the themes function file no visits are counted when DNT is set – in this case there is no need to consent.

So, yes my solution is not 100% clean.

Ralf

Ah,
found it . it was not the cache setting. It was the delayed execution of Javascript setting.
For Koko Analytics there needs to be an eyclusion added:
/koko-analytics(.*)/

Then it works without problems.

I finally got it working.
For those who are interested here is how it works:

Create a service and add this code to “execute at optin:
<script>
if (window.koko_analytics) window.koko_analytics.use_cookie = true;
</script>

In the corresponding content blocker add this to blocked elements section:
*/koko-analytics/assets/dist/js/script.js*

Keep in mind that Koko does not record visits if the “don not track” option is set in the browser options.
It will not collect data even if the visitor consents in real cookie banner. To avoid this add the following to the functions.php of your theme:

add_filter('koko_analytics_honor_dnt', '__return_false');

add_action('wp_enqueue_scripts', function() {
    wp_add_inline_script('koko-analytics', 'window.koko_analytics.use_cookie = navigator.doNotTrack !== "1"', 'before');
});

Cheers
Ralf

Hi,
thanks for the reply. Not generating a webp makes sense if the result would be larger than the original ??

Hi Ionna,
no i do not have any other examples at the moment. I have stopped using the WEBP images because of the downgrade in quality.

It would be great if you could share the WEBP image you get after smart compression.
In the examples I provided there is a clearly visible difference.

Second question:
With my example imagify tells me that the image is already optimized and creates only the webp image.
At this point it makes me wonder that you are able to appy smart compression to the image – and i am not.

BR
Ralf

Hi Ionna,
here is the link with the example images:
https://drive.google.com/drive/folders/1ixpvQNjEMb9twwFzjrOe1PbPvNJjmGIU?usp=sharing

There is the original jpg – Imagify tells me it is already optimized.
Therefore there is no other ‘optimized’ jpg in the folder.

I you now compare the jpg and the webp images you will notice:
The webp is not as sharp as the jpg.
This imho minor.
But if you look at the sun on the right side, the difference in quality is very visible.

Cheers
Ralf