Delivery options V10

[kev67]

Forgive me if I have posted this in the wrong place but this glitch is bugging me the point of screaming, I only send to UK, I.O.W and Northern Ireland, In V8 it worked, upgrade to V9 and it worked, having just installed V10 it doesn't

Mr customer can click on his location, UK, I.O.W or NI easily, it displays the relevant delivery cost, all goes well until he gets to Sage Pay and it displays this:

This transaction attempt has failed. Please use the Proceed button go back to the web store from which you were purchasing. The details of the failure are given below.

Status: INVALID

Status Detail: 3145 : The BillingCountry value is too long.

I've gone through all I can think of and I can't sort out why it is doing this, every aspect of V10 works prefectly apart from this bit

someone put me out of my misery please, what has gone wrong, also there is a horrible check box like this on the check out page, it looks a bit tacky to say the least and I didn't put it there

DeliveryCountryChanged(true);
http://www.doorentryonline.com/acatalog/access_control.html

thank you

[leehack]

Check the tax code against these locations in the settings > locations menu.

[kev67]

cheers Lee but they are the same as what they were in V9 and V8

UK = UK
Ireland = UK3
IOW = UK2

[leehack]

I just tried and got straight through to the payment options, i selected mastercard and it was happy to proceed? have you fixed it?

[kev67]

No Lee, I haven't mate

hmmm, this is strange, my problem is with delivery to I.O.W and N.I

Mainland UK is fine, that works no problem, it's when you opt for a location of I.O.W does it go belly up, same for N.I


I'm going to try it now, as I'm sadly not convinced as I have not touched a thing

[kev67]

Nope, it don't work for me or others - enter Northern Ireland for the location and you will see what I mean, as I say, perfect in V8 and V9 and I swear to god I haven't changed didly squat Lee

[leehack]

Yeah seems to happen on non-mainland options. I fear you may have encountered a bug here. The reason we do UK2, UK3 etc. is so that actinic allows you to setup a number of countries with effectively the same tax code. The tax code is always a 2 character reference, so the number just gets thrown off and ignored.

My gut instinct says that actinic is now passing the 3 character code and sagepay is not liking it. Can you do anything to confirm that? switch tax codes for example.

v10 will try and upgrade a v9 as best it can, if i were you i'd go into design library and select all of the checkboxes and revert any layout with cart or checkout remotely in its name back to factory standard, that should get rid of your other problem.

[kev67]

will do Lee thanks, I installed a fresh V10 and then imported my V9 site so as if it did go belly up I have the V9 version as a back up, so I have a V9 and a V10 on my pc

I'll try the reset as you suggest and let you know in case other people have the same problem but I understand where you're coming from in that is tries yet has failed to upgrade the "old version"

I'll be back

thank you

[kev67]

