Conflict with Advanced Custom Fields (Repeater Fields)

Hi, can you please provide a screenshot before/after enabling FVM, as well as the exact url and location where that issue happens?

The Advanced Custom Field plugin, usually doesn’t matter for the frontend. You create those fields on wp-admin (FVM doesn’t do anything about the backend) and then code your page to show those fields.

I see an invalid image on https://staging.uniqueteambuilding.com.au/case-studies/full-day-team-builds/ but this is already part of the code <img src="3" class="img-thumbnail" alt="Case Study"/>

Let me know exactly where to look as I don’t see other issues with it, thank you.

Hi Raul,

Thanks so much for this! I apologise for the shallow explanation:

The issue is with the prev/next navigation of the hero slider (at the top of every page) and the repeater fields (at the bottom of every page).

Here is the hero slider https://i.postimg.cc/QdjHS7mS/Capture-1331.png – these prev/next controls should be arrows at each side of the slider. Please see https://www.uniqueteambuilding.com.au for how it looks without FMV enabled.

As for the repeater fields here is a screenshot https://i.postimg.cc/mgW6nL1m/Capture-1354.png – again please see https://www.uniqueteambuilding.com.au for how it looks without FMV enabled.

Hope this clarifies everything! Let me know if not.

As for the invalid image, I did not actually notice that – thanks for pointing it out.

All the best,
Aidan

Your css code is not specific enough for merging. The image path is correct on the minified file, it just doesn’t apply because other rules overwrite or get ignored later.

In the case of the footer, left is the rules that apply when minified, and right is the rules when you are not merging css. Note some css rules do not apply, as they get rewritten somewhere else, or the last rules that were supposed to add those extra rules are not specific enough and thus get ignored.
https://i.imgur.com/CNlyNU7.png

When you merge css files you need specificity.
https://www.smashingmagazine.com/2007/07/css-specificity-things-you-should-know/

You need to exclude the following files from merging and minification:
/wp-content/themes/utb/assets/css/jquery.bxslider.css

When css files load separately, duplicate rules overwrite the previous. When you merge, duplicate rules get ignored or only one of them apply, depending on specificity.

But you may want to wait a couple of days as I am deprecating merging css and js files for the next update, as merging is no longer recommended for HTTP/2 servers. If the files load separately, likely the issues will be sorted out naturally.

Hello,

Thanks again for the quick & detailed reply! Very helpful!

That does all make sense but is quite complex for me. I have tried to fix this with your resources, but not able to yet. I will, as you say, wait a couple of days and see what happens. Thank you muchly for this.

I guess the most interesting part of this is how this issue still prevails while all the processing settings are disabled, but the issue disappears when FVM is disabled.

All the best,
Aidan

But you may want to wait a couple of days as I am deprecating merging css and js files for the next update, as merging is no longer recommended for HTTP/2 servers. If the files load separately, likely the issues will be sorted out naturally.

Raul P.
It will be very interesting.
I’m looking forward to the update.

Hi, the latest update came out today, sorry the delay.
It should work fine, provided you keep merging disabled and use only minification.
Else, you need to debug and try other configuration manually.

Please check the HELP tab for instructions on the plugin and try the latest update.

Raul,
Thank you so much for the new 3.1.5 release!
It was PSI 97/100, and now it’s 99/100 !!!
—-
I do not use FVM minification because I have all min CSS files
Good luck!

Hi Raul,

Thanks very much for this!

Unfortunately, this update has not helped with my error – so (as you say) I will go for debugging & manually try other configurations. Could you suggest how best to start with this?

And you obviously mentioned before about merging files being deprecated and no longer recommended anymore. This is news to me actually, I must have missed that on first read. Do you have any links to resources about this? Would love to read-up about this, I have spent a lot of time trying to combine all these files… Oh well!

Thanks again for all this!

All the best.

Combining CSS and JS files is deprecated for http2 enabled servers only.
I suggest googling about that, ie: https://dev.to/nitinja/http-2-as-web-developer-what-you-need-to-change-3jb3

On the next update I have added a few fixes for fonts and image file paths.
You can try the next version 3.1.8 soon, or try to use the ignore list until you find which file get’s affected.

I already listed which file appears to be causing it, but it could be some other css file. In that case, you need to try one by one.

Hi Raul,

I have fallen a bit behind on all this – but in all these updates being rolled out this issue has now been resolved just from these updates! Thanks very much.