|
Thayne Rigby
|
June 6, 2013 at 11:48 am
I have a client very interested in buying your plugin, but they would like to use wepay.com. In the forum I see a lot of people seeming to have issues with wepay integration. Is it working? Can anyone assure me that it works before we buy. Thanks
|
|
Sidney Harrell
|
June 6, 2013 at 12:00 pm
The current release of EE has an issue with using wepay with the Multi-Events Registration add-on, but it has been fixed in the next version of EE. We can either give you the code change (it’s a single line of code that needs to be inserted into a file) or email you the corrected files. I’m not aware of any other issues with our wepay module, but since it is a gateway that we support, we would be happy to work with you to address any issues that arise.
|
|
Bill
|
June 6, 2013 at 12:16 pm
My client has now told me that they have an existing license key. Are they entitled to that line of code fix?
|
|
Sidney Harrell
|
June 6, 2013 at 2:59 pm
absolutely. insert in between lines 5 and 6 of wepay_vars.php:
if (empty($event_name)) $event_name = "Event number #" . $event_id;
|
|
Bill
|
June 7, 2013 at 1:37 pm
We just purchased a new license specifically to see if the new version of event espresso would fix the issue we have with wepay integration. But it will not authorize the application. We are getting an error “Application is not approved to create accounts” I know you said you support this gateway, but what is the proper way to get support to help now that we have a new license? Thanks
|
|
Bill
|
June 7, 2013 at 1:42 pm
You can see here, that the option in the dropdown is not the correct name of the wepay account, but I can’t get it to clear this out and there is no other option. I dont know where this dropdown option even came from ==> (edited to remove identifying information)
|
|
Sidney Harrell
|
June 7, 2013 at 2:32 pm
Where are you getting the error: “Application is not approved to create accounts”? There are a series of actions that you have to take on the wepay.com site before you can take the actions on your site to get it set up. On the wepay.com site you have to:
1. Sign up as a user
2. Add an account to your user
3. Register your instance of Event Espresso as an application in your WePay user profile
|
|
Bill
|
June 7, 2013 at 2:45 pm
I have an user, I have an account, I have clicked on api and added an api application – named it what I was told to name it “event espresso” , got the client id and client secret, the application in wepay says it is live, I added the info to the payment settings, clicked update wepay settings, then clicked authorize application and then am taken to wepay where I get a red bar error that states “Application is not approved to create accounts”
drop down does not display the correct account and I can’t get it to change?
what am I missing?
|
|
Bill
|
June 10, 2013 at 2:02 pm
We have now purchased a priority support ticket. But after doing so, there is no form or way of communicating to you. It would make sense to have a way of actually utilizing our priority time?? Can you please have someone reach out to us so we can get wepay working.
|
|
Josh
|
June 10, 2013 at 2:18 pm
Hi Bill,
I checked with Sidney on this. It appears that WePay’s API has changed since the last time the Event Espresso integration has been updated. He is looking into it. We’ll update here once we find more information.
|
|
Sidney Harrell
|
June 10, 2013 at 3:15 pm
I found this in wepay’s new documentation: “Before creating accounts for users in Production, your app must be approved. Apply from your application’s dashboard.” and this: “Application approval needed
Before creating accounts for users on our Production server, your app must be approved. Visit the API Keys tab in your dashboard to request approval.”
Can you check there in your account to see if you app has been approved yet? I’m working on updating our wepay module now to work with these changes that wepay has made to their api / process.
|
|
Bill
|
June 10, 2013 at 3:56 pm
Is there any way to clear out any previous info from the wepay integration plugin. I have a dropdown in the wepay section that somehow displays incorrect info – Im not sure if the client previously added this, but it is not tied to the new wepay account. How can I refresh this ==> http://screencast.com/t/NT74IDG2GsMT
|
|
Sidney Harrell
|
June 11, 2013 at 3:37 am
The Available Accounts list is updated when you return from Wepay after having authorized your application. When that happens, the “Authorize Application” button will also disappear from below the “Update Settings” button. To get the “Authorize Application” button back, you have to make some change to either the client id or the client secret and then hit the “Update Settings” button. So what I’ve done in the past is just add a space at the end of the client id, update, remove the extra space, update again, then you can reauthorize and it will update the account list.
Have you tried setting up an account on stage.wepay.com to test everything out while you are waiting for Wepay to approve your application on their production server? I ran through the process with our test account on stage.wepay.com, and it looks like our wepay module is working.
|
|
Bill
|
June 13, 2013 at 5:03 pm
I guess we are about to give up on event espresso, we bought a brand new license and then a priority support ticket but have not heard anything since we initially reached out about whether the wepay api is going to work in the near future. Can we get some kind of update before we give up guys. Thanks
BTW – really need some kind of communication besides the general forum when people pay for support.
|
|
Josh
|
June 14, 2013 at 8:40 am
Hi Bill,
Did you get the email that Sidney sent you yesterday? If you’ve requested an app approval with WePay? If so, have you checked in your WePay account to see if your app has been approved yet?
|
|
Bill
|
June 14, 2013 at 10:11 am
I keep hearing you guys ask if my app is approved. There are three options on the bottom of the wepay api section seen here ==> http://screencast.com/t/ND5aiqJaAUKN
I had done the first one and the application was “live” ==>http://screencast.com/t/2JsO45YcXK
But then I began to wonder if I needed to apply for the other two? But no one mentioned anything about OAuth2 or the need to Tokenize credit cards?? Is this required?
I have now applied for the OAuth2, but I was not sure whether I needed to Tokenize credit cards? Do I?
|
|
Josh
|
June 14, 2013 at 10:29 am
Hi Bill,
The first screenshot says the approval is pending. Since Event Espresso doesn’t use the WePay Tokenization feature you don’t need to apply for it.
|
|
Bill
|
June 14, 2013 at 3:42 pm
I talked to wepay today and they claim my application is in a state that should not be giving this error. I updated the plugin today and that allowed the dropdown to choose different accounts which it could never do in the past. I removed and re-added the IDs etc and tried to authorize application and there was no error, but there was also no confirmation and the authorize button does not fade out and wepay is still not a payment option.
|
|
Sidney Harrell
|
June 17, 2013 at 11:14 am
WePay uses OAuth2 to let Event Espresso access to the API to retrieve the list of accounts. I created an account on wepay’s production server, my OAuth2 status is “pending” and I’m getting the same error when I go to authorize: “Application is not approved to create accounts”. I’m getting the same error when I hit the “Authorize Application” button from your payment settings page.
|
|
Sidney Harrell
|
June 17, 2013 at 11:51 am
I figured out a way around the problem. I tried some modifications on my test server so I could copy the access token and account id directly from the wepay’s api settings page to the EE payment settings page and it looks like it will work. I’ll get the modifications uploaded to your site so you can get up and running.
|
|
Bill
|
June 17, 2013 at 12:04 pm
That would be great
|
|
Sidney Harrell
|
June 17, 2013 at 3:00 pm
I got the file uploaded to your site. You’ll need to log in to your wepay account and go to the API Keys page where you got the client id and client secret from. You’ll need to copy the account id and access token from that same page and paste them into your wepay settings on your site.
|
|
Bill
|
June 17, 2013 at 3:06 pm
I went in and added the info. And it appears to be working. I really appreciate your support on this. I hope to use your software on other clients sites. Will this fix be incorporated into your plugin going forward? Thanks again.
|
|
Bill
|
June 17, 2013 at 3:10 pm
I may have spoken a bit too soon. This is happening when we click submit ==> http://screencast.com/t/Gv0YGOHTKBx
Opens a new page but no button. It worked once, but now it is doing this.
|
|
Sidney Harrell
|
June 17, 2013 at 3:42 pm
looks like the curl request to wepay is timing out. looking into it now
|
|
Sidney Harrell
|
June 17, 2013 at 7:50 pm
Looks like it’s working now. When I was working on testing it to find the problem, it seemed like it was a problem with your server connecting out to the wepay server. I changed the url that your server was connecting to to “google.com” and https://google.com” and those both worked. I tried taking all the post content, the url, and the headers and plugged them into the firefox poster plugin and the wepay server returned a good response, so it didn’t look like a problem with the request or wepay’s response. I cloned your site files and database onto my server so I could test whether it was a problem with your server’s firewall, and it worked on my server. I went to recheck it on your server, and of course it’s working now. Let us know if it starts flaking on you again.
|
|
Bill
|
June 18, 2013 at 9:20 am
It does seem to be working now. I really appreciate your willingness to support your product. I run into a need for your software often and wepay is my favorite option for taking payments nowadays – so simple and no hassle with paypal etc. Have you changed the wepay integration for future installs to avoid the need to get an application approved by wepay? I will probably be buying a new license next month if so, and more in the future. Thanks for your response.
|
|
Sidney Harrell
|
June 18, 2013 at 9:57 am
Yes, the changes we made have been added to the 3.1.34 version. You might want to make a copy of the gateways/wepay/settings.php file in case a hotfix of 3.1.33 goes out and changes it back. Even if it does, it should keep working, since the account id and access token are saved in your settings.
|
|
Bill
|
June 18, 2013 at 10:00 am
Thanks I will do it.
|
|
Bill
|
June 24, 2013 at 3:24 pm
Hi we are having that curl request timeout issue again. The shopping cart has a white screen background, black text, no css, and gets stuck on the Payment Overview page.
It’s been timed out all day. Do you guys have any idea how to prevent these curl request timeouts?
|
