Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › eStore – PayPal IPN not working, emails not being sent. IPN Debug Log is Blank
Tagged: estore plug in, PayPal IPN
- This topic has 11 replies, 4 voices, and was last updated 10 years, 1 month ago by brewermfnyc.
November 10, 2012 at 12:07 pm #7870
The PDT function is working. Customers are being taken to the product details page for download, but emails are not being sent to the buyer with the necessary information. The customer info is also not being logged in wordpress. The Debug IPN log is blank. Please advise.November 11, 2012 at 1:46 am #51237IvyMember
Please see the following post as this should help you with the issue you are having.
https://support.tipsandtricks-hq.com/forums/topic/what-to-do-if-the-debug-file-is-emptyNovember 16, 2012 at 5:59 pm #51238
I followed everyone of those steps, and the debug log did show the line when i manually visited the PHP file, but still after a test, there is nothing posting from the PayPal transaction. IPN is turned on in PayPal, PDT is turned on, and auto-return is turned on.November 17, 2012 at 4:01 am #51239
There can be nothing else outside those checklist items that can affect it. Please post a link to your page where you are using the plugins and I will check it with you and get to the bottom of this.November 19, 2012 at 3:33 pm #51240
Here is the page I am using this on. If you need it, email me and I can share log in details with you:
[http://www.brandonhensinger.com/the-alive-sales-rep/]November 20, 2012 at 4:29 am #51241
Thank you. I have done the testing and it looks like step 5.a (refer to the checklist I shared above) is your problem.
In summary, your server is rejecting PayPal’s IPN notification (it is not letting PayPal to send the data to the plugin).
Please read checklist #5 again from the following page which has suggestions on what to do to get this fixed:
One of the main reasons for this to happen is when you use a firewall/security plugin that blocks PayPal’s IPN. Do you have any such plugin installed? The other thing that cause this issue is when the server is not configured correctly to receive PayPal’s IPN. Contact your hosting provider and tell them about this issue and they should be able to help.November 27, 2012 at 3:43 pm #51242
I will contact Network Solutions about this. I do not have a firewall/security plug in installed. I will let you know what happens.
Update: Got my hosting provider to fix the PayPal IPN being blocked issue. Now it is working fine.February 24, 2013 at 3:05 am #51243
I’m having this same issue with a new install of WP eStore. Emails not being sent, nothing logged in the debug page, no customers listed in the WP eStore admin area. PayPal is completing the transactions and money is being transferred.
I’ve worked my way to step #5 on this page: https://support.tipsandtricks-hq.com/forums/topic/what-to-do-if-the-debug-file-is-empty
I have the plugin installed a couple times on the same Rackspace Cloud Site account (yes, I’ve bought a few licenses for different domains!) but in this one case the transactions will not send emails and I’m getting nothing in the error log. I followed the directions about IPN and I see that PayPal is unable to connect to the server.
Now here’s the catch – to check it out I looked at my other working stores and PayPal can’t connect to them either! Why would one version not work?
The only difference is the version of WP eStore, so I’m thinking maybe something changed in the most recent version of eStore that IPN is now necessary? I’m at a loss. Thanks for any suggestions.
Rackspace says they have nothing set up to block PayPal’s IPN requests.February 24, 2013 at 4:01 am #51244
If you have worked your way up to step 5 then there are only two reasons why PayPal’s IPN would be blocked by your server/site.
1) Server setup issue
2) You have a plugin that is blocking the PayPal IPN
If you go through the topics in the “Example” section of the following post you will see that every single time it has been one of the above mentioned two factors that resulted in PayPal IPN being blocked/rejected (go thorugh those posts and you will find helpful ideas):
So, just as a test, disable all your plugin(s) and do the IPN connectivity test. Also, check your .htaccess file to make sure you don’t have any condition there that would block PayPal IPN.February 25, 2013 at 4:55 am #51245
Thanks for getting back so quickly. I’ll try disabling the plugins and see what happens with a 1¢ purchase. I don’t have a PayPal sandbox set up.
What is so strange is that IPN was turned off on another site hosted in the same account on the same server, but the store works fine there. When I turned IPN on (just for kicks) I got an email from PayPal saying they couldn’t connect. The store still works great there so I guess I’ll just turn IPN off and leave that be… for now…February 25, 2013 at 5:15 am #51246
OK. I think I found the problem…
When I look at the IPN history, PayPal says the Notification URL is:
/wp-content/plugins/wp-cart-for-digital-products/paypal.php (with no domain)
So I’m guessing this would be why it’s not working! Where do I change that setting in the plugin? I wonder why I’m missing the domain part of the URL?February 25, 2013 at 6:15 am #51247
Sorry for the multiple responses to this, but I thought it would be useful to someone.
Rackspace Cloud Sites has a new WordPress install wizard that (along with installing WP in a few easy clicks) automatically installs a plugin called Root Relative. This plugin replaces WP’s absolute links with root-relative links.
So [http://www.domain.com/path/to/file] becomes /path/to/file
This is with the intention of making the transition easier from development to production servers. That makes sense to me – moving WP to another server has always been a pain – but unfortunately your eStore plugin uses the same method to tell PayPal where to send the IPN info. So as a result it’s just sending PayPal a root-relative link for the IPN connection:
The tip off was an uneditable WordPress Address (URL) in the General Settings for the WP installation. I never actually activated the plugin, but still I had to go in to the wp-config.php file and remove the following lines that the Root Relative plugin inserted:
define('WP_HOME', 'http://' . $_SERVER['HTTP_HOST']);
define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST']);
Just tried a purchase and that fixed it! It was a server issue even though the server folks said it wasn’t. Again – sorry to be so long winded, but I hope that helps someone.
- You must be logged in to reply to this topic.