daft question Lee, what code would you suggest (the .com site is a test site so it doesn't matter what I do to it)

[leehack]

I'd just swap UK and UK2, so the additional country has the UK code, then try and buy via that country.

[kev67]

ask a daft question....lol

I will try that Lee

[kev67]

I'd just swap UK and UK2, so the additional country has the UK code, then try and buy via that country.

Update on this, I did swap UK with UK2 and it allows me to buy from IOW but not Mainland so you are correct, it is throwing of the digit '2'

I've put it back to Mainland now but obviously I have no idea what I need do to sort this out, do I need to report this or has anyone else got this problem as I can't be the only one with different delivery cost to other UK areas?

thanks

[Mike Hughes]

I haven't had to do anything like this but I always thought the normal way to do this is to set up actinic with regions under the one country.

That should work if you want do it that way until this problem can be worked on.

Another option, might be customise the scripts to ensure only the first two characters get passed to sagepay. It shouldn't be too big a job for someone who knows what they're doing.

Mike

[kev67]

I do believe it is script thing as V9 works perfectly well for me, all I need really is to be directed to which bit of script to edit and I'll do that

[leehack]

I haven't had to do anything like this but I always thought the normal way to do this is to set up actinic with regions under the one country.
I think this is the traditional way with a country that is broken into states, like the USA or Oz, ours is a strange situation, where we are treated as a country when in fact it is 4. If you offer the countries in the main drop down, it's just a cleaner solution, one click one select and no second drop down on show which doesn't always look the best.

It's fair to say that this split is only usually applied when only shipping to UK is in place, so again, limited choices, nice and clean. The technical issue is that all UK countries use the same code, that's pretty rare if not unique.

Agree with your temporary fix though for sure, only other way is to remove the failing options.

[kev67]

It is what is so annoying as V10 does not let you enter the same UK code 3 times like I had with V9

I can't deliver to IOW at the same cost as Mainland UK so that's why I have a simple drop down menu with 3 area locations

Unless their is a wizz kid who knows what script I have to edit then I'll have to revert to V9 which will be a huge shame having paid out for Support :(

[leehack]

I've raised it on the mods forum Kev, so hopefully someone picks up on it rather sharpishly, although i must say actinic presence at the moment seems to have vanished like a fart in the wind.

[Mike Hughes]

Couldn't you just use the regions rather than countries for shipping and change the checkout layout so that it only displays the regions and not the country?

This should appear the same to the customer.

I can see the logic about the UK being 4 countries. Never noticed anyone claiming IOW as another one though.

Mike

[kev67]

I might that a try and see if it works.....watch this space :eek:

[Mike Hughes]

If you're confident about perl scripting it looks like you ought to be able to strip and extra characters from the country code in the OCC script.

It could be as simple as putting "substr($String ,0, 2)" around the country codes in the invoice (and?) delivery bits.

i.e.

Change:

if (length($::InvoiceContact{COUNTRY})!=0) { $sCrypt .= $::InvoiceContact{COUNTRY} . "\n"; }

to

if (length($::InvoiceContact{COUNTRY})!=0) { $sCrypt .= substr($::InvoiceContact{COUNTRY},0,2) . "\n"; }

and the same for the delivery address bit.

Mike

Note: Untested, untried and may need more work. Backup files before trying.

[kev67]

What the hell Mike, I'll give anything a try

thanks for your time :-)

[itc]

What the hell Mike, I'll give anything a try

thanks for your time :-)

Did you get this working kev or did you have another fix?

[kev67]

Hello

Sadly I have not managed to sort this at all, a simple thing like extra UK address' and I can't sort it in V10. All other versions is easy but not this one

I even emailed Actinic as I pay for support and they have not even replied to me and this was weeks ago (I wish there was a sad smilie to use)

[itc]

Hello

Sadly I have not managed to sort this at all, a simple thing like extra UK address' and I can't sort it in V10. All other versions is easy but not this one

I even emailed Actinic as I pay for support and they have not even replied to me and this was weeks ago (I wish there was a sad smilie to use)

I've just come off the phone to support too and I've pointed them to this thread. Surely it can't be just us that has this issue kev?

[kev67]

You mean you too have the same problem?

OMG, halleluyah (spelling) no offence by that remark but thank god for that, I thought I was going insane and have simply given up all hope:eek:

[itc]

You mean you too have the same problem?

OMG, halleluyah (spelling) no offence by that remark but thank god for that, I thought I was going insane and have simply given up all hope:eek:


We certainly do, our country code for northern ireland is NIR, which worked fine in 9, there are other 3 digit codes too which also cause the issue but the only customer we've had so far that live in one of those countries is in NI.

If I could change the code I would, but we have lots of other country codes & states there too so its difficult to know what to change them to.

I took a look at mikes suggestion but it looks like the script has changed from v9 to v10 and I wouldn't like to mess without actinic commenting first.

At times I wonder how many people are actually running v10 because some of things that are being noticed don't seem to be widely encountered - ip capture doesn't work according to the aug either and I thought loads of people would pick up on that. It seems very strange!

[kev67]

I totally agree with you, I checked the code from my old V8 version that Mike suggested and the lines are the same from what I can tell but I'd guess that everytime you uploaded V10 to your host would the script re-write itself again

I've been on to Sage Pay and they can't help, it is the codes, I'm sure of this as I swapped Ireland for England and it worked. I wouldn't mind so much but I have a few customers from I.O.W and NI and I can't afford to absorb the courier costs

