Hi @theblueking,
That would definitely be one reason why Woo & Square won’t sync products, they need to have matching SKUs between the two systems to know what two products to sync.
There is no proper way or method to name your SKUs, if that’s what you’re asking. When it comes to variations, just make sure each variation has a unique SKU that matches as well. You can set a unique one for each variation in both Woo & Square.
Those can be numbers or maybe colors, sizes, etc… just depends on what you prefer and how you want to use SKUs. Does that help clarify things?
Hi @shanemarsh28,
Is there any further information you can provide for this post? Where and/or how are you getting this error and are there certain steps we need to take to recreate this?
Could you please share a copy of your site’s System Status as well? You can find it via WooCommerce > Status.
Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
Hi @susanlangenes,
Between the site where this breaks and the cloned site, could you send us the system status reports from each of those?
You can find it via WooCommerce > Status.
Select “Get system report” and then “Copy for support”. Once you’ve done that, paste them here in your response.
Thanks!
Hi @rbrcurtis,
Perhaps there was a mis-understanding but at the moment this extension doesn’t sync orders between the two systems. Only inventory is synced between the two, and while payments show up there’s not functionality there to also sync orders just yet.
I’d wager it is a fairly popular idea though, add your votes to the idea here. 🙂 –> https://ideas.woocommerce.com/forums/133476-woocommerce/suggestions/15902653-square-sync-orders
Hi @onoxin,
Thanks for the reply and information. Is there any chance you’d have a staging site that replicates the issue? If your host doesn’t offer that option, we recommend WP Staging (https://wordpress.org/plugins/wp-staging/) for quickly spinning up a new test site.
On the test site I would try activating Storefront itself and then plugin wise only have WooCommerce & Jetpack enabled. Then see if infinite scroll causes issues still. It’d be great if you could help out and run a test like that, let us know what you think.
Hi @newcelic,
The thread remains open until you say so or mark it resolved yourself. Please do let us know what you find in testing this issue out, thanks!
Hi @ulyssislittlewren,
Perhaps you’ve fixed this, but at the moment I can enter numbers into these fields (even though my card number is fake). 🙂
Link to image: https://cld.wthms.co/fIgu7l
Let us know if you’ve solved this or perhaps aren’t seeing what I see just yet.
Hi @yc77s764et7v,
Just to confirm here for me, you’ve created a coupon in WooCommerce that only enables Free Shipping. It doesn’t provide any other discount, correct?
When the Apple Pay prompt appears I believe the customer will need to select the shipping method again as Apple Pay has its own prompt and dropdown for this. Do you know if your customer had done so?
Link to image: https://cld.wthms.co/7pIXex
On my test site from the cart page I added a coupon for Free Shipping, then in Apple Pay made sure I also selected Free Shipping. From there I don’t see any issues, at least in test mode, with the purchase in wp-admin.
Link to image: https://cld.wthms.co/OKpZkT
Where I think the confusion is happening is that when Apple Pay first loads it shows the correct total from WooCommerce reflecting the coupon discount. The problem though is that it’s not defaulting to selecting Free Shipping. Then if you don’t change the shipping method to the correct one you are going to switch that and potentially add back that charge like your customer had seen.
Which I think is what has happened here. At least from here you would be able to refund your customer that shipping fee. Looking through our Github repo I do see an open issue for this as well. –> https://github.com/woocommerce/woocommerce-gateway-stripe/issues/755
Hopefully this can be addressed in a future release then, I’m sorry it’s caused shipping issues for your customer though!
Hi Barry,
Sorry you’ve run into this error, can you let us know what specific error you’d seen in the console?
I’m not sure if we can recreate this, but what I would try is perhaps seeing if some conflict troubleshooting might help show the error on the front end.
The best way to determine if the issue is being caused by a theme and/or plugin is to temporarily switch your theme to Storefront (https://woocommerce.com/storefront/) and disable all plugins except for WooCommerce. Finally, test to see if the issue is resolved by
To figure out which plugin is causing the problem, continue to the next step – reactivate your other plugins one by one, testing after each, until you find the one causing conflict.
Here’s a more extensive explanation in our docs: https://docs.woocommerce.com/document/how-to-test-for-conflicts/
—–
Tools to help you troubleshoot:
Meks Quick Plugin Disabler is a plugin you can install which will remember what plugins you currently have active so it’s easy to switch them back on. Link: https://wordpress.org/plugins/meks-quick-plugin-disabler/
You can clone your site to a staging environment and perform tests without modifying your live site or impacting customers. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free WP Staging plugin. Link: https://wordpress.org/plugins/wp-staging/
PS – Could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status.
Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
Hi @jarfar,
Just to clarify, this function happens no matter the payment method in use. It’s not something Stripe does, rather a WooCommerce function. It looks like the issue will be fixed likely in the 3.9 release slated for early next year, which you can see the PR for here. –> https://github.com/woocommerce/woocommerce/pull/24227
I hope that helps.
Hi @stevek28,
Sorry you’re having issues with a translation in Stripe. Just to clarify, you’re site is using German as its main language and then you’ve installed the translations available for WooCommerce and Stripe. Do you also happen to be using our Subscriptions extension?
Would you mind sharing your site’s System Status? You can find it via WooCommerce > Status.
Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
Hi @surbma,
do you plan to modify the CVC field’s type to password?
No plans for this currently. At the moment none of the fields use the password label as I’m fairly certain we load the Stripe Elements from Stripe themselves. Meaning we may not have much control over the labels used. We provide a simple HTML markup required by Stripe that then uses JavaScript to fill in with their specific card fields.
Like this thread outlines, Stripe Elements doesn’t provide a way to modify those fields. –> https://github.com/stripe/react-stripe-elements/issues/328
I hope that helps explain things, and if it helps the PCI standards that help dictate payment and security standards don’t recommend the fields in the payment form use be masked. Stripe thus follows those requirements as needed in their forms.
Hi @indigodove,
Good work finding the cause. I think if the clients site, or client/you, are familiar and like using that plugin it’d be ideal to report the issue to their team.
When this sort of thing happens with payment methods it is usually a JavaScript error or something that loads over HTTP instead of HTTPS, which for good reason scares the payment processor since it’s not secure. 🙂
Nonetheless, the other big player in the SEO plugin space would be Yoast but like I said it should be something that the All in One SEO team could help fix quicker than you switching and redoing your SEO setup in another plugin.
Thanks for letting us know your solution thus far!
Hi @smallakin,
I’m sorry to see this happening when updating Square to the latest version, in this case there is a likely (from past experience) conflict happening here with how the payment form works in 2.0+
Would you happen to have a copy of your live site, a staging site, where you could update Square to the latest version and see if the card form issue happens there as well? I would then enable logging under WooCommerce > Settings > Payments and select Manage next to Square. Then at the bottom of those settings you’ll see a checkbox to enable Logging.
Image link: https://cld.wthms.co/t7saqj
Then if any errors are logged you’ll find those under WooCommerce > Status > Logs tab. There will be a Square log for every day that logging is enabled. Pick the appropriate day to find that days logs.
Also, if possible on the staging site would you be able to share the system status? You can find it via WooCommerce > Status.
Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
If your host doesn’t offer that option, we recommend WP Staging (https://wordpress.org/plugins/wp-staging/) for quickly spinning up a new test site. I hope that helps.
Hi @nicethreads,
Thanks for keeping an eye out for the issue returning after 2.0.6. I’ve seen in other cases a quick disconnect and reconnect helps fix this, seemingly it could be caused by an access token gone bad and hadn’t auto renewed.
