Forum Replies Created
-
AuthorPosts
-
ipn.php needs to be accessible
(https://support.wp-pizza.com/paypal-gateway-extension/)
you need to speak to your host and/or check other plugins you are using that might deny access to that page.
might also be a file permission problem.>Nothing has changed with our site and we have started getting these errors and missing orders
that isn’t really likely . things do not stop working by themselves . maybe some server side software update… but i cannot tell you. I know nothing about your server>But the calculation of the system is wrong.
no, it isn’t.42 with taxes included at 8%
42/108*8 = 3.1111… (rounded up as it’s tax) == 3.12
in reverse
38.8888888….+8% = 42i assume you have checked/enabled wppizza -> order settings “all prices are entered including tax, but I distinctly need to display the sum of taxes applied” ?
which makes it correct as it iscant comment without a link
24 February, 2017 at 10:17 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25875This reply has been marked as private.24 February, 2017 at 9:15 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25873This reply has been marked as private.24 February, 2017 at 7:39 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25866worth a read too
https://stripe.com/blog/upgrading-tls24 February, 2017 at 7:11 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25865says it all there
Protocol “https” not supported or disabled in libcurl(if the plugin did not support ssl/https it would not work for anyone, which simply is not the case)
the issue is that TLS 1.1 is still enabled (which can be disabled in the apache conf)
from the stripe sdk in use in the plugin
// Explicitly set a TLS version for cURL to use now that we’re starting
// to block 1.0 and 1.1 requests.
//
// If users are on OpenSSL >= 1.0.1, we know that they support TLS 1.2,
// so set that explicitly because on some older Linux distros, clients may
// default to TLS 1.0 even when they have TLS 1.2 available.
//
// For users on much older versions of OpenSSL, set a valid range of
// TLS 1.0 to 1.2 (CURL_SSLVERSION_TLSv1). Note that this may result in
// their requests being blocked unless they’re specially flagged into
// being able to use an old TLS version24 February, 2017 at 6:38 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25863the problem is the TLS1.1 protocol still being supported on that server (probably/perhaps open ssl version they are using, but i am not an expert)
in any event the stripe error clearly says what it isif there are issues they (that’s the host, not the website developers – unless they are one and the same) should speak to stripe.
>When we developed the website, we used stripe as a payment gateway and we have not experienced any errors,
so what. security issues change and get adapted accordingly24 February, 2017 at 5:11 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25858yup.
its using stripe 3.0.7
whereas wppizza stripe uses 3.20see also
https://support.stripe.com/questions/how-do-i-upgrade-my-stripe-integration-from-tls-1-0-to-tls-1-224 February, 2017 at 5:05 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25857>It is weird because the Stripe-Gateway of woocommerce worked with the same SSL
because it’s probably still using an outdated stripe protocol/library24 February, 2017 at 5:05 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25856This reply has been marked as private.24 February, 2017 at 4:57 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25853PS: Btw, error handling in wppizza 3.x will be handled differently to make finding these things easier
24 February, 2017 at 4:55 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25852ok, my educated guess is the following (this is admittedly difficult to find)
if you comment out approx line 11 in wppizza-gateway-stripe/ajax/ajax.php
error_reporting(0);
to read
// error_reporting(0);and do an order that throws that server error we have been talking about, you will now – most likely – find an entry in your debug.log that says
PHP Fatal error: Uncaught exception 'Stripe\Error\Authentication' with message 'Stripe no longer supports API requests made with TLS 1.0. Please initiate HTTPS connections with TLS 1.2 or later. You can learn more about this at https://stripe.com/blog/upgrading-tls.' in.......etc etci.e your ssl certificate and setup needs to be updated. you will need to speak to your host
(i’d suggest you comment out that line i mentioned above and do a test order that throws your error and check your debug log to confirm this)
cant see how, as the gmaps address data is not stored in the user profile
24 February, 2017 at 4:20 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25848dont remove it .
move it to the right place instead.24 February, 2017 at 4:11 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25845your first problem is certainly here
you/someone has added
define('WP_MEMORY_LIMIT', '256M');
to the bottom of the wp-config.phpit simply does not belong there and it will have no other effect except throwing errors
any customisation of the wp-config belongs ABOVE/* That's all, stop editing! Happy blogging. */so – perhaps you are simply running out of memory when executing an order.
i’ll do a test here regardless (with the proper wp-config.php) and let you know24 February, 2017 at 3:34 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25841This reply has been marked as private.24 February, 2017 at 3:26 pm in reply to: Stripe Checkout returns Error: Internal Server Error #25839This reply has been marked as private. -
AuthorPosts