Jump to content

Ian-San

Members
  • Content count

    761
  • Joined

  • Last visited

Everything posted by Ian-San

  1. My experience (belief ??) is that Google visits twice - once to capture urls and the next to index them. So it is possible you will get another visit in a day or so to create the listings.
  2. I had more than 250,000 hits from all search engines last month, with under 7,000 listings on Google - and not a sid in sight and no reported log on problems. This compares to October and November last year when I had a similar number if hits from Google in one week that resulted in 70,000 pointless listings all with sids. I reckon I can call this a success. :D
  3. Ian-San

    [Contribution] SID Killer v1.0

    My two cents: I have discovered that a unique feature of all spiders seems to be that getenv('HTTP_ACCEPT_LANGUAGE') is null. ie. spiders do not have a browser language. However, I am not sure that every valid user does have a browser language or under what circumstances, if any, a valid user could use a browser that does not have a language??? Seems to me that this could be used somehow. Any ideas?
  4. Ian-San

    Worldpay 4.0 - Version 1.0

    Nick - anyway a nice code snippet, you should add it to tips n tricks as it could be useful elsewhere.
  5. Ian-San

    Worldpay 4.0 - Version 1.0

    Rather than comment out, you would need to replace it with an auto-redirect to checkout_process I think.
  6. Ian-San

    Worldpay 4.0 - Version 1.0

    very true I think Personally, I would just comment out the continue button on success and then it should work fine - even if it is against the wp rulebook the wpbanner is not really essential as you show success once you get back to checkout success.
  7. Ian-San

    Worldpay 4.0 - Version 1.0

    Do the problems with WP never end??? This morning as I was solving another issue - I discovered that when using non-western character sets, the ',' separator in the number format gets converted to %2C. So 13,000 becomes 13%2C000 which then fails at WP - I then checked on other similar issues. I discovered that whilst your version eliminates the ',' here: $OrderAmt = number_format($order->info['total'] * 100 * $currencies->get_value($currency), 0, '','') ; $OrderAmt = $OrderAmt /100 ; instead, you create another potential problem which is that you force all order amounts to have 2 decimal places. Fine for those currencies that have them but doesnt work for those that do not. e.g. 13000.01 yen seems to fail at WP. So I suggest (and it is untested on your snapshot) using: $OrderAmt = number_format($order->info['total'] * 100 * $currencies->get_value($currency), $currencies->get_decimal_places($currency), '.', '') ; instead. Here the decimal places will be correct for the currency used and the decimal dot (the default in western character sets) used. For currencues that do not have decimal places, the dot is not used anyway so no error.
  8. Hi I didnt use the random number solution as it was too complex to identify unwanted guest accounts. Instead, I just prefix the old guest account emails with @_ when a new one is created for the same customer. This seems to work just fine.
  9. Graeme Many thanks - your reply put me in the right direction. If anyone is using a pre-November WorldPay snapshot, and want to see the payment type in the customer email, just change this line in worldpay.php: $this->code = 'Worldpay'; to this: $this->code = 'worldpay'; Yep, just the capital 'W' - it was a stupid mistake. :cry:
  10. Graeme I have noticed that the pre-november WP modules do not show the Payment Method at the end of the customers confirmation email. Does this happen with your version? I am trying to understand if this is a fault with the old modules or a general fault with using WP. Thanks
  11. Ian-San

    Worldpay V3c

    If you want, you can PM me your WP access code and I will try it with my store set-up. If it works for me, then the problem is your store, if not then it will be WP?
  12. Ian-San

    Worldpay V3c

    No, I dont and have no problem.
  13. Ian-San

    Worldpay V3c

    This is how mine looks: Under configuration options in WP, you should see some extra form entry fields: Fill in the Callback url with http://<wpdisplay item="MC_callback"> Do NOT check the box: Callback enabled? I also have this box checked as well: Use callback response? Probably it is not used as the Callback enabled box is not checked but you can never tell with WP. Also, you would think that the Callback url would not be used if callback is not enabled but again, you cannot be certain. My belief is that it passes the variables to the C / Y files as callback is not enabled. Sorry there is some confusion in these posts but that seems to be the nature of using WP - nothing is very clear. I dont know if this will solve your problem but it is one more step done ...
  14. Ian-San

    Worldpay V3c

    I guess that is the problem! The substitution in the C / Y files is not being done. I think the next step is to ask WP why you do not have a Callback option available to you?
  15. Ian-San

    Worldpay V3c

    Yes - it all looks fine. I remember that WP made some changes recently, try putting this code into the callback url in your WP admin: http://<wpdisplay item="MC_callback"> and turning callback back on?? I dont know why it should work but it is worth a try!
  16. Ian-San

    Worldpay V3c

    Then the last thing you can try is to replace the url for WP in the form post with a 'mailto:you@youraddress.com' so that instead of posting to WP you get an email back with the results of the post. This looks like a virus to your system..... Then you can check the variables being sent to WP see if you can spot what is missing or wrong. In particular, check the 'MC_' variables make sense.
  17. Ian-San

    Worldpay V3c

    Okay, next thing to try is: Can you get back to your OS store from WP by using the back button and still see your order (you may need to refresh the page). If this works, then the problem must be that the MC_successURL and MC_failURL are going wrong somewhere.
  18. Ian-San

    Worldpay V3c

    Make sure that you have the OS supplied Result C / Y forms loaded to WP and that you have NOT selected Callback. Your problem is that the C / Y forms are not loading - they do this is a planned error situation - WP tries to callback, fails and so tries the C/ Y forms. These have a built in auto-redirect that takes you back to the store. Without them, you will hang on WPs default banner page.
  19. Ian-San

    Worldpay V3c

    You should see the 'Order Success' page in your store when the customer is returned to it from WP if the transaction is successful or the payments page if it is not. What page do you get?
  20. Ian-San

    [Contribution] Worldpay V4 Beta

    Brilliant - works a treat! Well done. Probably you need to expand on the words displayed to incorporate WP's mandatory messages: e.g. Thank you, your payment has been cancelled Merchant's Reference: {your Shop Name} Please contact WorldPay immediately if there has been a problem making your payment. etc but this is a trivial issue.
  21. Ian-San

    [Contribution] Worldpay V4 Beta

    Graeme Looking at this again, are you not just assigning the string "<WPDISPLAY ITEM=transStatus>" to $WorldPayResult. ie you are not assigning the value of <WPDISPLAY ITEM=transStatus>? Should you not be using something like this: if ($HTTP_POST_VARS['transStatus'] == 'Y') { Your Action goes here; }
  22. Ian-San

    [Contribution] Worldpay V4 Beta

    Graeme Does it also print 'Fail' as well or does the if statement work okay? If so, why do you need the switch statement - can you not just get rid of it?
  23. Ian-San

    [Contribution] Worldpay V4 Beta

    Is it possible that the switch statement is assuming a logical test? ie it assumes that the 'Y' means Yes, looks for 'No' and so defaults to 'default'?? Try putting in an if statement: $WorldPayResult="<WPDISPLAY ITEM=transStatus>"; if ($WorldPayResult == 'Y') { define (WPRESULT, 'Success'); } else { define (WPRESULT, 'Fail'); }; print WPRESULT; switch(WPRESULT) { case "Success": print "Worldpay authorised<br>" ; break ; case "Fail": print "Worldpay cancelled<br>" ; break ; default: print "not recognised - after puting double quotes<br>" ; // Always goes here! }
  24. Ian-San

    Japanese Yen Problem with PayPal IPN .96

    Great - actually I just added this code myself - to make sure that I do not get the same problem as you - and it seems to test out okay.
  25. Ian-San

    Japanese Yen Problem with PayPal IPN .96

    It is part of the currencies.php class module in the new checkout. I dont know if it will work in older snapshots but you can try to add it in with the other functions shown at the end of this class module: function get_value($code) { return $this->currencies[$code]['value']; } function get_decimal_places($code) { return $this->currencies[$code]['decimal_places']; } function display_price($products_price, $products_tax, $quantity = 1) { return $this->format(tep_add_tax($products_price, $products_tax) * $quantity); } } ?>
×