Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

BrockleyJohn

Members
  • Posts

    1,427
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by BrockleyJohn

  1. The other thread's not much help though, is it. I believe the only way for the order to disappear is for the customer to come back to checkout_payment before the IPN hits. This could happen in the normal flow if they hit an error in checkout_process (eg. because of the cert) or it could also happen if they somehow (eg. with the back button or another open tab) get there by themselves. To get to the bottom of it, I think you're going to have to start digging through the site access logs and figure out what path they took through the site pages. If we know that we might stand a chance of deducing the cause.
  2. Check the settings within the paypal account - if the return URL is wrong you will get that effect if the customer returns to the site before the IPN arrives. Do you still get any paypal orders which do work? Do you get logs of notify_sync events?
  3. Have you got an up-to-date certificate in the ext directory? See
  4. I have just uploaded v1.4 to the addons section. This is a security update - all addon users should apply it. PM me if you want details of what the problem is (not necessary to apply the fix).
  5. @douglaswalker It doesn't get called to create the url in the address bar, but to create links on the page.
  6. There is something distinctly weird going on here, Doug. That should only get executed if the module is being installed. Do you know where it's coming from? Assuming that it's generating the urls properly elsewhere, my best guess is that a callback from a payment module isn't loading settings from the configuration table before the tep_href_link function is called. However another possiblity is that the class is broken and only works if it returns cached urls.
  7. Ignore the ssl test in paypal app it has not worked for anyone for a couple of years. First thing to check is whether your paypal certificate is up to date - see this:
  8. It's in recent phoenix releases. This problem hit UK sites in February but the US is only getting it now.
  9. you can make that text go away by copying the attached image to admin/images/ (used to be core osc)
  10. Here is a quick and dirty (and untested) update which side-steps the issue. There are some extra 'defines' at the top of the file, which you can change if I have missed any or made any tyops in the table names. Some of the code in this addon will be putting its teenage years behind it soon. It was updated to work with early Phoenix which still had the classic 2.3 admin but it has none of the latest Phoenix changes. It definitely won't be responsive and may throw some wobblies. I think there are people running it on 1.0.5.n quick_updates.php
  11. In your paypal app general configuration, check if force TLS1.2 is selected instead of default.
  12. Check that you have the latest security certificate in catalog/ext/modules/payment/paypal/ it should be the one attached paypal.com.crt
  13. Yes, you have told it to treat an unverified transaction as verified and vice versa. I suspect that you are not getting a reply (or an unsuccessful reply) to the verification request to paypal. This is only supposed to happen when the payment has failed and the customer needs to try again, so they end up back at the payment page instead of at the success page. What does the response in the log look like?
  14. What paypal module are you running? PP Standard? PP Standard IPN? The app? Have you checked that your paypal module settings haven't changed? I have seen a store (admittedly 2.2) hacked to send paypal payments to a different account.
  15. The test SSL errors are an irrelevant distraction. It fails for everyone because it tries to connect to servers that paypal created to support the upgrade (ssltest.paypal.com). These servers no longer exist. @glamocanilaktasi if everything works fine in sandbox you just need to make sure your settings are identical in live - both on your site between sandbox and live module settins and also in both paypal accounts.
  16. @ArtcoInc I guess you're talking about the buttons on the selected order in the list view. IIRC it just overrides the link of the first button - or the first yellow one, or something along those lines. There's a config setting for this which you can turn off instead of clobbering the hook. If you want it to pick a different button we'd need to work out a different jquery selector - if you copy the source code of the buttons section from your browser I can figure what it could be. I believe order editor does nothing with customers, addresses and so on, it simply manipulates the fields on an existing order and allows you to change the order products and totals. The place to do what you're asking would be the Order Maker addon which must be where the default address is getting pulled into all three when the order is created.
  17. What paypal module are you using? If standard: Check the paypal log via your admin menus and confirm if you are getting notifications or not - look for _notify-validate [IPN] entries. Do you see the balance displayed on your admin dashboard? That would tell us the app is talking to paypal ok. There will be corresponding successful GetBalance log entries. In your paypal account, go to the settings and check them. This has all moved again. It's now on the drop down from your name, then account settings; check Instant Payment Notifications are turned on. If they are, from that page click through to the IPN History page, check there are entries corresponding to the orders. Try resending one of them.
  18. In case you don't know, IPN (instant payment notification) is a feature so paypal automatically contacts your site to tell it about things that happen with payments in paypal - like it's been paid, if it was an echeque that it's cleared, it's been refunded and so on. It's a security feature making it harder for hackers to steal from you by faking paymennts. If you also run an ebay account and you look at your paypal logs in osc you'll see that it tells your site about those payments too! All of these IPNs trigger the ipn listener in /ext/... if the listener can find a related order it will write a history record that you can see in admin. Now, sometimes when people pay with paypal they don't come back to your site - maybe they don't wait long enough after hitting pay and rush back to looking at porn or their connection drops or whatever. So if the ipn listener gets notified that the payment is there and the order is in the Preparing status, it will go ahead and complete the order, do the stock adjustments, send the emails and so on. If the order is already in the later status (eg Pending), it will just log the history record. For the people that do come back to your site and get there before the IPN, when they go through checkout_process that executes the code in the paypal_standard module and changes the order status, stock levels and sends out emails. So... both files handle setting an order to paid, the stock and so on - but for any given order it was one or the other. If you want to know which it was, you can tell from the history records (if IPN handled it the change of status history is nearly simultaneous with the IPN email). The IPN listener file always handles processing the IPN notification but it may only write a history if the other got there first The standard module always handles the user going through checkout_process to checkout_success but it may not do anything for the order if the other got there first Both routes need to work properly and if you're changing one for some reason you also need to change the other.
  19. That doesn't tell you anything. A working paypal installation also displays those errors. That is because paypal has withdrawn the test servers it is trying to contact so the tests fail for every site.
  20. If you view the source of the page where the script has been included, it looks likely that there is something extra in the string coming out of the draw button function.
  21. It comes from a file you're unlikely to have changed: catalog/includes/modules/hooks/admin/orders_edit_order.php What version of the shop are you running? It occurs to me I've not tested the latest version I posted to the thread on bs3 shops.
  22. @radhavallabh - whatever solution approach you arrived at when you raised this four years ago should still work. If you struggle to get it working on this version, create your own thread to get help on it.
  23. @radhavallabh it needs a lot of changes to get rid of warnings and notices - you should turn them off by changing admin/includes/application_top.php error_reporting(E_ALL & ~E_STRICT & ~E_NOTICE & ~E_WARNING & ~E_DEPRECATED); It's my hope to get a lot more of them eliminated by the next release which will be to go with 1.0.6.0
×
×
  • Create New...