robmeerwijk

Resolved! It was caused by a setting in DIVI theme. WordPress was stuck on en_US. Couldn’t switch it, until I disabled “disable translations” in DIVI | Theme Options | General Settings.

I was a great fan of WordPress. I don’t understand how the wordpress release leaders have missed the score on the gutenberg plugin. Over 2.000 reviewers and 2 stars on average, only.

Mind you, those people were willing to try gutenberg before it was a part of 5.0.2

How can wordpress development continue in a dead end street without noticing something is definitely wrong?

And it has been said before, the classic editor plugin was downloaded over a million times in 2 weeks.

On the website it is stated that this release of gutenberg is the first phase of a complete makeover of wordpress. This is a horrific scenario. I will never upgrade wordpress again! And I will start looking for a drupall migration tool.

Hi, thank you for the advice. I have disabled all plugin’s and that made the problem dissappear. Then I reactivated all plugins and the problem stayed away. Pretty strange to me: magically resolved!

Rob Meerwijk

Hi Pankaj,

Could you make the cover image centered?

Thanks,

Rob

Thanks, it works. I clearly missed the point of “!important”. My only excuse is the time of night ??

Great plugin, anyway!

Rpb Meerwijk

On 1.0.8 it works automatically. Just switch it on in Jetpack.

I tried 1.10. Same problem. I restored 1.08 from backup.

Sorry to bother, they keep trying non-existing link ()302, therefore no inlog in WP, therefore no entry in auth.log, therefore no block ??

I will set a firewall rule myself for this fellow. Or maybe better, a rewrite rule to my actual login, so that fail2ban can help me for next cases

Thanks for the great work!

Hi, my installation stopped working after upgrading to 4.0.1

Restarting fail2ban and reactivating the plugin did not work. No messages in /var/log/auth.log And I am under attack at the moment:

meerwijk.dk:80 217.73.227.21 – – [22/Nov/2014:09:47:51 +0100] “POST /wp-login.php HTTP/1.0” 302 459 “-” “-“
meerwijk.dk:80 217.73.227.21 – – [22/Nov/2014:09:47:52 +0100] “POST /wp-login.php HTTP/1.0” 302 459 “-” “-“
meerwijk.dk:80 217.73.227.21 – – [22/Nov/2014:09:47:52 +0100] “POST /wp-login.php HTTP/1.0” 302 459 “-” “-“
meerwijk.dk:80 217.73.227.21 – – [22/Nov/2014:09:47:53 +0100] “POST /wp-login.php HTTP/1.0” 302 459 “-” “-“

Any clues?

Hi, it is not only on comments, unfortunately. The same happens with embedded pictures such as ipv6 test.

The code looks like:

<img title=”ipv6 test” src=”https://v4v6.ipv6-test.com/imgtest.php?bl=1&#8243; alt=”ipv6 test” border=”0″ />

And the image becomes full width. I hope you can do something about it, cause I like your theme very much!

For now I have scaled the smiley back using

.comment-content img, .widget img {
max-width: 14px;
}

Only images in comments are smiley’s!

More or less the sames happens with my jetpack “google-plus” link. It gets pretty wide on the bottom of my posts.

Count me in for this feature!

Hi, it is not an images, it is typed as :-D, and that is interpreted bij WP as an image, which gets scaled to 100% by the theme css. At least, that is my guess.

Look at: https://www.meerwijk.dk/9-misverstanden-artikel-430a/

Solved as far as I am concerned