Roy Tanck

Fair enough. Still, the best way to add the code you suggested would be to roll your own little plugin. Basically, mine exists to save you the trouble :).

It contains a slightly fancier version of the approach in the snippet, and does nothing else.

Thank you for suggesting this. Unfortunately, the snippet you posted does not preserve any (non-FLoC-related) values the header may have. This could lead to issues on sites where the Permissions-Policy header is already in use to control other permissions.

My plugin preserves those values if present, and then adds the “interest-cohort=()”.

Also, functions.php gets overwritten when your theme is updated, so in general it’s not the best option to add your own code there.

I’d say both are not ideal, but I’ll add this to my to do list. Perhaps we can tweak the way our plugin sorts so it matched with WP’s results.

Well, the link is not required, so technically this is not an issue.

Thank you for reporting this. It looks like these three plugins indeed do not supply a “plugin url” in their readme files. Obviously, Plugin Report can only display information it has access to.

Thank you for reporting this. By default, the list should be sorted alphabetically, just like on the Plugins screen. What differences are you seeing?

In Plugin Report, we’re using a javascript sorting mechanism that lets you sort based on a number of columns. Because this is not the same code as WP uses, small differences are probably to be expected.

I hope you find a solution, but for now I’m going to assume this is not caused by Plugin Report.

Hmm, after updating the translation files in my WP install through wp-admin/update-core.php I no longer see any English strings.

Are you seeing untranslated string in other plugins and/or WP core as well?

Thanks for testing!

Thank you @nekojonez for reporting this. I’ve just released a new version (1.8.3) that should fix this issue. You may need to click “Clear cached plugin data and reload” to refresh the data.

Thank you for your kind words. Very glad you found it useful. An excellent year to you too!

Thanks for reporting this. Can you check whether the environment type is set in your staging site’s wp-config.php file?

This plugin requires the environment type to be set using the constant introduced in WordPress 5.5.

New wp_get_environment_type() function in WordPress 5.5

Thanks for testing! I’ll merge this into a new version later this week.

If you could try this feature branch from Github, that would be wonderful. It appears to fix the issue for the “code-snippets” plugin, and the I’m confident the approach is generic enough to deal with other similar issues as well.

https://github.com/roytanck/rt-plugin-report/tree/fix/ignore-minor-wp-versions

@pomegranate Can you point me towards a plugin that exhibits this behavior? I’m having trouble reproducing the issue. Thank you.