I then tried to do an import of my V10 snapshot back to V9 and it spat it out so I can't even revert to V9 unless I want to spend days on re-editing

A nightmare springs to mind ......

[leehack]

Does NI have it's own code, i thought it came under UK and Southern Ireland had its own IE code.

[itc]

Does NI have it's own code, i thought it came under UK and Southern Ireland had its own IE code.

I thought the same lee. I tried changing it to UK too but it won't allow two to have the same code.

[leehack]

Put UK2 in instead.

[itc]

Put UK2 in instead.

Isn't that what kev has already?

[kev67]

cheers Lee but they are the same as what they were in V9 and V8

UK = UK
Ireland = UK3
IOW = UK2


is what I done from day one....:rolleyes:

A simple import from V9 to V10, no changes, no editing, no nothing, just a simple import

[leehack]

I've setup a site using that without sagepay in the mix and it works, if you're using sagepay then you're probably stuffed too. It's to do with the use of the 'none of the above' country which can no longer be used. There's a KB article coming out soon regarding the problem, it's one regarding the communication protocol as I understand. Short of it is you need to switch the UK to using the states facility, if you want to break the UK up into the various areas within it.

A new 10.01 will also have the update i believe.

[kev67]

hmmm, that's interesting Lee

I did get an email saying that 10.1 was available so I might give it a try as I don't want to knock SagePay on the head for something that should in all fairness be down to Actinic as their previous versions are fine, just not V10 and I don't seem to be the only one who has this niggling gripe that has been going on for way too long

thanks for the info though :-)

[itc]

hmmm, that's interesting Lee

I did get an email saying that 10.1 was available so I might give it a try as I don't want to knock SagePay on the head for something that should in all fairness be down to Actinic as their previous versions are fine, just not V10 and I don't seem to be the only one who has this niggling gripe that has been going on for way too long

thanks for the info though :-)

v10.01 is the only one we have tried, didn't bother with v10

[leehack]

Sagepay have changed to protocol 2.23 (i think) Kev, it's that change that has caused this, it's not an actinic change, it's more how actinic now communicates with that new protocol that is the problem.

[kev67]

So do we rollock the hell out of Sage on this?, I'm up for doing it as they will lose a lot of business if this is affecting people, however, I still have a running V9 version and I still have the IOW and NI delivery options working perfectly, so I'm as you say "stuffed" as I now don't know who to have a dummy spitting session with :confused:

ITC, does this still affect you with V10.01 and who is your payment provider with, is it SP?

[itc]

So do we rollock the hell out of Sage on this?, I'm up for doing it as they will lose a lot of business if this is affecting people, however, I still have a running V9 version and I still have the IOW and NI delivery options working perfectly, so I'm as you say "stuffed" as I now don't know who to have a dummy spitting session with :confused:

ITC, does this still affect you with V10.01 and who is your payment provider with, is it SP?

Yes we have only ever run with v10.0.1 - we use sagepay too. Sagepay still works with 2.22 (as v9 still works) so I don't see how it could be Sagepays issue.

[leehack]

It's not sagepay's issue, nor is it actinic's fault, it's just progress and the effects of it. Actinic need to now fix it, which they know about and are working on.

[kev67]

I have only just seen this thread by Bruce, so it would appear it is a known issue, however, I just wish I could turn back the clock as I wouldn't have upgraded so soon

http://community.actinic.com/showthread.php?t=47201

[saucysal]

I don't really understand any of this. We have places like Northern Ireland, Isle of Man, etc added to our list of countries, and with unique codes that I made up, such as XX for Northern Ireland. People select their destination from the drop-down list in the Checkout. The VAT is the same for these locations, so is the same. I have set up shipping tables to allow for the shipping options and prices being different for the different locations. All works fine in V9 with SagePay. Are you saying that if I upgrade to V10 SagePay will produce error messages for these locations as it will not recognise a country code of XX, though it accepts it with V9?

Sarah

[kev67]

I don't really understand any of this. We have places like Northern Ireland, Isle of Man, etc added to our list of countries, and with unique codes that I made up, such as XX for Northern Ireland. People select their destination from the drop-down list in the Checkout. The VAT is the same for these locations, so is the same. I have set up shipping tables to allow for the shipping options and prices being different for the different locations. All works fine in V9 with SagePay. Are you saying that if I upgrade to V10 SagePay will produce error messages for these locations as it will not recognise a country code of XX, though it accepts it with V9?

