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.
Thread Starter
HKP
(@hiskingdomprophecy)
@alignak Hi Paul,
Thanks indeed for your speedy and detailed reply. Much appreciated!
Yes, FVM is working well, however, I confess I am not so familiar with viewing view-source:https… for a cached page, as all I ever look at are uncached. 🙂
So when I checked a cached page source code on the same day as the WP7.0 update, I got a bit concerned, even though all was working as it looked odd and unfamiliar.
I have been using FVM for a very long time now, as it allows me the control I need for my settings, as all my Theme CSS and JS (Weaver Xtreme) are already minimized, so need to be excluded from a second minimization, or else they will not render correctly.
I appreciate your point on WP Optimize, which I’ve used for years with FVM, simply because WP Optimize has no settings! I found long ago that most Cache plugins are too complicated for me to figure out, but the FVM & WP Optimize combination is perfect for me.
Regarding the FVM option to fix HTML. I use “Strip HTML Comments | Cleanup Headers | Remove Emoji” but I cannot use the “Enable HTML Processing” as it stops my “Extra Sentence Space” plugin from working.
The Extra Sentence Space plugin adds a space after an end of sentence period, which the HTML Processing removes…. It took me a long time working with Claude AI to figure that out! So though the page code may not look as nice as it once did, and perhaps slows the site my a few milliseconds, overall the site is more readable and it loads faster now than before.
So when I checked a cached page source code on the same day as the WP7.0 update, I got a bit concerned, even though all was working.
I have been using FVM for a very long time now, as it allows me the control I need for my settings, as all my Theme CSS and JS (Weaver Xtreme) are already minimized, so need to be excluded from a second minimization, or else they will not render correctly.
I appreciate you point on WP Optimize, which I’ve used for years with FVM, because it has no settings. I found long ago that most Cache plugins are too complicated for me to figure out, but FVM & WP Optimize combination is perfect for me.
Regarding the FVM option to fix HTML, I use the “Strip HTML Comments | Cleanup Headers | Remove Emoji” but I cannot use the “Enable HTML Processing” as it stops my “Extra Sentence Space” plugin from working.
The Extra Sentence Space plugin adds a space after an end of sentence period, and which FVM HTML Processing removes….
It took me a long time working with Claude AI to figure that out! So though the page code may not look as nice as it once did, and perhaps slows the site my a few milliseconds, overall the site is more readable and it loads faster now than before. So a win-win for me… 🙂
Paul, again, thanks for your reply. Greatly appreciated!
Angus
Thread Starter
HKP
(@hiskingdomprophecy)
@alignak Hi Paul,
I have just updated FVM to Version 3.5.5 and all the page code now looks as expected. All AIOSE meta data is back in its expected place.
I’ll close this now as it is resolved.
Regards and thanks,
Angus
Thanks. With the update, I added some logic to preserve the correct order. Great that all works fine.