I installed the theme without any other plugins, using only FVM and all css and js files are being merged properly, meaning, they are also enqueued properly.
There are some conflicts when merging CSS due to the lack of specificity in some files https://www.smashingmagazine.com/2007/07/css-specificity-things-you-should-know/
In my case, I had to exclude /wp-content/themes/spalab/css/custom.css
via the ignore list, or alternatively, choose to inline all css without ignoring the file.
This works, because merging they are executed as one css file, while with inlining, they are still considered separate style rules, and so the last one wins.
Basically, the code on custom.css is causing the header background to disappear on my demo, when merged together with the others, due to the lack of specificity on other css files that come before it.
But other than that, all files found were merged.
There is no shortcodes directory on your theme, and neither there is any title.css file on it, so the issue is nothing to do with the theme, but rather one of your other plugins adding that css file.
—
I then proceeded to install and activate all recommended, bundled plugins.
This time there are 3 css files.
First one is merged by FVM.
Second one is https://code.jquery.com/ui/1.11.0/themes/smoothness/jquery-ui.css
Third one is merged by FVM.
Because you have an external file, that file splits the merging.
If you add it under the External URLs to Merge
on the Pro tab, it get’s merged together and you are now left with only 1 FVM generated file.
View post on imgur.com
This is the correct behaviour and for some reason, the specificity issue I explained earlier no longer applies, because now the other plugins installed have either corrected it, changed it’s order or added new code to overwrite it (so no need to exclude).
This is the list of merged css files I get:
https://pastebin.com/GeJm5Tdh
—
I can assume, that the title.css file you are talking about, is generated by one of the plugins, only when you add something on certain page via the editor, likely wpbakery.
You can see the full url on that file, and it will tell you exactly the path to the plugin which is not enqueuing the file properly. It should not be the theme… unless you are using a child theme that has been customized by another developer that didn’t follow the official documentation method of enqueuing the files.
Note however, it could be a limitation of their plugin.
If they are including the file with javascript conditionaly, or if they need to load extra style if something is present or not, that could explain it.
Either way, nothing I can do on my end regarding that situation.
As explained, the plugin only capture files enqueued with the official wordpress method, and so far, all files I saw on that theme and recommended plugins have been captured.
It’s something specific to some module, slider, or whatever is on that page, that it’s adding the css file directly to the page, without enqueuing.
In the future, FVM will be able to capture all CSS regardless of being enqueued or not, but for now that’s how it works for compatibility reasons.
-
This reply was modified 4 years, 7 months ago by Raul P..
-
This reply was modified 4 years, 7 months ago by Raul P..