Sarah

Is the correct answer Sarah and I fell foul to this big time as I can't revert back to V9 so I am as they say "stuffed"

I would say there are more people who used Protx/SagePay than any other provider and the delivery options are simple in V8/9 - upgrade to V10 or V10.01 and you'll end up like me so as you can see I'm a little annoyed about the upgrade until a patch/fix is made up

It's sad in a way as V10 is good, I prefer it to V9 but now I'm stuck with paying the price for delivery for IOW and NI

[malbro]

Is the correct answer Sarah and I fell foul to this big time as I can't revert back to V9 so I am as they say "stuffed"

I would say there are more people who used Protx/SagePay than any other provider and the delivery options are simple in V8/9 - upgrade to V10 or V10.01 and you'll end up like me so as you can see I'm a little annoyed about the upgrade until a patch/fix is made up

It's sad in a way as V10 is good, I prefer it to V9 but now I'm stuck with paying the price for delivery for IOW and NISagePay protocol 2.23 requires the country code to be alpha numeric with just 2 characters as specified in IS 3166-1 (copy uploaded) which is a list of recognised codes for different countries. The main issue with 2.23 is that for fraud prevention the billing and delivery details have to be passed to sage. in the past they were not compulsory. For the UK the code is GB and Ireland IE, no codes for Northern Ireland or others.

I am not sure using states for the sections of the UK would work either as the SagePay documents suggest states are US only.

[saucysal]

Does this mean that even with V9 Actinic, SagePay could reject these with their latest upgrade? If the problem is only with SagePay and not Actinic V10, this must be the case. We receive many orders from UK offshore, so this is of some concern.

Sarah

[Duncan Rounding]

V9 uses protocol 2.22, v10 uses protocol 2.23. They are both currently in use although 2.22 will be phased out by SagePay over time. In theory it may be possible to revert the v10 scripts back to use 2.22 but I'm not sure how compicated that may be.

You will find a lot about this in the SagePay forums: http://support.sagepay.com/forum/

[malbro]

Does this mean that even with V9 Actinic, SagePay could reject these with their latest upgrade? If the problem is only with SagePay and not Actinic V10, this must be the case. We receive many orders from UK offshore, so this is of some concern.

SarahThe perl code in V9 does not insist on the details being present (it uses protocol 2.22) whereas the code in V10 does (it uses protocol 2.23), V10 also holds a list of valid countries in one of the .fil files which it uses to check the country code (interestingly this file holds UK not GB, the UK is transposed to GB in another file for SagePay).

As V9 is currently working with SagePay, it is going to depend on how long Sagepay allow protocol 2.22 to continue, perhaps someone from Actinic could give a better view on this. The changes are being made to improve credit card security to prevent fraud, you can get more details from the Sage web site but I did not see any mention of timing on this.

In theory you could switch to the V9 code for the present so that it will work for you but I have no idea how long it will be before it stops working. The code changes needed will be quite large as several perl files are affected.

[saucysal]

We despatch a number of parcels every day to the Channel Islands, Northern Ireland, Isle of Man, Scottish Isles, etc. These cannot have the same carrier options and same carriage prices as the mainland. The Channel Islands have the additional problem of requiring Customs documentation and clearance when going by carriers other than the Royal Mail, who have a special arrangement and just need a small sticker on the package. We therefore have to despatch these by Royal Mail only. The charges to us vary considerably between mainland and offshore UK. For instance, we can despatch a 30kg parcel by non-Royal Mail carrier to the mainland for £6, next day delivery, but offshore this could be 5 times the price, and take longer. Royal Mail is cheaper than carrier to offshore, but more expensive than carrier to mainland. So offshore have to have their own tables.

Has anyone got any suggestions to get around this?

Sarah

[malbro]

NB SagePay users: we are aware of a SagePay problem that causes transactions to fail with state-based shipping. We are generating a patch to fix this, which will be released shortly, in the meantime you should not upgrade to v10 if you are using SagePay and using states to calculate shipping.
Quote from Bruce of Actinic

