I don't know why you force to have Roboto or Lato.... these fonts are not part of our brand guidelines. Just allow us to use default inherit theme font and not force use of any of these fonts... very bad practice.
At the moment you have option to choose one of those fonts from Customize page. If you what to use some other fonts, you can use this CSS rule on the page between style tags where you will overwrite font from our plugin.
Thank you for your suggestion. I will forward your request to my development team to discuss about this.
We carefully follow customers requirements and try to implement most of them if they appear in requests from time to time, so we will add to our idea list and look into some possible solutions on plugin side in the future.
I don't know why you force to have Roboto or Lato.... these fonts are not part of our brand guidelines. Just allow us to use default inherit theme font and not force use of any of these fonts... very bad practice.
Hi waynep16,
Thank you for your purchase.
At the moment you have option to choose one of those fonts from Customize page. If you what to use some other fonts, you can use this CSS rule on the page between style tags where you will overwrite font from our plugin.
<style> .amelia-app-booking input[type="text"], .am-modal.am-in-body input[type="text"], .amelia-app-booking input[type="email"], .am-modal.am-in-body input[type="email"], .amelia-app-booking input[type="tel"], .am-modal.am-in-body input[type="tel"], .amelia-app-booking input[type="url"], .am-modal.am-in-body input[type="url"], .amelia-app-booking textarea, .am-modal.am-in-body textarea, .amelia-app-booking select, .am-modal.am-in-body select, .amelia-app-booking .form-control, .am-modal.am-in-body .form-control, .amelia-app-booking .am-stripe-card, .am-modal.am-in-body .am-stripe-card, .amelia-app-booking h1, .am-modal.am-in-body h1, .amelia-app-booking h2, .am-modal.am-in-body h2, .amelia-app-booking h3, .am-modal.am-in-body h3, .amelia-app-booking h4, .am-modal.am-in-body h4, .amelia-app-booking p, .am-modal.am-in-body p, .amelia-app-booking span, .am-modal.am-in-body span, .amelia-app-booking div, .am-modal.am-in-body div, .amelia-app-booking section, .am-modal.am-in-body section, .amelia-app-booking ul, .am-modal.am-in-body ul, .amelia-app-booking li, .am-modal.am-in-body li, .amelia-app-booking a, .am-modal.am-in-body a {font-family:fantasy !important;} </style>We insert font fantasy just for example, but you will replace font that you need.
Best regards.
Kind Regards,
Isidora Markovic
wpDataTables: FAQ | Facebook | Twitter | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Amelia demo sites | Docs
You can try our wpDataTables add-ons before purchase on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables
Can you just add an option in drop down customiser to say NONE ? then it will use theme default fonts and not custom?
Hi waynep16,
Thank you for your suggestion. I will forward your request to my development team to discuss about this.
We carefully follow customers requirements and try to implement most of them if they appear in requests from time to time, so we will add to our idea list and look into some possible solutions on plugin side in the future.
Best regards.
Kind Regards,
Isidora Markovic
wpDataTables: FAQ | Facebook | Twitter | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Amelia demo sites | Docs
You can try our wpDataTables add-ons before purchase on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables