Jump to content

chrishamblin

Members
  • Content count

    47
  • Joined

  • Last visited

  • Days Won

    1

chrishamblin last won the day on November 25 2015

chrishamblin had the most liked content!

1 Follower

Profile Information

  • Real Name
    Chris Hamblin
  1. chrishamblin

    Sage Pay V3 Protocol

    Hi. Have a look at this topic: http://forums.oscommerce.com/topic/397812-sagepay-form/ I asked a similar question :) It is an addon to install. There are installation instruction in the addon from what I remember. Chris
  2. chrishamblin

    SagePay Form

    Ta. Looks like I'll be adding this soon then.
  3. chrishamblin

    SagePay Form

    Hi. This may be a daft queistion, but is the recetly updated addon for SagePay form processing (http://addons.oscommerce.com/info/6983) now using "SagePay v3"? I know that the change log on here says that it now uses the V3.0API. (http://library.oscommerce.com/Package&en&sage_pay&oscom23&form) Is this the same thing? Thanks. Chris.
  4. chrishamblin

    SiteMonitor

    Doh. I copied the files from the wrong folder. I'd upgraded my shops from old versions and spent about a week upgrading them manually to what I thought was 2.3, but it's not quite. That was some time ago. The files from oscommerce_MS2_or_RC2 seem to work loads better. Sorry about that. :-
  5. chrishamblin

    SiteMonitor

    Hi. I know that I've done something wrong, but after an upgrade from version 1.2 (I think) to teh latest 3.2, I now don't have an option on the left colum called SiteMonitor. I presume that it's all down to the file in admin/include/boxes/ I had a look at this, to my eye it looks like it's missing something. <?php /* $Id: sitemonitor.php,v 1.00 2006/09/24 by Jack_mcs osCommerce, Open Source E-Commerce Solutions http://www.oscommerce.com Copyright (c) 2010 osCommerce Released under the GNU General Public License */ $cl_box_groups[] = array( 'heading' => BOX_HEADING_SITEMONITOR, 'apps' => array( array( 'code' => FILENAME_SITEMONITOR_ADMIN, 'title' => BOX_SITEMONITOR_ADMIN, 'link' => tep_href_link(FILENAME_SITEMONITOR_ADMIN) ), array( 'code' => FILENAME_SITEMONITOR_CONFIG_SETUP, 'title' => BOX_SITEMONITOR_CONFIG_SETUP, 'link' => tep_href_link(FILENAME_SITEMONITOR_CONFIG_SETUP) ) ) ); ?> If that's right, then there's something else wrong. Any ideas?
  6. chrishamblin

    UK Vat

    I can't say for certain that this will work with v2.3.1, but the contribution below is what I use on my store: E.U. VAT Intracom Number (http://www.oscommerce.com/community/contributions,1848) It seems to work fine.
  7. That's exactly what I thought. I've tried a few of these type of things in a test environment, and they all seem to do the same. I have always understood that the oscid was golden, and any links shouldn't be shared with this in it, as it links to a certain customer at a certain time. Because of this, when I added an "Email this page" link, I went to some trouble to strip the oscid from the link that was included in the emails. Has anyone that's using this contribution experienced any issues that they know of? Or can anyone let us know if for some reason in this case the fact the oscid is there isn't a problem?
  8. chrishamblin

    Probelm with VAT less sales

    Well, I don't know if anyone else ran into this issue or not, but I found a solution. In the old version of the store (2.2) you never had to specify a tax rate for the Rest Of the World. Now you do. I have set a new tax rate group with the value at 0% and it's now all happy again.
  9. chrishamblin

    Probelm with VAT less sales

    Hi. I've recently upgraded my store to 2.3 from 2.2. It all seemed to go well, and after a bunch of testing it went live. Now I've found that there is quite a large flaw in my code. If someone from inside the EU buys something, VAT is added and all is good. If someone from OUTSIDE the EU (eg. USA) buys something, VAT isn't added - which is right - but for some reason the grand total after shipping costs etc. is $0. Thankfully we have a deferred payment system, and we use Sage Pay who don't process Zero cost transactions, so no real orders were processed at this rather impressive discount, but I need to fix it. I'm guessing that there is a problem with my upgraded code and the way that it calculates the VAT reduction (A possibly multiple by Zero is my current thinking). Has anyone else run into this sort of thing? If / when I get to an answer I'll post back here with my findings... Chris.
  10. chrishamblin

    sagepay form delivery postocde missing

    Hi. i just installed and tried to use the Protx Form Payment Module. I ran into an error with this though. I used the form to download a bit of software. SagePay failed the request, saying that they needed a delivery postcode. I remembered that this had been fixed on my site using protx, so I looked at the code. At about line 250 of the code in sagepay_form.php there is this code. $plain .= "DeliveryAddress=" . $delivery_address . "&"; $plain .= "DeliveryPostCode=" . $order->delivery['postcode'] . "&"; Replacing it with the code below fixes this problem if (strlen($delivery_address) < 10) { $plain .= "DeliveryAddress=" . $billing_address . "&"; $plain .= "DeliveryPostCode=" . $order->billing['postcode'] . "&"; } else { $plain .= "DeliveryAddress=" . $delivery_address . "&"; $plain .= "DeliveryPostCode=" . $order->delivery['postcode'] . "&"; } It fixed it for me. I hope this help someone else too. Chris.
  11. I know that the Javascript and the attributes are unrelated. BUT the install doc for the "tractormad" lightbox mod asks you to replace your product_info.php page with the one in the zip file. It's this new page that has the problems with the attributes. If anything, all that needs doing is just a note in the Zip file saying what to add, rather than just telling you to replace the page.
  12. No problem. Glad that I was able to be of some help to someone with this great product. Next time, watch your paths. ;)
  13. OK, so I was looking in the wrong place. In the same filke you have: <script type="text/javascript" src="lightbox/prototype.js"></script> <script type="text/javascript" src="lightbox/scriptaculous.js?load=effects"></script> <link rel="stylesheet" href="lightbox/lightbox.css" type="text/css" media="screen"><script type="text/javascript" src="lightbox/builder.js"></script> <script type="text/javascript" src="lightbox/lightbox.js"></script> Change it to: <script type="text/javascript" src="js/prototype.js"></script> <script type="text/javascript" src="js/scriptaculous.js?load=effects"></script> <link rel="stylesheet" href="lightbox.css" type="text/css" media="screen"><script type="text/javascript" src="js/builder.js"></script> <script type="text/javascript" src="js/lightbox.js"></script> Good luck...
  14. log into the admin section of your shop. click the "tools" menu, then click file manager. Navigate to the root of your site, then click the "product_info.php" file. You should get an edit button on the top right now. Click that, and you shoudl see the code. find (Ctrl+f) "window.open" (without the quotes) This code will be line wrapped round in the box, but it should be a logical places (i.e. not half way thought a word). If it's not, this could be your problem. Make the words whole, and see what happens.
  15. When your pages load, there is the small Script error box at the bottom left of the browser. Double clicking this brings up an error To me this seems to imply that you have got an error in your script box at the top of the page. Can you have a look and see if it looks like this: <script language="javascript"><!-- function popupWindow(url) { window.open(url,'popupWindow','toolbar=no,location=no,directories=no,status=no,menubar=no,scrollbars=no,res izable=yes,copyhistory=no,width=100,height=100,screenX=150,screenY=150,top=150,l e ft=150') } //--></script> If it does in your source, can you try making the "window.open('url..." line all in one? I would show you what I mean, but for some reason this forum wraps long sentences, so removing my point. :( If you go to this link, then right click, view source, you should see what I mean. This might be the fix to your problem...
×