Forum Replies Created
-
Posts
-
Hi,
Well my apologies, because I’ve stayed persistent with Gravity and just learned it’s an issue with the gform_review_page hook not being compatible with their Stripe add-on. In case anyone has this same issue I was able to use Better Pre-submission Confirmation instead. Finally found someone at Gravity willing to look into the issue instead of pass the buck. I haven’t tested again with Enfold again yet, but it’s probably not an issue now. Sorry again, I was caught between this being undocumented and also being in a support redirect that kept aiming at you guys.
Thanks!
Hi, I appreciate the link, but we too are doing custom calculations. I’ve search everywhere as well. The last message in that thread says:
“The calculations is done through a javascript function, whenever there are script errors elsewhere on the page it can often conflict. It looks like you are using a kind of custom theme, it should be a pretty simple fix for your dev, the filepath is just wrong.”
So even they say this should be a pretty simple fix for theme dev. Gravity Forms is pretty widely used and is listed as compatible with Enfold, and it’s my go too theme, I’ve got multiple licenses, but this is a big deal to not be able to process the stripe payment with Gravity. I’ve been pretty patient and I don’t want to have to leave a negative comment to warn others, but I’m going to have to consider going to a different theme if you guys can’t help get conflict or file path cleared up.
Updated to 4.0.5 like you advised, still getting the same error. Gravity and Stripe can say to contact you because there seems to be a javascript conflict. I can’t for the life of me get it to throw an error that helps pinpoint in console. Stripe has pointed me to you as well. Again, it all works with default 2017 theme but not Enfold. Getting to the point where we are going to have to change themes if you can’t solve it, but we love Enfold!
I’m having the same issue with the Layered Nav and Filter widgets not showing on shop base page. Any suggestions on how this was fixed?
