|
Robin
|
December 21, 2012 at 9:06 am
I’ve been trying to figure out why the wrong theme is being applied to my thank you page when the rest of the gateway testing is working perfectly, and I just found something interesting. When I checked the javascript console in my latest test, it is referencing the theme for the live parent site, not the dev subdomain. Additionally, I haven’t yet configured HTTPS for the parent site – just for the dev site – so it’s giving me error messages about insecure content. I’m going to enable it for the parent site, but that still doesn’t help me understand why it’s looking in the wrong place and applying the wrong theme. Any suggestions for something to examine or try?
Thank you!
Robin
|
|
Robin
|
December 21, 2012 at 10:25 am
I just noticed something about this problem that might help but I’m still stuck.
I’ve modified the authorize.net SIM interface to use eProcessing Network. So far, the charges go through perfectly – the part that’s not right is the return to the Thank You page. According to their instructions for their authorize.net emulator, other than the account information, this is what needs to be done: “Typically all a developer has to do is change the URL they access from https://secure.authorize.net/gateway/transact.dll to
AIM Users: https://www.eProcessingNetwork.Com/cgi-bin/an/transact.pl
SIM Users: https://www.eProcessingNetwork.Com/cgi-bin/an/order.pl”
I just noticed that the return page (I’ve tested in both IE and Chrome) is actually coming back to the first link for the AIM, and not the one I put in for the SIM. I have checked and checked, and I have only put in the SIM return URL. I have no clue how this can be happening, or where next to check. I did call them, but didn’t get much help. Any ideas? We are talking about Authorize.php, right? Did I miss a file?
Thank you again for your help.
Robin
|
|
Josh
|
December 21, 2012 at 2:55 pm
Hi Robin,
Is it the case where the one site was copied over to the other? In that case, it may be that the gateway settings on the one site are pointing to the other. If you look in the Event Espresso>Payment settings for the gateways that you have set up, it will display a relay response URL. You can verify that first, then go into the merchant account settings and make sure you have the correct response URL set. I can imagine this can also happen if the response URL set in the merchant account is set to a URL on the other site.
|
|
Robin
|
December 21, 2012 at 4:03 pm
Thanks, Josh.
To my knowledge nothing was copied over anything, but I’ve been wrong before. I had totally removed all files and created a new database for the dev site, so pretty much started from scratch.
I just checked the payment settings page. The images are referencing a development site url, and the relay response URL is also referencing a development site page. In the Authorize.php file, I had set the payment URL to the one they (ePN) said to use (and it’s working properly for the payment, as I mentioned) and there’s no way for me to set a response URL in my merchant account – I logged in to check. It’s only using what’s passed in as an argument in the function call. This is why I was wondering whether I may have missed something in another file that I should be changing?
So, basically I have two problems: the css is wrong (using the live site css instead of the subdomain dev site css) and the return page is wrong. I don’t know how to fix either, but I’m guessing that they may be related – if it’s oriented to get the right css, I’d hope it would also grab the right page.
Any other suggestions?
Thank you again-
Robin
|
|
Josh
|
December 27, 2012 at 8:56 am
Hi Robin,
I’m sorry for the delay. I can’t think of any other suggestions for this, partly because the ePN gateway isn’t one of the gateways we’ve built, so we don’t have a means to support it.
It sounds like there is a difference between how the ePN payment page pulls together the paths from your dev site. The images are likely getting pulled from an absolute URL, but the stylesheet may be a relative URL, and it’s not looking in the sub domain, and looking at the top level instead.
|
|
Robin
|
December 27, 2012 at 10:45 am
Thank you, Josh. I suspect you are right. After fighting with it for far too long (since I wanted it live already), I met with my credit card processing guy over coffee this morning (I would gladly recommend him to anyone looking for one) and we decided to switch me to the authorize.net gateway. It should happen this afternoon.
Once that change is made, and I can test again, I’m hoping that it has some weird connection to the duplicate events in the cart problem I’m also having. If that would miraculously be cured as a result of the change, I’d be one ecstatic camper. If not, I’ll be back here on the forum continuing to seek answers!
Happy New Year-
Robin
|
|
Josh
|
December 27, 2012 at 12:33 pm
Hi Robin,
I would suspect that the reason you are seeing duplicate events in the cart is because the volume discounts add-on is activated. Is that the case? If so, there is a bug where if an event has 2 categories, and volume discounts is active and set to 1 category, a duplicate event displays in the cart.
|
|
Robin
|
December 27, 2012 at 12:40 pm
Thank you so much!!!!!!!!!!!
I’m sure that’s it!!!!
It’s been driving me crazy – couldn’t find anything in the forum to explain that and had no clue what to try. If you were here I’d give you a hug for this one! I’ll play with my categories and do a work-around.
Happy New Year!
|
|
Robin
|
December 27, 2012 at 12:58 pm
by the way, I think that bug is a good reason to give more thought to my suggestion in a different thread: https://eventespresso.com/topic/multiple-volume-discounts-questions/. Don’t you think that might help solve that problem?
|
|
Chris Reynolds
|
December 27, 2012 at 3:47 pm
Hi Robin —
The bug has been fixed (not sure if the updated version is on the pre-release downloads page yet, but you can try re-downloading and see if that fixes it), but your suggestion does make sense. I suspect it would require a significant amount of overhaul of the code to implement this and most of our dev team is trying to focus on Event Espresso 3.2.
|
