I just wanted to come through and note that we’d solved this WooPayments account issue over in chat on WooCommerce.com. The account has been fixed and enabled now. 🙂
Howdy again @cre8ivewave. I’ve added a specific section to our docs now to clarify how to handle commas in things like product names, categories, etc…
Thanks for helping contribute to this change. You’ve helped make these resources better for the Woo community!
Thanks for opening this thread, and for also submitting a support request on WooCommerce.com for this question. I wanted to share what we had discussed here as well in case anyone else came across this issue.
At the moment, this would only be possible by modifying the Google for WooCommerce plugin. I was just looking for any existing hook or filter, but at the moment there isn’t one. This code that does this exists in the google-listings-and-ads/views/meta-box/channel_visibility.php file at lines 43-48.
I know this isn’t what we normally recommend, to update a core part of a plugin that would be overwritten by an update. But you can comment this if statement out.
IDEALLY, it would be great to add this to our ideas board. It’d be great to have a filter added to the plugin so you can disable this if statement, safely.
I think with the above information, we could probably mark this thread as resolved, but please do create a new thread if we could discuss this further or anything else in Woo. Thanks!
Just to clarify and confirm, this LIVE label is part of the Coming Soon Mode that came in WooCommerce 9.1.
There are of course hooks & filters you can use to customize or disable it entirely, see the post on our developer site.
If you were up to it, I think you all could bring some worthwhile suggestions to be made on this feature over on GitHub as an Enhancement Request. For example, there is already a WordPress Environment type that perhaps WooCommerce could extend with our Coming Soon Mode feature.
Let me know if that helps and what you think!
This reply was modified 1 year, 6 months ago by Ryan Ray, a11n.
Thanks so much for the review, Zade, and being honest with your experiences here.
I do know that the issue with styling on version 3.1.7 is being worked on, and I would say that the Braintree plugin supports 3DS at this point, like was mentioned in patrickhs support thread. Outside that, it sounds like you’ve done everything else that is often recommended when thwarting card testing attacks.
I’m glad you’d found WooPayments as a great solution for the card testing issues you’ve experienced. If we can help further troubleshoot that and try to help improve your experience with Braintree please do let us know.
Had you seen this pull request that made the getdata() method in the order-attributes.js file accessible? This was done to help get order attribution work with payment methods that add express checkout options, like Apple Pay & Google Pay.
There is then this related issue where further discussion is taking place on how to get that data. Check those over and perhaps there is some useful changes there you can use in your checkout you’re building to still populate and use order attribution data.
Thanks for sharing any logs and your system status with us when you can. That’ll give us a bit more insight into what’s in use on the site, and could offer some theories on what may be happening.
Can I ask in the meantime, when you do update stock via CSV, is that the only column or data, outside a SKU or ID number to match to existing products, in your CSV file you import?
That’s a good question. Maybe these are details they can add as account fields in the My Account page? Something that is saved to their account / profile and not used when checking out with Apple Pay / Google Pay since neither seem to fully support custom fields currently.
Happy to help as best we can. It is a bit of a bummer, I’m sorry that your data was muddled for those few days. Maybe there’s a way to divide said data by a quarter for however you may report or record that?
Do we have any options for repairing the incorrect data in GA4?
Thanks for the question, and to my best knowledge once it’s in Google Analytics it is there with no option to edit. I don’t know, nor can I find, any way to correct historical data in Analytics.
This reply was modified 2 years, 1 month ago by Ryan Ray, a11n.
Thanks for the short review. As you may have seen in other threads, rolling back the Google Analytics plugin on your site to version could help make sure things work for you as they were before.
From the Advanced View page, scroll to the bottom, and you’ll see a dropdown where you can select 1.8.14. Also, to be sure, do you know that the current 2.0.3 version doesn’t work on your site?
Either way, I hope this helps and as more updates are released we can help change this review to a good one!
