Postcodes Don't Match Issue

[spcdust]

I can totally accept the issue of the sheer weight of numbers trying to get tickets and the servers struggling but we actually got through only for the booking page to reject two of our groups postcodes as not matching.  Tried everything and they are 100% correct but not according to Seetickets site.

It just makes booing impossible.

[Neil]

1 minute ago, spcdust said:

I can totally accept the issue of the sheer weight of numbers trying to get tickets and the servers struggling but we actually got through only for the booking page to reject two of our groups postcodes as not matching.  Tried everything and they are 100% correct but not according to Seetickets site.

It just makes booing impossible.

that must be a bitch, tough luck, it works for other people, tho. 🙂 

[spcdust]

3 hours ago, Neil said:

that must be a bitch, tough luck, it works for other people, tho. 🙂 

The postcode issue is not a new one - on previous years sales people have had the same issue whereby perfectly good credentials are rejected by the Seetickets servers.  There's reports of others having issues with postcodes on this years sale.  If you happen to be one of the unlucky registrations that this happens to it's grossly unfair as nothing you can do despite due diligence ensuring your details are 100% accurate.  Both registrations have been successfully used in past sales and were checked in the weeks leading up-to-sale.  Makes the registration scheme rather pointless if it erroneously rejects correct details at the crucial sale.

[Neil]

4 minutes ago, spcdust said:

The postcode issue is not a new one - on previous years sales people have had the same issue whereby perfectly good credentials are rejected by the Seetickets servers.  There's reports of others having issues with postcodes on this years sale.  If you happen to be one of the unlucky registrations that this happens to it's grossly unfair as nothing you can do despite due diligence ensuring your details are 100% accurate.  Both registrations have been successfully used in past sales and were checked in the weeks leading up-to-sale.  Makes the registration scheme rather pointless if it erroneously rejects correct details at the crucial sale.

some of that new fangled AI making computer say no.

[efcfanwirral]

We had this exact issue in the October 2019 sale. Turned out my girlfriend's postcode was in the wrong format - it has to 100% match what is on the registration, including capitalisation and spaces.

I see a "proper" postcode as including capitals and spaces, and assumed everyone else was the same. Turns out its just me - I'd put her postcode in the same format as mine on the spreadsheet, but she'd put it on the registration with no spaces and no capitals. And as I got through right at the end of the sale I only worked it out afterwards. I think we shared 50% of the blame in the end but that was a tense day...

I noticed the same with another member of our group this year and had to clarify, and she'd actually missed a space out so got her to paste from the site to be sure. 

 

[BenG92]

For what it's worth, when the registration page was up early and you could test details, I did try with and without spaces in the postcode and both worked. I didn't try lower case though - frankly nobody should be putting a lower case postcode in anywhere, they're capitalised on purpose so people don't confuse l and I

[efcfanwirral]

6 minutes ago, BenG92 said:

For what it's worth, when the registration page was up early and you could test details, I did try with and without spaces in the postcode and both worked. I didn't try lower case though - frankly nobody should be putting a lower case postcode in anywhere, they're capitalised on purpose so people don't confuse l and I

ah interesting - must just be case then. You'd be surprised, I know a lot of people who put in lazy postcodes. Most websites will validate it and pull your address in anyway, so it creates the conditions for some ticket day stress as people have no reason to do it differently most of the time!

Edited November 6, 2022 by efcfanwirral

[Neil]

25 minutes ago, efcfanwirral said:

it has to 100% match what is on the registration, including capitalisation and spaces.

the capitalisation part can be dealt with easily in software code, could deal with spaces like that  too.

part of designing good software is predicting how people will ~(mis-)use it (i don't have to train people on the efest content manager, cos i've documented examples for the form fields, to make it easy  to fill in, and have everything work).

[dulcificum]

Does the form automatically capitalise all input? And yeah, backend culling spaces before checking for a match is standard practice.

[efcfanwirral]

39 minutes ago, Neil said:

the capitalisation part can be dealt with easily in software code, could deal with spaces like that  too.

part of designing good software is predicting how people will ~(mis-)use it (i don't have to train people on the efest content manager, cos i've documented examples for the form fields, to make it easy  to fill in, and have everything work).

 

13 minutes ago, dulcificum said:

Does the form automatically capitalise all input? And yeah, backend culling spaces before checking for a match is standard practice.

Could the problem be down to them having to match the registration data within the See on the day ticketing system? The issue I came across may be fixed by now but definitely not taking that risk and its on the ticket day checklist now!! 

Edited November 6, 2022 by efcfanwirral

[spcdust]

There is definitely something wrong at Seetickets end as the exact same postcodes in exact same format were accepted by one of the groups that was trying later on for us (alas that didn’t go through due to the payment timing out). Worth noting, they were trying a bit later on so not a case of two people trying at the same time and locking the registrations.

Also we tried every combination, no spaces, lower case and upper case and nothing would work but looking at the registration the format we were entering matched the registration exactly.

My suspicion is being connected to two different Seetickets servers and the one we were on had a fault whilst the other group was connected to another server which was acting as it should.  It’s just totally random and, like I said, these registrations have previously worked with no issues.

[gfa]

1 hour ago, efcfanwirral said:

We had this exact issue in the October 2019 sale. Turned out my girlfriend's postcode was in the wrong format - it has to 100% match what is on the registration, including capitalisation and spaces.

I see a "proper" postcode as including capitals and spaces, and assumed everyone else was the same. Turns out its just me - I'd put her postcode in the same format as mine on the spreadsheet, but she'd put it on the registration with no spaces and no capitals. And as I got through right at the end of the sale I only worked it out afterwards. I think we shared 50% of the blame in the end but that was a tense day...

I noticed the same with another member of our group this year and had to clarify, and she'd actually missed a space out so got her to paste from the site to be sure. 

 

Bold isn't true

[WestCountryGirl]

I got through on my Dad's iPad this morning, the one device which didn't have reg details pre-typed ready to copy and paste. Mum was reading them out to me as I put them in. I think on some of the postcodes I didn't even type in the space that was there on the registered detail, and capitals were hit and miss due to the sheer pressure of it all. 

And yet, it went through no problem. I was as shocked as anyone.

[efcfanwirral]

1 hour ago, gfa said:

Bold isn't true

Is it just capitals or spacing that's the issue? (Or was, haven't made that mistake again)

[gfa]

7 minutes ago, efcfanwirral said:

Is it just capitals or spacing that's the issue? (Or was, haven't made that mistake again)

not sure sorry, too new!

[Dave_c]

I didn't capitalise or put spaces in and didn't have any issues

[spcdust]

My understanding is nowadays the postcode field is relatively relaxed in terms of capitals or space or no space.