NOTICE: We've Moved to a Ticket System for Support
As of August 31, 2017 (12am EST) our support forums will be retired (read-only), and we will be moving to a support ticket system. This will allow us to better organize and answer support requests, and provide a more personalized experience as we assist our customers.
For the time being, we will leave our forums open for reading and learning while we work on creating a more robust Knowledge Base for everyone to use.
If you are a WC Vendors Pro customer please open a support ticket here. If you are a WC Vendors user please open a support ticket on the Wordpress.org forums.
The information on this forum is outdated and in most instances no longer relevant. Please be sure to check our documentation for the most up to date information.
Thank you to all of our customers!
- This topic has 6 replies, 3 voices, and was last updated 7 years, 7 months ago by
.
-
Posts
-
Hey guys,
I’m running WC Vendors PRO on a site to provide a vendor store and also running the Ignitiondeck plugin to power a crowdfunding platform on the same site. I would like to use Stripe with both plugins to allow project creators to receive pledges and also to allow vendors to receive commissions on sales.
For the site owners, who are taking a percentage on both vendor and project creator activities, I’ve created a Stripe profile and inside that I’ve created two separate accounts, one for the vendor transactions and one for the crowdfunding transactions. I’ve succesfully set up WC Vendors to work with Stripe and vendors can connect from the vendor dashboard fine.
When project creators try to connect via the Ignitiondeck dashboard, I get the following error after they’ve entered their login details for Stripe and are in the process of being redirected back to the website:
Fatal error: Uncaught exception ‘Exception’ with message ‘Error making StripeOAuth request: (400) Bad Request’ in /home4/ned/public_html/wp-content/plugins/wc-vendors-gateway-stripe-connect/classes/lib/StripeOAuth.class.php:346 Stack trace: #0 /home4/ned/public_html/wp-content/plugins/wc-vendors-gateway-stripe-connect/classes/lib/StripeOAuth.class.php(174): StripeOAuth->getTokens(‘ac_97jv5rHNbQ81…’, false) #1 /home4/ned/public_html/wp-content/plugins/wc-vendors-gateway-stripe-connect/gateway-stripe.php(155): StripeOAuth->getAccessToken(‘ac_97jv5rHNbQ81…’) #2 [internal function]: stripe_check_connect(Object(WP)) #3 /home4/ned/public_html/wp-includes/plugin.php(600): call_user_func_array(‘stripe_check_co…’, Array) #4 /home4/ned/public_html/wp-includes/class-wp.php(386): do_action_ref_array(‘parse_request’, Array) #5 /home4/ned/public_html/wp-includes/class-wp.php(725): WP->parse_request(”) #6 /home4/ned/public_html/wp-includes/functions.php(963): WP->main(”) #7 /home4/ned/public_html/wp-blog-header.php(16): wp() #8 in /home4/ned/public_html/wp-content/plugins/wc-vendors-gateway-stripe-connect/classes/lib/StripeOAuth.class.php on line 346
It looks like it’s trying to connect back to the WC Vendors plugin rather than Ignitiondeck. I’ve checked all the API keys and client IDs for both the plugins and Stripe accounts about a dozen times now and they are definitely paired up correctly: Stripe Vendor Account to WC Vendors plugin and Stripe Crowdfunding Account to Ignitiondeck plugin.
Any idea what could be causing this? I’ve asked for support from both Ignitiondeck and Stripe and I’m hoping that by speaking with everyone I might be able to piece together what’s going wrong here.
Any ideas you have would be greatly appreciated!
Thanks,
Chris.It is quite likely that the Stripe classes from the two plugins are conflicting.
See what Stripe has to say- commonly using two Stripe plugins – and these are both Stripe connect, I believe – does not go well.I would use Galaxy Funder instead. And then download our free simple auctions integration and use that as a template to add in the extra fields for your crowdfunded products. Now, you’re a few plugins lighter, your add/edit product form is cooler, and you dont have any conflicts with Stripe! 🙂 (PS — One Stripe client per website, more than that, and booooooom)
Thanks for the advice Anna and Ben,
I may follow up on the Galaxy funder, but right now we have Ignitiondeck configured mostly the way we need it and I’ve already trained the site owners on how to administrate it.
Do you happen to know if two Stripe Connect clients could be run in conjunction if I moved the crowdfunding functionality to a subdomain?
Thanks for your help and advice, it’s the most useful I’ve received from everyone I’ve contacted.
Cheers,
Chris.Always happy to help, it’s what we try to be here for most of the time. 😉
I would implore you to try Galaxy Funder, despite your resistance. I think you’d be flat out amazed at how easy it would be to incorporate it into your Pro add/edit product form. It’s nothing more than a few meta keys. I did an integration of it a few years ago — before Pro was around — and tied it into WPUF at the time. Pro would be even easier if you followed the simple auctions integration template.
We will have more “out of the box” integration plugins for Pro in the coming months. This would be more unusual and unpopular of the other ones of course, but certainly will be on our list to make a bit easier to non-coders, too.
If you moved crowdfunding to a subdomain, then you’ve got issues with needing two user accounts on two sites since you cant multisite woo and share user accounts or orders and things like that. It’d get messy fast, although if you’re able to do this seamlessly the entire Internet would love to know how. 🙂 That’s why I recommend Galaxy — Just one plugin new, you get to deactivate two? three? four? other plugins, and your interface is all perfect in one spot and no bullshit. It just works. Sure, cost a bit more to do it now, but……….
Hey guys,
The people over at Ignitiondeck took a look at the conflict my site is experiencing with the Stripe Connect gateways and they came back with this:
“I’ve forwarded the information to the developer to take a look at. Here’s what he found:
Line 143 of gateway-stripe.php:
if ( isset( $_GET[‘scope’] ) && ! empty( $_GET[‘scope’] ) && isset( $_GET[‘code’] ) && ! empty( $_GET[‘code’] ) ){This function is instantiated via https://codex.wordpress.org/Plugin_API/Action_Reference/parse_request, basically whenever there are $_GET or $_POST params. WC Vendor’s function does not use its own $_GET var to differentiate between other apps that might use the same scope/code $_GET vars and this is resulting in the conflict that you are experiencing.”
My client has resolved to pay project creators manually for the time being. I’m just passing this info on to you in case in can help with the future development of your PRO plugin.
Cheers,
Chris.
- The forum ‘Stripe Commissions & Gateway Support’ is closed to new topics and replies.