Steven Vachon

You might want to reread the plugin description ??

Fixed in v0.5.5

Interesting. I’ll look into it!

No, I just switched to Jetpack recently.

I think I may have scheduled the post, then updated it with a modification before it published; if that helps.

Hmm, not sure if I understand.

I wrote it on March 8 and scheduled it to publish on the 11th. I had Publicize enabled before the 8th.

Note: If you’d read the footer of my article, I’ve since updated it not to display the modified date if it’s older than the published date.

https://www.svachon.com/blog/seo-internal-link-shortcode-for-wordpress/

Awesome! Thanks!!

Okay, I figured it out; it needed to be in a custom Loop.

Would it be possible to modify this plugin to work outside the Loop? It’d be useful for those using WordPress as a back-end for desktop apps.

Heavily tested, but software is never perfect. It was tested with W3 Total Cache a while ago, but not recently. It should, however, if W3’s HTML minifier is disabled (it sucks, anyway).

Should be faster than .5s, but anyway, as stated in the FAQ, you should be using a caching plugin to prevent any slowdown.

I’ll keep it in mind for a future version when an admin panel is made available.

In the meantime, if you upgrade to v0.5.4.2, open up wp-html-compression.php and comment out lines 35, 36, 41–46. That will enable the plugin for the admin, but it will also minify the HTML, thereby slowing down each page load by a small fraction of a second.

Could be a strange issue that some WordPress installations have with the plugin. I don’t know why they do, but I’ve applied a simple workaround in v0.5.4 when/if it happens. Perhaps this fixes your issue?

Not overly important, but clean, nonetheless. Applied to v0.5.4

I can’t reproduce this error.

Fixed in v0.5.4

This was a weird error that only occured on a few servers, so it took a while for me to get to it.