mc
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Need versions prior to 3.0Thank you @ryanr14 !
I looked at the code before trying to run it and found the version requirements in the addons class. I jumped the gun thinking that the entire plugin needed WC2.3!Screen shot of addons class
(Not sure how you added images to the post!)I ran the plugin on our staging server and it appears to work in testing mode!
Thanks so much again for your help!Mike
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Need versions prior to 3.0Thanks so very much @ryanr14!
You’re right, the current Stripe version does have relaxed requirements regarding older versions. But I need the most recent Stripe version that will still run on WooCommerce v2.2.3
I should have explained further. My client is running an older version of WP (3.8) and WooCommerce (2.2.3) that was tied to that version because of the integration we built to work with Intuit Merchant Service (SkyVerge plugin) and QuickBooks POS in their shop.Now Intuit has sunset the QBMS in favor of Intuit Payments with an end date of Nov 17. I certainly should have been alerted that they were discontinuing APIv1 but because of the way their developer account is setup, I wasn’t alerted until the client was. 🙁
SO we’re looking for the fastest way to eliminate the Intuit QBMS and replace it with Stripe within their current platform versions. I see that stripe-gateway 2.6.12 still needs WooCommerce 2.3.
So, may I ask if there is a stripe-gateway version pre2.6.12 that is compatible with WooCommerce 2.2.3?I installed the site to another location before we upgraded to yoast 3.1.2 and it works as expected. In other words, there is only one instance of
post_tag-sitemap.xmlThis leads me to believe that something happened in the upgrade from SEO v 2.x to the latest 3.1.2.
Any experience with the same thing?
Report this as a bug?Thank you Daniel. Oddly, the 3.1.2 was working after the SSL to TLS switch. It stopped working and now is working again – without updating to 3.1.3. I’ll update it regardless. Thanks for writing.
I’m having a similar error. It appears to be the SSLv3 error, but we had re-authenticated since the change and it was working up until 2 days ago.
Running scheduled, I get the error. If I run manually, it works fine.
@zerogravity I wonder if both of these are caused by the system having to delete a backup either for storage space or because the number of backups files threshold has been reached?
[INFO] BackWPup version 3.1.2; A project of Inpsyde GmbH [INFO] WordPress version 3.8.1 [INFO] Blog url: http:// [INFO] BackWPup job: NS Dropbox WWW; DBCHECK+DBDUMP+WPEXP+WPPLUGIN [INFO] BackWPup cron: 0 3 * * *; Next: Tue, 30 Dec 2014 @ 03:00 [INFO] BackWPup job started from wp-cron [INFO] PHP ver.: 5.3.10-1ubuntu3.14; apache2handler; Linux [INFO] Maximum PHP script execution time is 600 seconds [INFO] MySQL ver.: 5.5.38-0ubuntu0.12.04.1 [INFO] curl ver.: 7.22.0; OpenSSL/1.0.1[30-Dec-2014 01:10:15] Archive size is 1.04 MB. [30-Dec-2014 01:10:15] 10 Files with 226.00 B in Archive. [30-Dec-2014 01:10:15] 1. Try to send backup file to Dropbox … [30-Dec-2014 01:10:15] ERROR: Dropbox API: (35) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure [30-Dec-2014 01:10:15] 2. Try to send backup file to Dropbox … [30-Dec-2014 01:10:15] ERROR: Dropbox API: (35) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure [30-Dec-2014 01:10:15] 3. Try to send backup file to Dropbox … [30-Dec-2014 01:10:16] ERROR: Dropbox API: (35) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure [30-Dec-2014 01:10:16] ERROR: Step aborted: too many attempts!Thank you Alex. Your fix worked as expected!