[saucysal]

Somewhere on this forum I read that using states to get around the offshore UK problem does not work with SagePay, as it only accepts states for the US etc. - places that have states. Are you saying that Actinic is working on having states for the UK for places like Northern Ireland accepted by SagePay? Or perhaps some conversion facility in Actinic that converts these states to GB at the payment stage? The latter seems to me like it might work, like the conversion from UK to GB, as long as the carriage options remain as set on Actinic.

Sarah

[brucet]

Just to clarify, there seem to be a couple of unique things about the latest SagePay release, compared with other PSPs that Actinic integrates with.

Firstly, as far as we can establish it has no way of handling country names that it does not recognise. Other PSPs, if presented with an unrecognised country, will offer the shopper a list to choose from instead. SagePay simply returns an error.

Secondly, it only supports States for the USA.

The consequences are that you can no longer use either countries or states to create customised regions with SagePay; and you can no longer use 'None of the above' as a country option.

In v10.0.2 we are developing a workaround to enable you to use states as regions for the UK, but we are not able to produce a generic solution that will work for all countries.

[brucet]

NB Actinic v9 and SagePay will continue to work as before, unless and until SagePay withdraw support for their earlier protocol.

[saucysal]

Thank you, Bruce - your confirmation confirms what I was saying. The "work-around" looks to me as possible if you do it in the same way that you convert UK to GB. The problem is only with UK offshore.

I shall await the work-around before upgrading to V10.

Sarah

[brucet]

For more information about limitations in the new SagePay protocol used by Actinic v10, please see our Knowledge Base article (http://community.actinic.com/showthread.php?p=302239).

[itc]

Supports long considered response after having our snapshot for a while.

-------------------------------------------------------------
Solution:

Can only use standard country code i.e. two digits long codes any more than that will cause error as above.


------------------------------------------------------------

Hmm now why didn't I think of that. No shit sherlock springs to mind.

[kev67]

So what about the likes of I.O.W then??

ARRRGH!

[Darren B]

All this leads towards the need for shipping to be able to incorporate postcodes, well the 1st two letters of one, then you can keep your 2 digit country code, and define shipping bands by

Second thoughts maybe 4 digits of the postcode, IOW uses mainland postcodes so do some others areas

[kev67]

OMG! - I got this working :eek: (for Ireland at least) I'll take a few screen shots for anyone interested as I'm off down the pub to celebrate, I just need I.O.W codes

How do we get these or modify something for this?

Thanks everyone for the inputs you have given me:D

[saucysal]

Hello Kev. Great to hear you have it sorted. If you have now recovered from your hangover, can you tell us what you did? Did you enter the offshore UK places as states of UK, or what. The thread became a bit confusing. Thanks.

Sarah

[itc]

Hi Sarah

I'm not sure if Kevs workaround is this but, if you set United kingdom to be UK & Northern Ireland to be GB (or vice versa) it will work for those two countries. I need to test setting all the other extra UK 'countries' to GB within the database directly and see if this works too, the dialog locations within actinic won't let you have two country codes the same, but directly editing the database gets around this, though I'm not sure it will work.

I'll let you know.

edit: I don't think it would work by editing the database, but perhaps revisiting malcoms idea editing the OCCPROTXScriptTemplate.pl script, but to take any country code with the prefix UK (irrespective of the number of chars) and convert it to GB would do the trick. Working on that now :)

[itc]

ok OCCPROTXScriptTemplate.pl in the CommonOCC folder


make a backup first.


Find the line "# Handle state code according to country"

you should have

#
# Handle state code according to country
#
my $sStateCode = '';
if ($sCountryCode eq 'UK')
{
$sCountryCode =~ s/^UK$/GB/;
$sStateCode = '';
}


change this to:-

#
# Handle state code according to country
#
my $sStateCode = '';
if (substr($sCountryCode ,0, 2) eq 'UK')
{
$sCountryCode = 'GB';
$sStateCode = '';
}



Make sure your extra UK country codes are of the format UK1,UK2,Uk3 etc....


Seems to work for us, but use at your own risk!

[Mike Hughes]

revisiting malcoms idea editing the OCCPROTXScriptTemplate.pl script

Is Malcolm still around? :)

