Tim Eckel

Also, the the Minify HTML plugin does nothing if you’re an admin. This code in the plugin will only allow MinifyHTML’s functions to run if the user is not an admin:

if?(?!is_admin()?)

Maybe I don’t understand what to be looking for in step 6. Not sure what classic block is. When I save the draft, it looks exactly the same as it did before I saved it. When I exit the post and edit it, it looks the same.

What should I be looking for that’s changing? As I don’t see anything different.

I can’t duplicate your issue. The Minify HTML plugin already checks is_admin() and doesn’t run minification if the user is an admin (which should be anytime in the admin console). I’m testing with WordPress v6.4.1, so it’s possible a fix corrected the problem. I do see a bug fixed in v6.4.1 having to do with wp_admin_notice(), which is_admin() may rely on. If you’re not running v6.4.1, I would give it a try as that could be the issue.

The problem is that you’re using an HTML coding style where you’re using carriage returns as padding, which is ambitious and doesn’t accommodate minification. Many other cases will have the same result after minification, not just anchor tags. I would do something like this:

<span class=”link-list”>
<a>Art</a>
<a>Food</a>
<a>Music</a>
</span>

And then use link-list to style the spacing with something like margin-right:1em

This only fixes your unique problem, it’s incorrect in other situations and there’s others which wouldn’t work.

The problem is with how your creating the HTML. You’re using carriage returns as white space. Instead, you should be doing this one of two ways. One, adding a ;nbsp between the links, or two, adding CSS to add a space. Changing this plugin doesn’t really resolve anything, other than your unique HTML situation.

No, this plug-in does not create any kind of notification. It simply defaults all new reviews to pending instead of active. If there’s a new review notidlfication, it would require WooCommerce or another plug-in to accomplish this.

@poonasor Good catch! The problem wasn’t the order, it’s that the comment ended with a comma. The plugin has been updated to v2.1.9 which corrects this problem.

Sounds like there some kind of conflict between Matomo and MinifyHTML. All kinds of things could be causing it, including both libraries trying to access the same buffering cache.

I dont use Matomo so I won’t be able to diagnose the conflict. Probaby best to not use one library or the other.

What happens when you enable the plugin, but disable all of the settings for the plugin? Also, your link doesn’t work.

My guess, is that Simply Static is rendering the pages on the back-end to create the static pages. Because it never actually initiates the WordPress hook to send the page to the browser, the Minify HTML is never triggered.

Minify HTML does its magic by minimizing the output buffer right before sending to the browser. Simply Static probably never gets that far when generating the static pages. It would appear Simply Static basically never allows Minify HTML to ever run.

there’s are many online services that will “beautify” HTML or CSS.

I’ve never used block patterns, and this is the first time anyone has reported an issue, so leaving it on by default seems okay for now. Maybe someone will change block patterns to use something better than HTML comments as a trigger. And it’s as simple as turning off comment minification until such time, so I see no need to change the default behavior.

It seems block patterns and Minify HTML are using the same hooks, which is why it’s not working. The only solution is to disable comment minification untill a more modern method is used with block patterns, as using HTML comments like they’re doing is really amature hour programming.

Minification must happen on the back-end as it would lose most of its usefulness if done on the front end. Minify HTML provides controls so you can disable certain minifications if it causes a conflict with something specific on your website. I’ve never used a site with block pattern comments, so I’ve never had this situation. But the switch is there in case you have the exact problem you’re experiencing.

It’s possible that a work-around could be found, but I’d need example HTML output of these block pattern comments as I don’t use that feature to know what they look like.

But in any case, disabling the comment minification is the solution, and how the plugin was designed to be used.

There’s an over-zealous group which is profiting on reporting plugins for trivial potential security “issues”. In any case, the plugins has been updated to address this issue. If you’re using the latest version of Minify HTML (v2.1.8), the issue has been resolved. If it’s still reporting a problem, it’s a false-positive at this point as they haven’t updated their system yet that the latest release resolves the problem. You may be able to contact word fence and have them update their database.

• This reply was modified 1 year, 11 months ago by Tim Eckel.