Hoston Problem Still

[Time Traveler]

I reported the "Houston" problem to the help desk some time ago and was told to try different browsers, clear my cache, and so on. None of these solved the problem. Help finally said they were able to replicate this anomaly and would have the programmers look into it. Well, here we are - it is nearly June and the problem still is not fixed. Meantime I am not able to view the trees of any of my matches. If I change browsers it may work for the first tree but then will not for the second tree. My patience is fading rapidly. I rarely look at FTDNA any more, preferring to spend my time at my Ancestry.com matches and Gedmatch.

[Biblioteque]

Has the private message function here been disabled? Has anyone used it lately and received a reply? Thanks....

[Jim Barrett]

From GAP Home Page - Houston is the Problem!

Can't even get to the list of members.

I really hate having to tell my project members that the FTDNA website is so messed up I am not able to help members.

Will we ever see relief?

I don't have time to stay on hold and sending messages to the help desk is a waste of time because they are buried under a mass of e-mails reporting problems.

I wish FTDNA would restore their site as it was back in Sept. or Oct. It really doesn't matter it that wouldn't provide the new disasters (I mean improvements). At least we had a website we could access. Then they could do their development on their time, not ours!

[dtvmcdonald]

I can't get to the list of members either ... from Firefox.
But I can from Chrome. I can get to everything else from
Firefox.

[dtvmcdonald]

I can't get to the list of members either ... from Firefox.
But I can from Chrome. I can get to everything else from
Firefox.

Now corrected, as is the bogus new BigY results problem.

Now if they just fix the bogus new Ytree problems!

[Tenn4ever]

Had five new matches come in today. Only one and the most promising has a tree....but the can't access her tree because of the Houston we have a problem. Same thing happened a few weeks ago with a promising match but the tree wouldn't load.

[John McCoy]

Two bugs for the price of one!

First, I get the Houston We Have a Problem screen for SOME GEDCOM files for Family Finder matches, but not for others. The problem seems to affect more recent matches. However, I haven't done a systematic check to verify that there is a specific cutoff date before which the GEDCOMs can be viewed.

Second, when I FOLLOW THE DIRECTIONS and enter my e-mail address in the blank on the Houston We Have a Problem page and then click on the SEND button, the page redisplays (repositioned to the top), but it doesn't appear that the e-mail address is actually being "processed" or sent. So, maybe there is a problem with the Houston We Have a Problem screen.

It would be helpful if we had an update on the status of both of these Houston problems.

[suttonwho]

It would be helpful if we had an update. The gedcoms are a bare bones essential tool.

I seem to get the error message for trees from early May onwards.

I have matches. My cousins are cooperating by uploading their gedcoms so we can compare. FTDNA, a genealogical service, is hindering our progress by not making family trees available? Dear oh dear, IT, get it together.

[Katydid]

I share your frustration. I have a kit for which the Gedcom has been inaccessible by others for a month (since May 7, when the results were posted). This is the latest reply I've gotten from the Help Desk (as of yesterday):

"Thank you for your reply. Our IT department is still working on the issue, but I do not have an estimated time frame as to when it may be resolved unfortunately. However, working out the issue itself is taking longer than expected. We realize that the GEDCOM files are an important part of the research and we apologize for the delay and inconvenience this causes."

[suttonwho]

To make matters worse, many people who have uploaded their gedcoms recently have no idea they aren't accessible to their dna matches.

I continue to run into matches who uploaded gedcoms during the glitch period where their names/dates appeared but locations didn't. That problem has been 'fixed' but I wonder if it has only been fixed for people who reuploaded after it was resolved? Several of my matches still have partially blank trees and are unaware that they need to reupload to fix the blanks.

[hodgept]

I think maybe it has something to do if they upload their gedcom before their matches come or after. No other reason that I can see their being houston on one and not the other dated the same day.

[georgian1950]

very frustrating!

I have received 26 FF matches since May 1. Only eight had gedcom's, but of those only one does not have the Houston problem. It's bad enough with matching people not supplying information to work with, but frustrations add up when you can't see what those that did provided.

[efgen]

Hi all,

Engineering is aware of this issue. There are some updates coming soon that will fix this, but it may still be another couple weeks.

Elise

[suttonwho]

Elise, is it expected that the repair will retroactively fix the broken gedcoms or will customers need to reupload them as was the case with the gedcom issue of broken places?

[efgen]

I don't believe the GEDCOMs will need to be re-uploaded, but I'm checking on it to be certain. I'll let you know when I hear back.

Also, I just found out that it may be closer to a month for the fix. The fix will be part of some other updates to the GEDCOM system, so that's why it's taking so long. It will be worth the wait, though!

Elise