This is a follow-up to #1452 ...
In that issue, we ended up moving OpenSans out of the Seven core theme and into /core/misc/opensans/opensans.css. The original issue though was about shipping core with a /core/fonts and a /fonts directory:
I'm not sure if this is makes sense or if it's worth pursuing at all, but here it is...
I noticed a considerable difference in the filesize of the .zip from the master branch since the last time I had to download it, so I decided to analyze the size of our various directories. I noticed that when extracted, the
/core/themesdirectory takes up almost half the size of the entire distribution. Digging further down revealed that Seven takes up 99% of that space and that is because of thefontsdirectory. Then I realized that fonts is a resource that various themes might need to access and it might either be a waste to include the same font in more than one themes or simply silly to point to a specific font of a theme from another theme (what happens if the theme that actually ships with the font is removed from the installation?).So the question here is should we introduce a top-level
/core/fontsdirectory (as well as a/fontsdirectory for contrib themes)?...related: #364
Recent comments
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'
I'll test this tomorrow to see if I can replicate the problem and report back. It's not "per user" so it should be working.
TFA - how to setup fallback options 'per user'
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list