moody1337

Awesome, thanks a lot!

Hey Mateusz,

thanks for getting back that quickly – I’m aware of the benefits also of using webp and with this approach it might the best out of best solution.

but still, if somebody – like me – wants to go with “you can get the absolute best with avif or you stick with the mainstream-formats jpg / png while using a not so cool browser”, any chance to convert only to avif and skip the webp-conversion?

Hey Torsten,

yeah, already thought about switching the language, but maybe there are also non-germans outside with the same problem and want to follow our small discussion ??

You are right, I never counted the characters and just looked at same. But as wordpress does not use a monospace-font it was just … dumb from my side.

Good idea with the user-agent! I changed the server-config and at least my tests looked good. Will see if the spam-comments are stopped by it.

Thanks for your help and of course the great discussion ??

Hey Torsten,

thanks for getting back that quick ?? I sent a few seconds ago the form filled out as good as I could (was not sure about the user-agent, hope it’s the “comment-agent”)

Also, important to say: I’m not really a developer, it’s more like that I tried to read some parts of the plugins-code, stumbling through the support-forum, try to understand a bit and adapt it.

Now to your questions:

Regex I tried out

I thought maybe I can extend the host-part in

array(
				'host' => '^(www\.)?fkbook\.co\.uk$|^(www\.)?nsru\.net$|^(www\.)?goo\.gl$|^(www\.)?bit\.ly$',
			),

for example with adding some of the following

|^(http|https)(\:\/\/)(www)*(\w+){1}$

|^(http|https)(\:\/\/)(www)*(\[a-z0-1]+){1}$

Worth to mention: whenever I have to do something with regex, I use https://regexr.com/. To test it before implementing it, I tested it with

1. https://test (should be matched to the regex-expression and so marked as spam)
2. https://test (should be matched to the regex-expression and so marks as spam)
3. https://www.test.de (should not be matched to the regex-expression and so not be marked as spam)
4. https://test.de (should not be matched to the regex-expression and so not be marked as spam)

Somehow the regex-expressions are working, but they also mark comments as spam when they are like example 3 and 4 – so in the end, they are not working or let’s say “they work too good” and mark more than they should.

I also tried the same regex-expressions as an additional array, e.g.

array(
				'rawurl' => '^(http|https)(\:\/\/)(www)*(\w+){1}$',
			),

Your example at github

If I’m not wrong, the curly brackets and the number within it means “exactly the amount of the number in the brackets” – which means: if the body exists only of one word with a length of 30 characters, its working, but with more or less than the 30 characters, it fails and so it’s not marked as spam.

Gravatars

I disabled Gravatars completly because of GDPR-reasons (you know, the stupid german data-protection law … was at least for me the easiest thing to just get rid of it)

“Use regular expressions”

Yes, I do (double-checked it, just to be sure) ??

Some more thoughts from my side

For me, it seems the common pattern is always the strange looking URL. They don’t have any subdomain mentioned and also no dot and a TLD at the end – could be a good startpoint for some solution for which I’m too dumb to figure the implementation out. Additionally or another point to start might be the comment-body – its always just one gibberish word, but at least quite long (but still not always the same length).

Sounds awesome ??

Btw: I found out, your plugin is not compatible with the plugin “AMP for WP – Accelerated Mobile Pages” and interrupts the loading of their settings-page – you can find my complaints (I did it at theirs end) here: https://www.ads-software.com/support/topic/settings-not-loading-3/#post-12481190

I’m not sure what directly causes the issue but when I deactivate Meow Analytics, their settings-page is loading again.

Here you go: https://www.wihel.de/wp-content/uploads/2020/02/Bildschirmfoto-2020-02-26-um-08.39.04.png

URL where I got it: https://www.wihel.de/wp-admin/admin.php?page=amp_options&tab=2

I’ll try my very best ??

I asume we are talking about “Google Analytics Dashboard for WP” for the guys who fucked it totally up by releasing the new version. So far I just reverted to a previous version to have – as told – some kind of quick view for the current day.

As screenshot maybe this is helpful: https://www.wihel.de/wp-content/uploads/2020/02/Bildschirmfoto-2020-02-26-um-08.04.41.png

Its basically the same view your plugin provides, but with a breakdown to the current day.

So when I’m not totally wrong, your are showing the last 6 or 7 days (my dashboard is currently showing statistics from 19th of february up to 25th of february) and in the end it should show something like starting from 0am up to the last hour or how the other guys did -> showing the x-axis already for the full day (0am up to 11:59pm) but only numbers which are already existing (I’m not sure how the do it, but I can always see some numbers for the current hour which are updated until the current hour is “over).

Not sure, if this was understandable, but from a user-perspective and with as many less words as possible: exchange the dates in the current view with hours, limit it to the current day and … done ??

• This reply was modified 5 years ago by moody1337.

Sure, I just updated this morning to 1.0.30 ?? And maybe helpful, the WP-version is 5.3.2

@tigroumeow this was the perfect hint, thanks a lot ?? Looks like basically I was just dumb and missed to also activate the Analytics-API in the library-section …

Dear Jordy,

I have the same issue like the two people before raised: connected the plugin to Google (so I can see the client-id and the client-secret and la la la) but going back to the wordpress-dashboard, no data is shown.

But the console shows

Failed to load resource: the server responded with a status of 403 ()

for https://content.googleapis.com/analytics/v3/management/accounts and clicking on this link just shows a page telling me

{"error":{"errors":[{"domain":"global","reason":"required","message":"Login Required","locationType":"header","location":"Authorization"}],"code":401,"message":"Login Required"}}

Can you help?

• This reply was modified 5 years ago by moody1337.

Awesome, already updated and looks like its working again perfectly.

Thank you

Just change the whole function to:

function urlencodefix($url){
	//TODO: Remove/fix this. Probably not a good idea to "fix" invalid URLs like that.
	return preg_replace_callback(
		'|[^a-z0-9\+\-\/\\#:.,;=?!&%@()$\|*~_]|i',
		function ($str) {
			return rawurlencode($str[0]);
		},
		$url);
}

Just change the whole function to:

function urlencodefix($url){
	//TODO: Remove/fix this. Probably not a good idea to "fix" invalid URLs like that.
	return preg_replace_callback(
		'|[^a-z0-9\+\-\/\\#:.,;=?!&%@()$\|*~_]|i',
		function ($str) {
			return rawurlencode($str[0]);
		},
		$url);
}

For me its working again, no error-messages after update ??

Got the same problem. Also with adding

allow_url_fopen = On
allow_url_include = On

to the server-config the error isn’t gone.

• This reply was modified 6 years, 10 months ago by moody1337.