Raul P.

Looks like there was a missing file on the phpminify update.

Hi,

A few things:

Maybe unrelated, but always the first step to ensure everything is in order.

You seem to be running wp 7 with fvm just fine now.
Plugin is compatible. But you are also using WP Optimize, so ensure that no settings are doing minification on that plugin, and that cache is purged after FVM, not before.

I suggest going to fvm settings and resave.
Then from the top admin menu, FVM> Clear Everything
Followed by WP Optimize cache purge.

If your server also does server caching, that needs to be purged as well.

—

Regarding the metadata, it did not disappear.
It was prioritized. It went up on the page, and because FVM process these things in stages, the comments were left behind.

I checked 57 fields from that block, including the article tags and JSON-LD schema and none are missing.
They are just moved up into the compressed head around line 5. The AIOSEO comments remain lower down, so the block looks empty. It’s just being optimized, and that behaviour didn’t change.

You can enable the Strip HTML Comments, Cleanup Header and the recommended settings on FVM, and those comments should disappear as intended. You don’t need comments in HTML, thats for debug purposes only.

Will send a quick update for the compatibility check soon.

Hi, that depends.
This plugin is not a install and forget, you need to manually optimize scripts.

First thing you need to check, is if the frontend in incognito mode, when you view source, does it show any files pointing to the cache directory, minified? Or do they show on gtmetrix?

By default, at least the CSS files should be automatically optimized.

If they are not showing up, means there is some error (check the footer, if any html comment shows up).

Sometimes there is server or hosting cache as well, so you may not be seeing the fresh optimized page.

Can you share your url or gtmetrix report ?
Is there zero difference, or just small?

Note that sometimes, the site is just too heavy that even with optimization, it can fall short.

Hi there,

Sorry to hear about that.

That logic was intended for SSRF Protection, but there was a bug in order of execution so it got blocked before actually processing local files.

Furthermore, considering that people might use this on intranet or have resources over NAT.
But more importantly, WordPress itself does not perform IP-based filtering in wp_remote_get().

I thought it was a good idea for security, but thinking back, if someone can inject arbitrary URLs into wp_enqueue_script(), they likely already have enough access to do worse things, so it makes sense if I remove this check.

Update will follow shortly.

Thanks for reporting.

Hi, thanks for reporting. This should be fixed on 3.5.0 now.

Hi, that sounds like page caching (cache plugin, or server side), or maybe file permissions, not the logic on the plugin.

If you run 3.4.1 and delete the cache on FVM from the plugin a few times, does it still work when you go and check on incognito mode and refresh a couple of times?

Because that sort of behavior happens usually when there is some sort of page caching active somewhere, which FVM cannot clear.

When minification is generated, it needs to purge the html page cache so that it generates a new file pointing to the correct minified files.

If it’s server side caching (a lot of providers have this to speed up loading times) it might store the page for a few minutes anytime, either before, after or during FVM creating those files. That would result in inconsistent view, because cache would be pointing to files that might not exist anymore (fvm cache purged, without purging the page cache from server or other plugin), or point to a cached page before FVM generated the files.

Normally, ensuring any page cache is disabled or trying in development mode, staging, etc should show if it works or not.

From 3.4.1 to 3.4.3 the differences are really minimal, essentially a not null check and wp cron check, which would not cause this behaviour.

Sorry about that, there was a typo. You should be able to update to 3.4.3 now.

Hi, there were no changes that would require an update, so that is why. I will consider an update soon, just for the sake of the version notification.