If Kenny answers my questions, I will pass them along. I doubt I will get answers though.

When was this location mess supposed to be fixed? Anyone hear anything from Ancestry? It's now Monday afternoon my time and the locations are still showing extra spaces....

Kebby's e-mail said "Monday". I assume that means today. He gave no specific time but I'm sure that he meant Monday as defined by Utah time.

They are also rolling out the new entry thingie on the search today so it may take some time.

DRAT!

Kebby's=Kenny's

Sorry Kenny

"Attention whoever on staff is doing this, in WV the given name 'Icie' is short for 'Isophene' and is **not** the same name as 'Essie.' 'Sena' and 'Cena' are short for 'Aseneth', and quite unrelated to Serena, Lena, and Celia."


No, but they sure do *sound* alike, and I'd rather see them than have to perform eight separate searches to cover all the bases.

Message from Kenny today. Double spacing problem should be fixed sometime tonight-11-9-2009. In response to my asking why these things happen, he says they check and double check but things get through anyway. In my opinion, too many things like this get through.

And what about frostfreedet's comment "Tree Hints are getting lots less relevant. Like for people not with same first name, nowhere near same birth-year, nowhere near same birth-state, etc."
This happened about the same time as the double-spacing. All of a sudden I'm getting 10 to 20 tree hints on a person and they're all way off. So much so that I'm not bothering to check my hints now which defeats the purpose.

Changing a little bit of code causes all sorts of problems. Kenny told me they check and double check but we-the users- have to catch all sorts of problems so it makes me wonder just how much checking and double checking they really do.

This troublesome problem has been fixed "SORT OF". The basic bad code has been fixed. However, using "type ahead" to click on a death location will still get the double spacing.I just realized this when I e mailed Kenny Freestone that I was still seeing the problem cropping up today. I sent him several screen shots. The first two involved one person in which I added the vitals today but used "type ahead" to click on the death location. The second two involved his wife. I did a screen shot before I corrected her birth and death data, then I typed in her data but manually typed in her death location rather than using "type ahead." Now, when linking a census to her, the double spaces are gone. It just shows the problem with unintended consequences and all the problems that causes just because one programmer did do enough checking to see what was being affected before the bad code was added.

You get the double-spacing in the type-ahead for any item that you saved with the dbl-space before you noticed the problem and (presumably) started deleting the extra space from the form.

This is what I meant about the problem translating into the type-ahead fields in an earlier post.

If you look lower on the drop-down list, you should find a version of the same place-name with single spacing, if you have saved it in the past with normal spacing.

Note that the drop-downs are often in alphabetical order. While it is sometimes hard to tell from the list display which version has the double-space, a 'space' is ordered before a letter, so if there are 2 versions of what look like the same place, the one with the double-spaces will be listed first. Of course. :(

Just another of the Ancestry.com-created annoyances.