Mike

[Paul Bulpit]

Mike, I suspect you may be referring to a different Malcolm.

Mods delete these two posts?

[Mike Hughes]

Mike, I suspect you may be referring to a different Malcolm.


True. My Mistake. Just pointing what looks to me like an error in attribution.

Mike

[saucysal]

I could put all the offshore UK places as GB, as the carriage options and charges in our case for all of these will be the same. From what you say this will work. I have not as yet upgraded to V10 from V9 as I have been waiting for this problem to be sortable first, and for any bugs to be sorted, so I cannot yet test anything out on V10. If this simple change does not work, then I could try the script change. Thanks.

Sarah

[itc]

My pleasure Sarah.

It won't let you have more than one 'country' called GB or UK on the dialog inside actinic, so you can't just give them all the same code. V10 remaps the code 'UK' to GB when it processes payments via sage.

All the script change does is to remap any UK prefixed code to GB instead of just the normal UK two digits. So by setting your other UK countries codes to UKx, where x is any character (UK1,UK2, UK3 etc are the simplest) when it comes to process for the purposes of sagepay alone they all end up with the GB country code. This works fine.

Tbh unless you have good reason to upgrade, I'd still perhaps leave it until bruce or someone else from actinic have commented again, either a new patch, say my change is ok or to blow it out of the water :D

[saucysal]

OK, I understand. Your script solution looks like a good one. I am not rushing to upgrade as yet, for two reasons; waiting for any other bugs to be identified and sorted, and waiting for when we have a good opportunity timewise to upgrade. We have had problems every time we have upgraded. Last time the simple upgrade from 9.0.4 to 9.0.5 (change from Protx to SagePay) caused our online shop to be down for a couple of days, due to an unfortunate combination of circumstances. We thought that doing it at 5.00 pm on a Friday was a good time as business was quiet, but in fact it was the worst time as both Actinic, Sage and our IT guys stopped work at 5.00 pm until Monday morning. From what I understand, upgrading from V9 to V10 will not over-write V9, so we can get V10 right first before uploading, and can go back to V9 if necessary.

Sarah

[brucet]

Yes, that's correct, you can install v10 and upgrade your site to that version without interfering with your live site in v9. You can either upload the v10 site to a different location; or you can put it in test mode (Web | Switch to Test Mode), in which case it will be uploaded to a test folder on the same server as your live site, with a different script ID so that the two do not conflict.

[leehack]

From what I understand, upgrading from V9 to V10 will not over-write V9, so we can get V10 right first before uploading, and can go back to V9 if necessary.
That's correct Sarah, every actinic version can be loaded onto a machine and operate independently, when you install the software, just don't take the upgrade installation option. You then have 2 independent versions, i have 3 on my machine for example as i still work in v8 occasionally.

Get yourself a test domain for £50 a year, leave v9 running the site as normal and upload v10 to the test site, once happy with the site on the test site, then switch over. Every designer follows this method. You can even have v9 and v10 open to compare sites if you want.

[saucysal]

Thank you for your advice. You two could merge together to become a Chinese martial artist.

Sarah

[kev67]

Anyone know if you can add extra UK areas to the delivery options yet such as I.O.W, Scottish Highlands etc?

I've just upgraded to V10.02

Thanks

[leehack]

Yes you can, settings - locations, set them up and then make sure they are accounted for in tax and shipping settings.

[kev67]

Well done Lee, as per usuall!!!!!!! ;)

Would it be UK1, 2 and so on or is there a download for it all cos I've been round the houses for this and I can't find jack on it, most frustrating

thanks

Kev

[leehack]

Yeah use UK1 UK2 etc. no download available all manual i'm afraid. When you create the new locations, they will default to the bottom, you can move them up and the locations lists then sets the order on the country drop down list, so you can put the popular stuff to the top.

[kev67]

thank you Lee, I'll give it a try and let you know so anyone else might benefit

thanks again;)

[kev67]

Hello again, now please don't shoot me down here, I have V10.02 and I had changed in locations, Mainland UK to Mainland UK1 and added IOW as UK2

