Jeff Daigle
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] on_sent_ok errorI second this. Removing such an important and widely-used feature without community discussion (as far as I know) seems like a bad move. I’ve decided to migrate my forms to another plugin long-term, but short term I have found that this plugin will keep my Contact Form 7 forms working for now:
I’ve been living dangerously for the past few months and using it with PHP 7. No issues.
Thanks, I ended up switching to the Woocommerce Square Gateway from Woothemes. That was having trouble as well but I was able to get it working. Thanks for the help anyway.
Forum: Plugins
In reply to: [FoundationPress] Stripe checkout error with woo commerceI’m also having this problem with a custom theme developed using FoundationPress. The problem is caused by the foundation.js file (if I manually remove it from the header the checkout process works) but I can’t for the life of me figure it out.
I’m using Woocommerce’s official Stripe Gateway Plugin:
https://woocommerce.com/products/stripe/The error I get is:
TypeError: wc_stripe_form.form.block is not a function. Referring to lines 52-60 in stripe.js: block: function() { wc_stripe_form.form.block({ message: null, overlayCSS: { background: '#fff', opacity: 0.6 } }); },
OK, I’m confused: first you say your plugin doesn’t load any javascript, but now you’re saying that 1.0.8 does?
Can you tell me which javascript files your plugin relies on, whether they are part of Woocommerce, being loaded from stripe.com, or included with your plugin?
That might help us get some idea of what is going on.
My theme doesn’t override any of Woocommerce’s checkout pages or scripts.
I tried a few older versions of your plugin.
1.0.8 = Doesn’t work
1.0.6 = Doesn’t work
1.0.4 = WorksSo something changed b/w 1.0.4 and 1.0.6 that is causing this error.
The test site is running 1.0.4 right now if you’d like to take a look and test it yourself:
It works under 2016 but switching themes isn’t an option for this client.
Again, could you look at the source code of the checkout page to make sure that all of your plugin’s javascript is being loaded correctly? Or at least give me a list of the scripts that the plugin should be loading so I can do it?
All file permissions are correct.
Can you look at the code to see which scripts are missing?
Can you tell me which scripts should be loading so I can check them?
I don’t see any javascript errors in the console in either Safari, Chrome, or Firefox.
The home page for the testing site is:
https://www.christophertaylortimberlake.com/staging/The store page for the testing site is:
https://www.christophertaylortimberlake.com/staging/catalog/The cart page for the testing site is:
https://www.christophertaylortimberlake.com/staging/cart/
The checkout page for the testing site is:
https://www.christophertaylortimberlake.com/staging/checkout/Let me know if you need a temporary admin login.
Yes, I did, but then re-enabled it since it made no difference and I don’t want to give up the performance boost from pre-fetching those resources.
I’ve turned prefetch off again.
As I said above, the site is already in test mode.
You can add the following product to your cart to test it for yourself:
Use the following credit card info:
Number: 4242 4242 4242 4242
Exp: 01/21
cvv: 123The dns prefetch items are added by WordPress Core. Just for fun I disabled them, and the problem persists.
Not running Jetpack or any other caching plugin presently.
Sorry, that exp date should be 11/21 (or anything in the future).
Yes, I’ve got a valid SSL certificate and the checkout page is using SSL (green lock).
Still getting the “You have passed a blank string for ‘card’. You should remove the ‘card’ parameter from your request or supply a non-blank value.” message when I click “Place Order”.
You can try it out yourself, here’s a product to add to the cart:
Yes, I know, this is a staging site I put together quickly to demonstrate the issue with the plugin. The broken images are not relevant to the problem I am posting about and will be updated shortly.
Can we focus on the error with the Square plugin?
The plugin is in sandbox mode so you can use credit card number 4242 4242 4242 4242, exp date 11/11, and cvv code 123 to test.
That’s my development site, not accessible to the internet.
I think the blocked frame message is a red herring (not related to the issue).
Here’s a test site you can see the issue on (images might be broken but the site works):
https://www.christophertaylortimberlake.com/staging/catalog/