ps – I have tried this one “keep the order” of css files” but it doesn’t fix the problem.
Neil
Hi there,
It could either be a css or js compatibility when merging, or minifying.
a) Disable js processing and try again. If it fixes it, you know it’s a js related problem.
b) Do the same for the css (only) if the above doesn’t fix it.
c) Once you know which section (css or js) broke the slider, try do enable js or css processing back, but disable minification (merge only). On the status page, you must purge the cache, then try again.
d) If this didn’t fix, then there is probably a problem merging your files (some incompatibility). The solution is to use the ignore list.
You can extract a list of files that have been merged from the status page and add them to the ignore list. Then remove one by one and refresh, to see if it works. When it works, the file you removed is the one you need to put in the ignore list (others you can remove).
In the end, you will end up with one or two files on the ignore list.
Once you know, please let me know so I can look at it in the future and think of a way.
Please read the faqs for more information:
https://ww.wp.xz.cn/plugins/fast-velocity-minify/faq/
@gemini23 after some quick testing, it turns out that nextgen gallery needs jquery to be render blocking, so you may want to consider using it if you’re aiming at removing the render blocking message from pagespeed insights.
There are 2 ways to make the gallery work with fvm:
Option 1:
Add these to the ignore list:
/jquery.js
/nextgen_basic_gallery/static/thumbnails/nextgen_basic_thumbnails.min.css
/nextgen_basic_gallery/static/slideshow/nextgen_basic_slideshow.min.css
or, Option 2 (better):
Add only the /jquery.js file to the ignore list, but make sure you select the “Inline all header CSS files” option.
—
What happens here is that if we merge jquery with other scripts, the gallery cannot read it.
Secondly, their css files cannot be merged into one, because those 2 CSS files on Option 1, are not using specificity ( https://www.smashingmagazine.com/2007/07/css-specificity-things-you-should-know/ ) that allow them to overwrite others, when merged together.
Without that, styles get broken simply by merging the css files.
It works when you inline, because the browser evaluates each css block individually.
