Tim Eckel

Oh, and the issue is resolved as there’s options in the plugin to set features that will resolve the problem. In other words, the solution doesn’t need code to be changed, you just need to click a couple boxes on your end. Not every problem requires a software fix, sometimes it’s operator error or operator education.

Okay, then turn off the switch for protocol and domain.

The plugin can’t solve every unique situation. Instead, I’ve created settings which allow you to enable or disable certain features. In this case, turning off relative domains and/or protocol schemes should resolve the problem.

There are switches because some features won’t work for everyone. Most people don’t need to use canonical links (I never have) and those that do are typically on a different domain, in which case the domain won’t be removed. It’s rare and quite odd that you would have a canonical link to the same domain.

Sorry if this doesn’t work out perfectly for you, there’s probably another minify plugins that will accommodate you. One of the goals of Minify HTML is to be fast, lightweight, and not use bloated libraries. Trying to accommodate this unique case is outside the scope of the plugin.

You may want to consider doing 301 redirects instead, as that’s what I’ve done for the hundreds of websites I’ve been a part of. Best of luck!

What’s the problem with minifying JS ads?

I don’t follow you. There’s a switch in Minify HTML to convert improper XHTML to HTML. If you want to keep the improper XHTML, simply turn off the switch. This has nothing to do with canonical links, it’s the self-closing tags that are not required with the HTML doc type.

If this doesn’t help, please explain in detail what the issue is once you turn off the setting in Minify HTML that removes the self-closing tags in HTML.

Thanks!

With doctype HTML, you don’t use closing tags with void elements (self-closing tags). For example, in a link tag you would not add a /> at the end. That’s XHTML, not HTML. With a doctype of HTML, it’s WRONG to add the closing tags on void elements. Sure, it works, but it’s technically not correct and unneeded.

For this reason, there’s even a setting in Minify HTML that removes the closing tags from self-closing tags. This saves 2 characters each time it’s done.

If, however, you really want to be incorrect and use XHTML in HTML doctypes, you can turn off the switch in Minify HTML and it won’t touch your closing tags on self-closing tags.

It wouldn’t surprise me at all if WordPress adds closing tags to self-closing tags when doing a wp_head(). Just because WordPress is doing it, doesn’t mean they know what they’re doing or it’s right.

There’s a switch in the plugin to not minify inline JavaScript. Just turn this off and all JavaScript code won’t be minified.

Adding the trailing slash is xHTML, not HTML5. Are you really generating xHTML?

I believe you’re not understanding what I’m trying to say.

Basically, Minify HTML is removing white space. But, the plugin you’re using uses white space. You can’t have it both ways. If you want to minify and remove white space, you won’t be able to use a plugin that relies on it (which isn’t a good idea).

What I’m saying is that the tag cloud plugin you’re using should be modified to work without needing white space, that seems wrong.

This is because whatever you’re using is using line feeds to divide objects, which typically isn’t done. This is a unique case with whatever tag cloud you’re using. Minify HTML is designed to remove white space so it won’t work if your site relies on white space to remain.

“Remove relative domain from internal URLs” is a switch because of conflicts like this. The solution is to turn that option off. Something the Disqus Conditional Load plugin is doing is tripping up Minify HTML.

You would need to customize the plugin to do that. But, I’d suggest just disabling the “Remove relative domain from internal URLs” feature as that’s what it’s designed to do.

Closed

The plugin works just fine, even with the latest version of WordPress v4.9.2 as stated on the plugin page. You are trying to do this for blog posts, correct? Excerpts in WordPress only work for posts, not pages. Here’s proof that it works with the latest release:

https://www.renegadelife.org/category/news/

There are some themes that allow some overriding control over excerpts. For example, the theme on the above website (extension of the Sydney theme) has options in theme customization that forces the entire post to be shown. If these options are turned on, it overrides all excerpt rules including the Read More Excerpt Link plugin. While uncommon, check your theme’s customization to see if there’s any settings having to do with content length or excerpts.

Sadly, there are some themes that build their own excerpt function rather than correctly extend the built-in excerpt function. Basically, there’s a hook in WordPress that can be used to correctly extend the excerpt functionality, and that’s how Read More Excerpt Link works. However, if your theme doesn’t adhere to this WordPress standard, there’s no way Read More Excerpt Link can work as the theme has bypassed the standard method and used a custom and improper implementation. This would tell you that your theme is a little half-baked and the designer didn’t know what they were doing.

Hope this helps! Let me know if you have any questions.

This is a very specific issue. I’d probably need to see it first-hand to resolve as I’ve never done anything like you’re doing. If you make changes to the plug to address it, I’d be more that willing to integrate your changes into the source.

I don’t exactly follow what the problem is, could it be that just removing the “Content-Length” line would resolve the problem?

Minify HTML only minifies HTML web pages, not file uploads. It shouldn’t cause any issues with uploading. But, I don’t fully follow what you’re doing from this piece of code.