Bart Kuijper

@zelphirkaltstahl Your intentions were good and I appreciate you looking out for other WordPress users such as myself. However in this case the warning is unwarranted. In fact updating the readme with something like a version number without pushing a new version is recommended practice by the WordPress Developer Codex.

As a fellow user (not affiliated with this plugin or its author in any way) I’d like to ask you to reconsider your 3-star review. I often use reviews to decide whether or not to install a plugin and your review is – in my opinion – unnecessarily lowering the average score for this plugin.

I find it to be a very useful and well functioning plugin.

I came across this bug as well and reached the exact same conclusion, however I only just downloaded the plugin today.

Looks like something went wrong when committing this fix.

/trunk/readme.txt has a stable tag 2.7, but /tags/2.7/letter-avatars.php still lists 2.6.2 as current, causing the plugin page to also still display 2.6.2.

Both /trunk/lib/ltrav-frontend.php and /tags/2.7/lib/ltrav-frontend.php still contain this bug.

• This reply was modified 5 years, 9 months ago by Bart Kuijper. Reason: Corrected file path

Thanks @abigailm! I was hoping to make the fonts available through the customizer again, so that less technically inclined people working on a specific website in the future would be able to pick a different font more easily. Though there is also something to be said for your approach, since it is less likely to break with future theme updates (not to mention a lot less complicated). Right now it is like you said, the theme still fully supports all fonts, it’s just not showing them in the customizer. As an extra insurance I will probably also have my child theme import the specific Google fonts I picked, just to be sure they continue to be available (even though evolve is already very good about maintaining backwards compatibility).

Hi @romik84, thank you. You’re right of course about the GPL, but this being the support forum for your theme, I could imagine you might not like it or deem it outside of the scope of this forum. The GPL makes it legal, not necessarily polite ??

The ‘Easy Google Fonts’ plugin does allow for the use of Google fonts, but in a very roundabout way and not integrated with the theme at all. It also requires manually adding the CSS tags for lots of parts of the site, since the plugin by default only works on paragraphs and headings. Though it is probably a good solution for those not willing or able to dig into the theme’s code.

On that note, I’m trying to make a child theme that does include all the Google fonts like it was in evolve 4.0.5, but this being my first adventure into php and the WordPress backend, I’m a bit stuck at the moment. Replacing evolve/inc/admin/customizer/kirki-framework/modules/webfonts/webfonts.json with the same file from evolve 4.0.5 appears to bring all the font choices back, however I haven’t managed to make it work in a child theme. If anyone else is doing something similar and has any pointers I’d love to hear it.

@romik84, if you have any objections to public discussion of this subject, please let me know. If this is something that could hurt sales of your paid theme I will remove it immediately.