Will Stocks

Ahhhhh, OK – I’ll try the fresh install and will let you know!

Do you want me to fully reinstall the latest version? i.e. start fresh?

Basically:
– I had been using 1.2 for quite some time (probably 6 – 8 weeks) so had a few gravatars in the cache etc.
– Upgraded to 1.3.0 and saw the original errors
– Upgraded to 1.3.1 and saw the new errors

Nice, thanks! I’ll try to get that installed later this week! ??

Looking forward to the PHP 7.2/7.3 version!

I’ve deactivated the plugin for now – I’ll wait it out until you have a PHP 7.2 version ready ??

Thanks @jomisica ??

Don’t suppose you have a download link for the zip of 1.2.2 do you? ??

I’m guessing it’s something to do with a PHP 7.2 backwards incompatible change: https://php.net/manual/en/migration72.incompatible.php#migration72.incompatible.warn-on-non-countable-types

OK, so two of the errors are now gone, but I’m seeing:
Warning: count(): Parameter must be an array or an object that implements Countable in /WillStocks/wp-content/plugins/optimum-gravatar-cache/optimum-gravatar-cache.php on line 1283

Warning: array_merge(): Argument #1 is not an array in /WillStocks/wp-content/plugins/optimum-gravatar-cache/optimum-gravatar-cache.php on line 1284

Warning: count(): Parameter must be an array or an object that implements Countable in /WillStocks/wp-content/plugins/optimum-gravatar-cache/optimum-gravatar-cache.php on line 1287

Sorry – went to sleep! ??

Personally, I’ve always thought that providing constructive feedback/assistance is a useful thing – especially when the product is good/could be really good. It’s always useful to have an extra set of eyes on something as well ??

Yes, I was seeing the errors in production.

Just updating now!

WP 4.9.8
PHP 7.2.10

Almost there! That’s sorted the lockout issue, now though I’m seeing:
Warning: array_merge(): Argument #1 is not an array in /homepages/28/d644178550/htdocs/clickandbuilds/WillStocks/wp-content/plugins/optimum-gravatar-cache/optimum-gravatar-cache.php on line 1284

Warning: Invalid argument supplied for foreach() in /homepages/28/d644178550/htdocs/clickandbuilds/WillStocks/wp-content/plugins/optimum-gravatar-cache/optimum-gravatar-cache.php on line 1287

The plugin generated 221 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

You can also find my bug reported to the Yoast team, here: https://github.com/WordPress/gutenberg/issues/10315

Sorry @jerparx – I raised an issue on GitHub: https://github.com/Yoast/wordpress-seo/issues/11131

It does look like Yoast is breaking Gutenberg.

I have also raised a Gutenberg bug (Gutenbug anyone!?) to go along with my Yoast GitHub bug: https://github.com/WordPress/gutenberg/issues/10315

@deexperte – do you use Yoast per chance?

I raised an issue on Github (got a response there): https://github.com/WordPress/gutenberg/issues/10315

Ah, I don’t even get that! It’s just a plain white page with absolutely nothing on it :/

2 & 3 – Nice, thanks! 1 might not be something that’s useful/wanted by many people though to be honest…

1) It is something I found rather useful in WP Super Cache. In some cases, I had updated a minor bit of CSS (either via FTP or WP-Admin Editor), but the page that it primarily affected (example: contact form submit button placement on a contact form page) would still be serving up the cached version of that file. It may not be so much of an issue with Hummingbird, but it’s something I found quite useful a) to know the age of cached pages and b) being able to clear an individual page, not the entire page cache all at once.

It was also quite useful to see that “oh, all of these pages are cached, but not these two or three – I wonder why”, whereas at the moment all I can see if 67/83 pages cached.

Again, it’s one of those “I have updated a small element on my homepage, but I have to clear my ENTIRE page cache (which then has to be rebuilt manually, currently due to FR-2 as mentioned) rather than just the page that CSS change affects?

Just read through that post – all makes sense!

Hopefully jsDelivr usage starts to increase, so there’s a higher chance of users already having stuff cached ??