... it’s a bad practice to give your API keys to thousands of people…
Point taken Ruben, thank you!
Check this link
Big thank you for this link Lubos. It explains that the API wouldn’t really be used, so maxing out wouldn’t be an issue. Still, it would be quite trivial for anyone with access to the theme files to extract my API key, which I suppose would still be bad practise.
I’ll post a question about this at the Redux Github Repository and I’ll request a staff reply on this also.
Thank you so far everyone, I’ll post back here when I have more info.
Following Lubos’ link, I found a couple more on the Redux Github repo, which address the same question and give some further insight:
Looking into the source of Redux’ typography field, there is already an array of available fonts built in (like OriginalEXE and KrownThemes suggested). The API key is only needed as a backup should the locally stored fonts-list be unavailable for some reason.
With Redux, Google fonts only work if you supply a Google API key though. But as long as you provide any key (including a non-existing one), it will work.
So considering everything mentioned here, that’s the route I’m going. I’ll supply a non-existing API key and update the Google fonts list with each theme update.
Thanks again everyone!
Thanks for info!
I have one question, how do you update Google fonts in Redux? I have googled for answer but haven’t found anything.
[...] how do you update Google fonts in Redux? [...]
They release updates to their options framework on a regular basis, so if you follow those you’ll have them automatically I think.
Also, in the framework files you’ll find the Google font related files in ..\ReduxCore\inc\fields\typography\\googlefonts.html and ..\ReduxCore\inc\fields\typography\googlefonts.json
I hope this helps
Lead dev of Redux here. Remove the googlefonts files, have a valid key in your config, and a new update will be downloaded on your next panel load.