@bhrealmfr I see inline CSS/styles that are hiding those form elements, both the credit card form and the submit button (and also an Other Amount) field.
The network panel in the browser developer tools show that all requested scripts and styles have loaded, but I see a couple of JavaScript errors that are probably responsible here. Is your site running a Google form plugin? You could check if there are updates available for it, or if some API Key or license expired.
Thanks, I see the js errors too. Complaining about a PayPalScriptSrc and we appear to have an expired GravityForms license and are using a Gravity Forms Paypal Checkout Add-On so that might explain it. Not to find out who bought the prior license. I’ll track that down and hopefully the button will re-appear.
Got my gravity forms license renewed. Still see these same errors about
Cannot read properties of frontend.min.js?ver=2.0:1 undefined at o.setPayPalScriptSrc
Sure seemed like it would be coming from the GravityForms PayPal plugin so updating looked promising. Have to dig more.
@bhrealmfr I see the script looking for a script element with the data-identifier="gform_ppcp_js_sdk"
attribute and then it wants replace its src
, but this script isn’t loaded on the site.
It could be that there’s a version mismatch between the plugin you have and the updated one, or potentially there could be something occurring as a result of the defer
loading strategy on your scripts. Do you happen to have any plugins installed which attempt to optimize the JavaScript files or load them asynchronously?
Most of our plugins are either Gravity Forms (Including the Paypal Checkout), or wooCommerce. One is called Advanced Custom Fields PRO. I don’t know them well enough to know if they alter loading strategy. I was able to update several but it didn’t help the error.
Solution was to update the Gravity Forms Paypal plugin. I had assumed I was on the current version since the plugins page showed no update but I was on an old version and needed to download and re-upload the latest plugin which resolved the issue. Thanks again for your help.
Great! Glad to hear you figured this out through a plugin update. I just checked and saw that the form fields are back.