Magento Submit Order button not forwarding after security patch update - magento-1.7

Magento Submit Order button not forwarding when Credit Card (Authorize.net Direct Post) payment method selected after Magento security patch update
Few days ago I have installed Security patch 8788 (PATCH_SUPEE-8788_CE_1.7.0.2_v2-2016-10-14) for Magento ver 1.7.0.2 successfully. But I found that, Order is not submitting when the Credit Card (Authorize.net Direct Post) payment method is selected from the checkout page. When hit submit to finish the checkout, all it does it keeps loading and nothing happens. See below attachment.
N.B: I didn't found such type of problem in the list of SUPEE-6788 TECHNICAL DETAILS. I have checked the system.log and exception.log but nothing found.
Also I have checked that the old version works perfectly before security patch update.
Any ideas why this might be occurring? Please help me to solve the problem.

Check your console log error, It seems like Checkout ajax request is not working.

Related

Can you generate new PayPal IPNs for past (IPN-less) transactions?

So I'm working with a system that uses the legacy NVP/IPN thing from PayPal. The IPN listener URL wasn't set up properly and so they ran a couple weeks worth of transactions with no IPN data coming back. I've set it up properly now, but I'm wondering if there is a way to regenerate that last couple weeks that never had any. Whenever I go to the IPN history page, I just get a this feature is not available message. I know it's now working because I can see three transactions in our database (that come through the IPN listener)
On another note, if I go to the download history page and try to click download, the page refreshes but nothing happens. I don't get a report or anything, any idea why?
It sounds as though you're looking for the IPN history page, where you can resend IPNs: https://www.paypal.com/us/cgi-bin/webscr?cmd=_display-ipns-history
Late edit: changed title to better reflect the true question (it's not about regenerating IPNs). And the answer is it's not possible. Instead, for past IPN-less activity one must manually import a CSV obtained from www.paypal.com account home -> Reports -> Activity Download
This is the URL: https://business.paypal.com/merchantdata/reportHome
If once in the Activity Download, "Create Report" does not work properly (e.g. "nothing happens"), contact PayPal's support for assistance as that is not normal.

Paypal not working in OJS3.1

Recently I have created my e-journal’s website with OJS 3.1 (Fresh installation).
I have configured my Distribution Settings -> Payment -> Paypal Payment Settings
Created a Rest API in Paypal and placed every detail under Account Name, Client ID and Secret. But the paypal payment is not working. Everytime when someone tries to make a purchase it shows a blank screen.
Please help me. I there any problem with the Paypal plugin ? I have also used OJS 2.8 but there was no issues like this and everything was working fine.
Have you checked your PHP error log? A blank page typically means something is captured there.
If you see something like...
PHP Fatal error: Interface ‘Symfony\Component\EventDispatcher\EventSubscriberInterface’ not found in /var/www/vhosts/my_domain/httpdocs/plugins/paymethod/paypal/vendor/guzzle/guzzle/src/Guzzle/Http/RedirectPlugin.php on line 20, referer: http://my_domain/index.php/EI/user/register?source=%2Findex.php%2FEI%2Farticle%2Fview%2F16%2F14
...you may be running into https://github.com/pkp/pkp-lib/issues/2996.

Sorry — your last action could not be completed

I have confusion, that I have integrated recurring payment system.
It was working well before, 3 days.
Form 2 days I am getting error
Sorry — your last action could not be completed
When I am trying to login.
It login successfully but now shows the payment confirmation page.
What should be the issue?
I am using sandbox for now.
Let me know if you want more details.
please check or do the following
Use a separate browser page for logging into sandbox.paypal.com as you stated you are trying to 'login'
I have noticed periodically that sandbox.paypal.com loads my live credentials when a previous paypal.com session was activated; an apparent cookie issue
If you have a password / user id client like fast pass, etc; make sure to verify the password that's injected into the fields in your options of the pw/user ID client
Please take note as I am replying to:
Sorry — your last action could not be completed When I am trying to login <-- Not to recurring payments system not working as it appears that these are 2 different issues. If not, please clarify for me

PayPal Sandbox account new design, can't login

Since PayPal changed their website for developers I can't use it anymore. Before I had some test accounts setup and I was able to go in, create buttons and so-on. Now I have imported my previous accounts but I can't log into them, just getting The requested resource () is not available. 404. If I clear browser cache and cookies, it just tells me to login (using my developer-login details, not the test details) and I can't come in. Their support says clear cache and it works... Stupid PayPal.
Anyone knows what to do?
I tried to update Chrome and Firefox to latest versions and then cleared all cookies/cache then logged into developer account and then tried to login to test accounts.
I always get this 404 message: http://snag.gy/rL5t2.jpg
HTTP Status 404
type Status report
message
description The requested resource () is not available.
Apache Tomcat/5.5.15-150
We're aware of this issue and are working on getting it resolved as soon as possible. In the interim, you can manually remove the '/se/' from the URL included in the screenshot, which will bring you to the correct page (https://www.sandbox.paypal.com/webapps/mpp/home).
Sorry for the inconvenience. We'll get this fixed soon!

Paypal Sandbox IPN error

After paypal updated their interface (sandbox.paypal.com for example is not working, now you have to go to developer.paypal.com) many of the things are not working: 2 of them are particularly frustrating and I was hoping someone here knew how to get around them:
Am I the only one whose sandbox customer test accounts are not able to make purchases? The transaction page says they are not available.
IPN validation is not letting me send a https request. When I do it says there is something wrong with the server name. Yesterday however before the update I could get verified status. If I dont put https, now my handler gives me an invalid responde status, code: 400. What does it mean?
To fix the HTTP 400 error, follow the instructions in https://www.x.com/content/bulletin-ipn-and-pdt-scripts-and-http-1-1 and update your code to pass "Host" information. Ideally, things should work with just the recommended changes from the above link. Apparently, thats not the case. Here is a fix from one of the PayPal MTS person - PalPAL sandbox IPN processor rejecting all messages?
Remove the "cmd=notify-validate" option from the validation URL. I tried this and it worked. Though it doesn't return the right string, atleast it doesnt break with the 400 error.
While we wait for a fix from Paypal, I wonder how a company like PayPal can cause such a huge blunder and not post anything on their status page - https://www.x.com/developers/paypal/documentation-tools/site-status/pp-cri. It just makes you think that even smaller companies can do a better job than companies like PayPal.
For the code:400 issue, you have to update the post to version 1.1. That information is located here.
https://www.x.com/content/bulletin-ipn-and-pdt-scripts-and-http-1-1 in this bulletin.
However, as I posted before the asp.net example uses a call, that does not exist, so I was only able to get mine partly working. After fixing this, the servers appear to be rejecting calls to https, or the cert they have installed is invalid.
Action Required before February 1, 2013
Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” header in the IPN postback script. In addition to this bulletin, these merchants will be notified via a direct email.
Alright, seems to be fixed!
If you are having trouble logging in, like suggested above, clear cache and cookies and try again.
Regarding the error 400, seems to have been solved by paypal!