maxd2020
Forum Replies Created
-
I updated back to v3.5.2 and tested what you suggested. On my staging site, I created a new page and added the default Woocommerce checkout — I’m still getting the red error bar at the top of the checkout page that reads, “ZIP Code is not formatted correctly.”
I’ve also just now noticed that no tax is being added when inputing an address for my shop location state (Arizona) with automated taxes enabled.
I should also mention that this issue only happens when I enter an address that corresponds to my shop location. When I enter an address for any other state, there is no error.
In the changelog for v3.5.2, it says, “Fix – Correct nexus address handling for stores in CO, AZ, and OH (US) and QC (CA).” So I thought my issue had to do with my shop location being AZ.
To test this I changed my shop location to California to see if the issue would go away, but it didn’t. After setting my shop location to California, the issue persists but now only when I enter a California address and not with an Arizona address.
So it appears that this issue happens when entering any address that corresponds to the shop location. Additionally, no tax is being calculated/added for addresses that correspond to the shop location (the only time taxes should be added as my business only has nexus for my state). And all of these issues are both with the default Woocommerce checkout and my custom FunnelKit checkout.
One last observation — I don’t know what’s different about today than yesterday, but when I disable automated taxes and import my own tax rate table CSV, everything works as it should and I don’t get any zip code error.Yeah, as long as this plugin exists, there’s really no need for CryptoWoo, unless maybe if you’re trying to accept all sorts of other alt coins. Probably other free plugins for those, though.
I can confirm that I’ve successfully received payments correctly with this plugin running WC 3.0.9. and WP 4.8.
Thank you for sharing that workaround for marking orders as “processing” after completed payment instead of “completed” since I also only mark orders “completed” once shipped.
I’d also be interested in having the payment address included in the completed payment email.
Oh and I have updated to the latest WC 3.0.9 with WP 4.8 and the plugin is operational. It officially supports up to WP 4.4.10, but it’s working for me. On the plugin page on wp.org, I actually don’t see anything about which versions of WC it’s compatible with, only mentions WP.
If you’re worried about updating, you might look into the “WP Rollback” plugin, which can revert plugins back to previous versions (i.e. WooCommerce) after updating.
Yep, it’s operational and back to normal after applying this fix.
Orders don’t automatically cancel for me, either. Heck, I even have to manually “complete” orders as that doesn’t happen automatically, either. Maybe due to the WP soft cron? I’m on a managed WP and don’t have access to cPanel to create my own hard cron job so that may be the reason.
Anyone know how to create cron jobs in managed WP without access to cPanel? Maybe I’ll have to contact my host to see if it’s even possible.
I actually purchased CryptoWoo along with the HD wallet add-on for $34 and $29, respectively. Got it just to have a working solution that is regularly maintained, but now that I’ve fixed the free Bitcoin Payments for WC plugin, I sort of don’t have a use for it — the extra features don’t seem that useful to me. But whatever, it’s a small price to pay to know I have a legit, working solution for a year in case I ever have issues with this plugin in the future. It’s just that the setting up of WP to utilize CryptoWoo is another challenge — hard cron is necessary, as opposed to the default WP soft cron.
Oh my gosh, I didn’t know it was that simple. I’m not super advanced at this sort of thing, but I’m definitely capable of accessing the site via FTP.
I, too, can confirm that this fix works. Thank you, @jylee1997123!
Tip for others: Line 763 in bwwc-utilis.php — this is the only instance where you will make the change. I saw two other instances where the https://api.bitcoinaverage.com address shows up and foolishly changed those, too. I refreshed my site and got the white screen of death (500 error) until I disabled the plugin via FTP.
I am having the same problem and see the same error message in the backend indicating the bitcoin payment plugin is nonoperational. I messaged the developer a couple days ago, but have not gotten a response.
I have just sent another message to the developer asking about purchasing the pro version. I see the bitcoin address to send payment/donation to on the bitcoinway website, it’s just not clear how much the pro version cost.
I’d like to try the fix posted by jylee, but I believe that must be in the advanced settings which are only available on the pro version.
Hopefully I hear something soon — I’ll report back any relevant info.
BTW, I also had the “No FX Rates Available” problem in Electrum, which I was able to fix. I was using Electrum 2.6.4, and the “Fiat” tab was nowhere to be found in the preferences — I downloaded the newest version (2.8.3) and was able to find the “Fiat” tab in Tools>Preferences. Set Fiat as USD and Source as BlockchainInfo — BitcoinAverage is now obsolete. Left “Show history rates” unticked.