gpowerhost

There was no need to allow the default implementation, as you say, to break the checkout experience plummeting income. There are a myriad of ways that you could have dealt with this better, programmatically. There could have been a critical notice upon upgrade with the configuration option (you already have but that is buried) pointing out the serious change and the immediate need to review the implementation which, as I already stated, failed to work well. Do you realize that some, individual plugin users lost tens of thousands of dollars because the implementation doesn’t work, and was not well disclosed in the UI or the change log? Is it Strip’s fault that it was implemented in such ways that it decreased sales by 90% and completely eliminated donation via third-party plugins like Give from workig at all because you programatically injected your Woo intended code onto their checkout forms?

Thanks for the insight. In this case, the order had passed through a completed state and then progressed to a custom stated we use internally. When they’ve done this in the past, those orders just disappeared and they would then enter a consolidated entry for all those orders manually to keep the donation totals correct. It would be nice if there were a way to have custom statuses and be able to mark those statues as having been through the “Complete” status (which these all have prior, and perhaps you’d need pending and failed, etc.) so no matter the status it is now, they are equivalently know as completed and get accounted for.

I appreicate the insight and I’m glad we were able to update the client.

Here is a system report:

###########BEGIN

### WordPress Environment ###

Home URL: https://[snip]
Site URL: https://[snip]
WP Version: 6.0.1
WP Multisite: –
WP Memory Limit: 368 MB
WP Debug Mode: –
WP Cron: –
Language: en_US
Permalink Structure: /%postname%/
Show on Front: page
Page on Front: Support [snip] (#477)
Page for Posts: Unset
Table Prefix Length: wp51_
Table Prefix Length: 5
Table Prefix Status: Acceptable
Admin AJAX: Accessible
Registered Post Statuses: publish, future, draft, pending, private, trash, auto-draft, inherit, request-pending, request-confirmed, request-failed, request-completed, in-progress, failed, wc-pending, wc-processing, wc-on-hold, wc-completed, wc-cancelled, wc-refunded, wc-failed, wc-checkout-draft, refunded, revoked, cancelled, abandoned, processing, preapproval, wc-paid, wc-tax-pending, wc-closed-tax-paid, wc-closed-prior, wc-fulfillment-hold, wc-submitted-tax-pen, wc-submitted, wc-service-inquiry, wc-fulfill, wc-paid-tax-pending, wc-fulfill-special, wc-closed, wc-reporting, wc-waiting-4-return, wc-wait-4-return-fre, wc-wait-4-return-lab

### Server Environment ###

Hosting Provider: DBH: localhost, SRV: [snip]
TLS Connection: Connection uses TLS 1.3
TLS Connection: Probably Okay
Server Info: Apache
PHP Version: 7.4.30
PHP Post Max Size: 64 MB
PHP Time Limit: 360
PHP Max Input Vars: 100000
PHP Max Upload Size: 64 MB
cURL Version: 7.71.0, OpenSSL/1.1.1d
SUHOSIN Installed: –
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
gzip: ?
GD Graphics Library: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?

### GiveWP Configuration ###

GiveWP Version: 2.21.4
GiveWP Cache: Enabled
Database Updates: All DB Updates Completed.
Database Updates: All Database Migrations Completed.
Database Tables: ? wp51_give_donors? wp51_give_donormeta? wp51_give_comments? wp51_give_commentmeta? wp51_give_sessions? wp51_give_formmeta? wp51_give_sequential_ordering? wp51_give_donationmeta? wp51_give_revenue? wp51_give_migrations? wp51_give_log
GiveWP Cache: Enabled
GiveWP Cache: ?New Donation?Donation Receipt?New Offline Donation?Offline Donation Instructions?New User Registration?User Registration Information?Donation Note?Email access
Upgraded From: 2.21.4
Test Mode: Disabled
Currency Code: USD
Currency Position: Before
Decimal Separator: .
Thousands Separator: ,
Success Page: https://[snip]/donation-confirmation/
Failure Page: https://[snip]/donation-failed/
Donation History Page: https://[snip]/donor-dashboard/
GiveWP Forms Slug: /donations/
Enabled Payment Gateways: Stripe - Credit Card, Offline Donation
Default Payment Gateway: Stripe - Credit Card
PayPal IPN Notifications: N/A
Donor Email Access: Enabled
Stripe Webhook Notifications: July 9, 2022 5:05 am

### Active GiveWP Add-ons ###

### Other Active Plugins ###

Ajax Cart AutoUpdate for WooCommerce: by taisho – 1.5.5
Akismet Anti-Spam: by Automattic – 4.2.5
Bloom: by Elegant Themes – 1.3.12
Breadcrumb: by PickPlugins – 1.5.27
Bulk Change Media Author: by Ruslan Mikhno – 1.2
Cart Insights for WooCommerce: by Berend de Jong – 1.4.3
Disable Admin Notices Individually: by Creative Motion  – 1.3.0
Disable Bloat for WordPress & WooCommerce: by Disable Bloat – 3.0.3
Divi Responsive Helper: by Pee-Aye Creative – 2.2.3
gPH AUG Front-end Styles: by gPowerHost – 1.1.02
Maintenance Mode: by Lukas Juhas – 2.4.4
Members: by MemberPress – 3.2.1
Monarch Plugin: by Elegant Themes – 1.4.14
Post Duplicator: by Metaphor Creations – 2.28
Product Size Chart for Woocommerce: by Ciobanu George – 1.1.3
Real-Time Find and Replace Pro: by Marios Alexandrou – 4.0.3
Scheduled Sale Manager for WooCommerce: by Berend de Jong – 1.11.2
Search Exclude: by Roman Pronskiy – 1.2.6
Ultimate Order Combination: by Fahad Mahmood – 1.5.4
User Switching: by John Blackbourn & contributors – 1.6.0
User Switching in Admin Bar: by wpexpertsio – 1.4
WooCommerce: by Automattic – 6.7.0
WooCommerce - StampscomEndicia Integration: by Stamps.comEndicia – 2.0.0
WooCommerce Bulk Stock Management: by WooCommerce – 2.2.31
WooCommerce Cart Notices: by SkyVerge – 1.13.3
WooCommerce Cost of Goods: by SkyVerge – 2.11.1
WooCommerce Customer/Order/Coupon Export: by SkyVerge – 5.3.3
WooCommerce Extended Coupon Features FREE: by Soft79 – 3.2.9
WooCommerce Order Navigation: by woosmartcod.com – 1.1
WooCommerce Order Status Manager: by SkyVerge – 1.13.3
WooCommerce PDF Invoices & Packing Slips: by WP Overnight – 3.0.0
WooCommerce Sale Flash Pro: by WooCommerce – 1.2.22
WooCommerce Shipment Tracking: by WooCommerce – 1.7.0
WooCommerce Smart Coupons: by StoreApps – 5.6.0
WooCommerce Stamps.com API integration: by WooCommerce – 1.3.26
WooCommerce Stripe Gateway: by WooCommerce – 6.4.3
WooCommerce Tab Manager: by SkyVerge – 1.14.1
WooCommerce USPS Shipping: by WooCommerce – 4.4.74
WooCommerce Waitlist: by Neil Pie – 2.3.2
WooCommerce Warranty Requests: by WooCommerce – 1.9.33
WP Crontrol: by John Blackbourn & crontributors – 1.14.0
WP First Letter Avatar: by Dev49.net – 2.2.8
WP Mail SMTP Pro: by WPForms – 3.4.0
YITH WooCommerce Badge Management Premium: by YITH – 1.4.14

### Inactive Plugins ###

Divi-Modules – Table Maker: by Divi-Modules – 2.0.1
Follow-Up Emails: by WooCommerce – 4.9.24

### Theme ###

Name: Divi Child
Version: 1.0.0
Author URL: https://www.elegantthemes.com
Child Theme: Yes
Parent Theme Name: Divi
Parent Theme Version: 4.17.5
Parent Theme Author URL: https://www.elegantthemes.com

#############END

If you are suggesting that there’s and issue on our end, there’s nothing wrong with cURL on our server TaxCloud just refuses to answer. So, either your plugin has changed the way it asks or api.taxcloud.net is refusing our request. Possibly the latter. Maybe it’s a firewall issue on api.taxcloud.net end. To illustrate that api. is selectively blocking requests:

Go here:
https://ip-lookup.net/domain.php

Enter in the domain: “api.taxcloud.net”
and there is no dns response.

Enter in the domain “taxcloud.net”
and there is.

Hello,

We are using this filter to save cards for those customers who’ve agreed:

add_filter( 'wc_stripe_force_save_source', '__return_true' );

Do you have a replacement?

So far, Plaid seems reasonable to work with and many of our clients should have to pay about $1.50 as a one-time fee to Auth each bank account (on a pay-as-you go plan). Is that in line with what you’ve heard? Am I missing anything Plaid wise (Auth is sufficient product)?

Thanks!

I feel that this is unfair. I’m not reviewing the plugin. Perhaps, a plugin would have been a better way to do Gutenberg but I’m not talking about a plugin. And, there are clear indicators that feedback is appropriate here. There is even a checkbox to help divide those feedback posts from support posts.

I’m not asking for Gutenberg to be shelved and I don’t understand why its remaining would change the value of my feedback. I think that the timeline is off. There is certainly room to change the future.

If you wish to shut me up then go ahead and do it.

• This reply was modified 6 years, 2 months ago by gpowerhost.

I got this issue on a new installation.

To any who still need more instructions on how to fix:

1. Backup your database.
2. Confirm your backup is good.
3. Open database in phpMyAdmin and click on the wpXXX_subscribe_reloaded_subscribers database table.
4. Click on Structure Tab. Notice that the “subscriber_email” and “subscriber_unique_id” columns both have a Collation of: “utf8mb4_unicode_520_ci”, which needs to be changed to: “utf8mb4_unicode_ci”.
5. Chick on the “Change” icon for each column and use the dropdown menu to change: “utf8mb4_unicode_520_ci” to: “utf8mb4_unicode_ci” and click “Save”.
6. Test to see if that worked–it did for me. If not, restore your database from your backup.

Thanks to the Developer for this great plugin and thelawstudentswife for reporting this bug and the solution on the GitHub support page.

Also, in our evaluation we looked at the consistency of responses to SUPPORT questions here in the Plugin Support Area. This developer is on the ball providing prompt and courteous FREE SUPPORT for the FREE plugin–not just occasionally–but like clockwork since day one!

BTW, I should clarify that we made an error in our original post. After checking our client upgrade notes we know the issue began after the upgrade to WordPress 3.7.1 from version 3.7. Prior to installing your next version. Something likely changed in WordPress that caused the issue to surface. The plugin is certainly well crafted, and of course is well maintained.

Thanks! Five Stars to you, and EWWW Image Optimizer!
Your Plugin saves our clients a great deal and makes their sites load even faster.

Note: Most of our servers are on more recent PHP versions. Though, some of our customers aren’t ready to switch yet and are still on EOL/Depreciated versions of PHP. In a few months, they will all be on versions that don’t even have the possibility of Safe Mode (not that is being used now). But we really appreciate your excellent service and responsiveness none the less.

Thanks! Here is a link to some discussion of this issue: that might be helpful. ??

Added note: One of our developers suggests that you might be checking ini_get(‘safe_mode’ agaist only the boolean and not also “Off” and the somewhat unlikely, but still possible “off”. Our servers need safe_mode = Off not safe_mode = 0 .

Could this be the issue?