It don't wanna know, I cannot for the life of me add IOW as this is not on the list of protocal for SagePay as per a previous guy who posted the entire list

The UK1,2 and 3 only works with the older version in V9

Bear in mind, I have taken the advice you have all kindly issued me at face value from those that are very experienced in websites, I have not modified any scripts so perhaps this is why it does not work for me as I don't really want to edit scripts unless I am told to do so

Sorry if I have read previous post wrong,

Thanks anyway

[saucysal]

Ok. I have downloaded V10.0.2 and have been doing the necessary changes for the offshore UK places (eg Northern Island, Channel Islands, etc). I tried first as recommended on here by some, changing to UK1, UK2 etc [in Locations country list]. I noted earlier that Actinic V10 auto changes UK to GB when going to SagePay. I tested this, selecting Northern Ireland, but got this error when going to SagePay, "The DeliveryCountryvalue is too long".

I then tried setting up Northern Ireland etc as states of the UK. Got into a bit of a mess with strange things happening.

What appears to have worked OK and the orders go to SagePay OK with no error messages is as follows:

Changed United Kingdom Mainland in countries list from UK to GB. Created a new country called UK Non Mainland, code UK (can't have two codes the same). This will auto convert to GB when going to SagePay. Set up states for UK Non Mainland (Northern Ireland etc) [in Locations]. Deleted previous entries for countries like Northern Ireland in countries list. Moved UK Non Mainland up the list to be second. Then changed properties of Shipping areas from the countries to the states listed under UK Non Mainland. Changed the helpful instruction in the Checkout about what to select.

Sarah

[kev67]

Hi Sarah

I have managed to get NI, IOW, UK and Higlands to work using the "proper" ISO codes at long last

Now I'm having grief with PayPal VOIDING payments as and when they feel like it and they don't tell you this either, so you send your customer items out, try to "Release" payment and you could end up with a VOID!

Sorry, thread drift but I is fuming big time:mad:

[Runner]

Changed United Kingdom Mainland in countries list from UK to GB. Created a new country called UK Non Mainland, code UK (can't have two codes the same). This will auto convert to GB when going to SagePay. Set up states for UK Non Mainland (Northern Ireland etc) [in Locations]. Deleted previous entries for countries like Northern Ireland in countries list. Moved UK Non Mainland up the list to be second. Then changed properties of Shipping areas from the countries to the states listed under UK Non Mainland. Changed the helpful instruction in the Checkout about what to select.
Sarah

I tried this and it b%^££&ed up all my existing orders. It took all the VAT off them in current totals and would not allow me to add it back. So I had to set the shipping back to how I had it before.

Has Actinic or anyone else made any progress on this?

[grant]

Hi All,

Just trying to sort this out with a shop I am doing at the moment. The customer is using sagepay, and we are using Actinic 10.0.3

We wish to have a particular county set as free delivery. Following advice on here previously, we set up this county as a country - this works great for assigning free delivery etc.

Now it comes to Sagepay and we get the "Status: INVALID Status Detail: 3145 : The BillingCountry value is too long." error.

So, after reading this thread, it would seem that I would need to have England/Scotland/Wales as regions rather than countries, and then make the counties as sub-regions of these? So the country code would be the same for Sagepay?

But this means ditching my free delivery to a specific County...

This means that the combination of free shipping to a county and Sagepay through Actinic is not possible?

Or is there another way around this??

Any thoughts would be greatly appreciated.

[itc]

What code are you using for your county in the country settings?

[grant]

Hi ITC - using UK at the moment - but as I have only 1 Country - split into 4 regions (England, Scotland etc) it is working fine.

[grant]

ok OCCPROTXScriptTemplate.pl in the CommonOCC folder


make a backup first.


Find the line "# Handle state code according to country"

you should have



change this to:-




Make sure your extra UK country codes are of the format UK1,UK2,Uk3 etc....


Seems to work for us, but use at your own risk!

That seems to have worked for us. We are upgrading a V8 to V11 and came up against the issue of having 4 Countries (England, Wales, Scotland, NI) with their respective counties as States - using Sagepay.

Working in TEST mode - fingers crossed for Live.....