Home Forums Weaver Xtreme Theme Is a font being defined in the theme?

Topic Resolution: Answered
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #69490
    Answered
    GeorgeW
    Participant

    Hello folks – hope you’re well!

    Sorry for the long post.

    Using Firefox, if someone goes to https://pluginpoets.com/ready-made-sites , adds a website to their cart and then checkout…

    … on the checkout page, if they select to pay with a credit card on the checkout page, the “Credit Card” field is not showing “Day/Month/Year” or CVV.

    Also, the field is not responding if one tries to click in it.

    Video:

    https://drive.google.com/file/d/1zE8pIQwg3uZwFBJ1IMQTuxXHW5uLHKSa/view?usp=sharing

    This form is created by a plugin called Easy Digital Downloads.

    I contacted them about this, and their response was:

    – – –
    The issue is likely because your theme has no defined font set so the dynamic styles being applied to the credit card field are using the Windows font “MS Shell DLG” which is causing the syntax error when building the credit card field.

    To stop the user agent stylesheet from taking over, the theme needs to define an input font family:

    input { font-family: “Open Sans”; }

    Add that CSS to your theme/site, clear caches and try again as that should solve the issue.
    – – –

    Well, I have pasted the code above exactly as it is in the Weaver Xtreme “Fonts and Custom” text area.

    I have tried clearing cache, disabling all my browser addons and using an Incognito window. The issue persists.

    It works fine with Chrome or Microsoft Edge (it always did).

    Can someone see if a font is actually being defined in the theme now?

    The Weaver Xtreme theme has several font options and I have defined specific fonts in most them.

    Thanks!

    George

    #69491
    scrambler
    Moderator

    The site does already define a font family, so that is not the issue.
    The issue also does not happen on Chrome or Edge, so you need to go back to the developer on why it is doing that with Firefox only ….

    #69492
    Best Answer
    Weaver
    Keymaster

    This reply has been accepted as the best answer.

    The link you provided, https://pluginpoets.com/ready-made-sites, must be being generated by a plugin or something, and NOT by the Weaver Xtreme theme. I don’t know how you are doing that – typically every page on a site is generated by some Weaver Xtreme template, but NOT the page at the link your provided. It does load some Weaver Xtreme JavaScript files, but no styling nor other HTML that would normally come from the theme. I don’t know for sure, but it seems there is a plugin called “Thrive” that may be replacing the real theme.

    As far as I can tell by looking at the HTML of that page, it does NOT include the normal .css styling used by Weaver Xtreme, nor even the Custom CSS you may have defined for the theme. So this does not seem to be a theme issue, rather some plugin issue.

     

    One possibility would be to use the Customizer ->  Custom CSS -> Additional CSS -WP settings to add that input styling suggested by the plugin support instead of the Weaver Xtreme Custom CSS. I think the WP version will always be included, even for plugins, while the Weaver Custom CSS settings are there only when using a page generated by Weaver Xtreme, which is almost always the case.

    #69493
    GeorgeW
    Participant

    Ka-ba-BLAM! You guys deliver again!

    Thank you scrambler and Bruce…

    Bruce, the real page in question is https://pluginpoets.com/checkout/

    That’s where the credit card field wasn’t working.

    The page https://pluginpoets.com/ready-made-sites and the checkout page, are built with the Thrive Architect WordPress plugin, which is a WYSIWYG visual landing page builder.

    I just added the font code in Customizer -> Custom CSS -> Additional CSS -WP settings – and now the credit-card field works!

    Thanks!

    George

    #69494
    scrambler
    Moderator

    what I don’t get is why the issue only occurred on Firefox…

    #69495
    GeorgeW
    Participant

    scrambler, although I’m no programmer, I guess other browsers may have different fall-back settings for fonts?

    #69496
    Weaver
    Keymaster

    It seems that form elements (including input) do not seem to be required to inherit from the cascade, at least in some versions of HTML. So it must be that Firefox is not implementing input inheritance. But form elements can be manually overridden.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.