Roy Tanck

For performance reasons, Plugin Report caches the information ot gathers about a plugin. You can use the “Clear cached plugin data and reload” link at the top of the page to force Plugin Report to fetch new data.

For its data, Plugin Report relies on a combination of the plugin’s bundled readme file, and information from the wp.org plugin repository. If either supplies information that is incorrect, that data will be shown.

It looks like this particular plugin is available in the repository, but has stopped or delayed publishing updates there. The last code commit was three months ago.

This can confuse Plugin Report, and there’s very little we can do about that.

@justaniceguy Thanks. I was a bit late this time with the update, but I just tested the plugin with WP 6.2 and updated the information accordingly.

I finally got around to fully testing the plugin with WP 6.1, and updates the version information. Should be fixed now.

Thank you for reminding me. I’ll schedule some time to test my plugins and update the “tested up tilo” info accordingly.

Are you experiencing any issues with Plugin Report and WP 6.1?

This happened on one of my clients’ website too. As a workaround, As a workaround, I selected only the ‘attachment’ post type, which is not really used on this particular site. This removed the unwanted share icons from other post types. Unfortunately, I don’t think it’s possible to unselect all post types.

Hi @rainer-r . I just released version 2.0.2, which should fix this issue, and has a couple of other fixes for potential similar PHP warnings.

You’re very welcome. Glad you enjoy the plugin.

@rainer-r Could you please upgrade to version 2.0.1 of the plugin to confirm if that fixes the issue for you? Thank you.

Thank you for reporting this. I’ll look into this asap.

Plugin Report aims to give you an overview of the “health” of your currently installed plugins. I feel that keeping track of “historical” changes is out of its scope.

If you’re looking to keep such a log, there are a number of excellent plugins for that. I like Simple History for instance.

As for notes on decisions like you describe, I’d probably tend to keep those somewhere outside of the site. Every plugin you install is a potential security risk, so info that’s just for you could just go in a document somewhere?

Thanks for your suggestion. Plugin installation and activation dates aren’t recorded by WordPress. The plugin you mention, once activated, does this by writing timestamps to the options table. If I would add this to Plugin Report, it’d initially have no data.

What are you using this data for? Activation date appears to be reset when a plugin is temporarily deactivated, which is often done to troubleshoot issues.

Hi @woutervddn. This plugin is not currently being actively developed. I’ve made the code available on Github (https://github.com/roytanck/WP-MQTT) and am happy to look at PRs.

I’m no longer using MQTT in any projects, and have taken my broker offline a while ago. This makes it harder to test against new WordPress versions. Releasing a new version on www.remarpro.com requires at least some testing to make sure it works with whatever is the current version of WP at that time.

Ideally, someone with a more active interest could take over development.

I’m not familiar with the inner workings of ‘aretheyflocingme’, but the result page of my checker literally contains the exact header it has detected. This allows you to check its contents.

In the plugin’s FAQ, I’ve also attempted to describe how to check using your browser’s developer tools. For your URL, I can see the header when a page is served “fresh”, but it’s missing when the page is served from W3 Total Cache’s cache.

This unfortunately is a known issue with many page caching plugins. They tend to modify the page’s headers. I’ve added support for WP Super Cache, but not for others.

It looks like my checker is getting served a fresh copy somehow, which in this case is slightly misleading.

Ah yes, thank you. Corrected for version 1.9.1 which also fixes another small issue.

I just released version 1.9 of the plugin with fixes to address this issue.