Meitar

MIME support for this was requested years ago but I never found the time or other resources to work on its implementation. You have three options: implement MIME support in the plugin, fix inline support in your client, or use a different client. That’s really all there is to it. Shrug?

Great, thanks. The next version of this plugin will pin the dependency to that version. There is no difference between that tag and the current deployed code, so this doesn’t yet warrant a plugin version increase.

Yeah, this is a known issue in the upstream library so supporting ECC is not a trivial ask at this time.

I’m also aware of the PHP 8.0 errors as reported earlier but again, I’m waiting on an upstream release in order to fix that. If you would like to help, nudging the upstream library maintainer to tag and release a new version so I can pull it in via my Composer set up, that would be helpful. Thanks.

Oh, that’s disappointing. 🙁 I’m now using the latest released version of the upstream library so if that error is still there we’ll have to wait until the upstream library cuts a new stable release with support for PHP 8.

This error indicates an upstream library is incompatible with the version of PHP you are using.

I’ll have to see if this has been fixed upstream and if so update the version of the library this plugin uses. Thanks for letting me know. Hopefully I can get a fix released in the next few days.

Only the original Admin has a PGP key field. Second Admin does not. Subscriber and Editor does not.

They do. Log in as them and see for yourself.

What warnings is your site generating? Post them here or file an issue report in the project’s issue tracker and I’ll have a look.

The reason I haven’t made any updates is because as far as I know the plugin doesn’t need any. If that’s no longer true, then I need users to tell me about the errors they’re encountering so that I can be aware of those issues. This is open source software, which means it’s everyone’s responsibility including the users of the software to do their part in maintaining it. That means you.

Oddly enough there was a plugin update available for the plugin moments ago and now it works correctly, so thanks for patching the issue.

Huh! This update wasn’t supposed to change any behavior. And it didn’t on my test sites. If you’re seeing new (and better/more expected) behavior after this update, that means my update here coincidentally fixed a bug I did not know existed and that has not been reported or at least not reported clearly enough to be isolated.

To be specific: the update streamlined a function called filterTags that was written years ago. Your post prompted me to update it so that it more closely followed the function signatures of the two WordPress core hooks it was designed to use. That process involved streamlining the function and removing some unnecessary (and buggy, apparently?) code.

Regardless, you have my apologies for probably incorrectly assuming the situation you encountered was the same as the many dozens of other people reported before today in this particular case. That said, I’d urge you to consider providing meaningful bug reports in the future and doing the legwork to at least demonstrate that you’re not just mindlessly repeating the claims of dozens upon dozens of others that are recorded here. You didn’t do that, and I’m not likely to change my approach to similar postings of yours in the future unless and until you change that initial behavior, first.

Finally, I’d be curious to have a look at your site to see what’s changed. Again, notably, you provided no links or other materials that would have given me any way to verify, test, or otherwise analyze any of the claims in your posts. Not even a link to your site, which is explicitly something that the instructions for filling out a support request on this forum asked you for. As you may know, you’re far more likely to get more help when you do provide some actually usable information.