conflict with SimplePayPro for Stirpe
-
I’ve isolated TablePress as the conflicting plugin after installing WP Simple Pay Pro for Stripe. My dev machine is a MacBookPro with everything current, checking things on windows through Parallels.
I already had TablePress set up and really like it. Then trying to put shortcode buttons for Stripe using the Simple Pay Pro Plugin inside the TablePress table is when I started getting the error:
“Fatal error: Uncaught exception ‘Stripe\Error\InvalidRequest’ with message ‘Invalid source object: must be a dictionary or a non-empty string. See API docs at https://stripe.com/docs” in /home/jeffnye3/public_html/auilanguage.org/wp-content/plugins/stripe-checkout-pro/libraries/stripe-php/lib/ApiRequestor.php:102 from API request ‘req_7wEBX34dF9U7Ny’ Stack trace: #0 /home/jeffnye3/public_html/auilanguage.org/wp-content/plugins/stripe-checkout-pro/libraries/stripe-php/lib/ApiRequestor.php(216): Stripe\ApiRequestor->handleApiError(‘{\n “error”: {\n…’, 400, Array, Array) #1 /home/jeffnye3/public_html/auilanguage.org/wp-content/plugins/stripe-checkout-pro/libraries/stripe-php/lib/ApiRequestor.php(60): Stripe\ApiRequestor->_interpretResponse(‘{\n “error”: {\n…’, 400, Array) #2 /home/jeffnye3/public_html/auilanguage.org/wp-content/plugins/stripe-checkout-pro/libraries/stripe-php/lib/ApiResource.php(105): Stripe\ApiRequestor->request(‘post’, ‘/v1/customers’, Array, Array) #3 /home/jeffnye3/public_html/auilanguage.org/wp-c in /home/jeffnye3/public_html/auilanguage.org/wp-content/plugins/stripe-checkout-pro/libraries/stripe-php/lib/ApiRequestor.php on line 102″
Now I also set debug to true in my wp-config file, and only see this in the javascript console – see link below:
https://auilanguage.org/wp-content/uploads/2016/02/Screen-Shot-2016-02-19-at-1.31.02-PM.png
The issue is on this page:
https://auilanguage.org/publications/
It only seems to happen when TablePress is active. It seems to happen more on windows than using mac safari or chrome…
- The topic ‘conflict with SimplePayPro for Stirpe’ is closed to new replies.