<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Temporary Site Problems with Search Functionality</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=temporary-site-problems-with-search-functionality</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Tue, 21 May 2013 01:07:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Marilyn</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53424</link>
		<dc:creator>Marilyn</dc:creator>
		<pubDate>Wed, 13 Jul 2011 02:44:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53424</guid>
		<description>Denise, my first call to ancestry I was told I was using the wrong internet explorer.  They told me I was using version 9 and that it doesn&#039;t work with 9 and that I need to go back to 8.  I wasn&#039;t sure how to check this and the person I was talking to said he couldn&#039;t help with that.  So I was going to wait till my son got home but I got online and found out how to check.  Sure enough I was using 8 not 9 as they told me.  So I called back and was then told I needed to update java but I had done that the day before.  So I thought maybe I didn&#039;t get a good download so I checked it and it was fine.  The third call I was finally told it was a problem on their end.  Why couldn&#039;t they just say that to begin with.  I am doing research almost every day.  Why can&#039;t they get people who can fix the problem?</description>
		<content:encoded><![CDATA[<p>Denise, my first call to ancestry I was told I was using the wrong internet explorer.  They told me I was using version 9 and that it doesn&#8217;t work with 9 and that I need to go back to 8.  I wasn&#8217;t sure how to check this and the person I was talking to said he couldn&#8217;t help with that.  So I was going to wait till my son got home but I got online and found out how to check.  Sure enough I was using 8 not 9 as they told me.  So I called back and was then told I needed to update java but I had done that the day before.  So I thought maybe I didn&#8217;t get a good download so I checked it and it was fine.  The third call I was finally told it was a problem on their end.  Why couldn&#8217;t they just say that to begin with.  I am doing research almost every day.  Why can&#8217;t they get people who can fix the problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denise</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53419</link>
		<dc:creator>Denise</dc:creator>
		<pubDate>Tue, 12 Jul 2011 21:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53419</guid>
		<description>Well, that particular problem may (or may not, judging by the recent comments) have been fixed, but it&#039;s managed to break basic functionality that was perviously working.  I can no longer do anything, because every time I run a search and go to click on the link for one of the results, my login information is apparently lost -- not passed through to the next page -- and I get redirected to the login screen.

As a long time full access paid subscriber, I find the tech support response that it&#039;s *my* problem because I&#039;m using Safari as my browser to be totally unacceptable.  You guys are pushing Apple products.  See the links on your own website for the new iPad app, etc.  So how can you consider any update that doesn&#039;t work with Safari to be anything less than a major failure?

Very frustrated.  Waiting for a real fix -- one that doesn&#039;t require me to adopt another browser.</description>
		<content:encoded><![CDATA[<p>Well, that particular problem may (or may not, judging by the recent comments) have been fixed, but it&#8217;s managed to break basic functionality that was perviously working.  I can no longer do anything, because every time I run a search and go to click on the link for one of the results, my login information is apparently lost &#8212; not passed through to the next page &#8212; and I get redirected to the login screen.</p>
<p>As a long time full access paid subscriber, I find the tech support response that it&#8217;s *my* problem because I&#8217;m using Safari as my browser to be totally unacceptable.  You guys are pushing Apple products.  See the links on your own website for the new iPad app, etc.  So how can you consider any update that doesn&#8217;t work with Safari to be anything less than a major failure?</p>
<p>Very frustrated.  Waiting for a real fix &#8212; one that doesn&#8217;t require me to adopt another browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marilyn</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53404</link>
		<dc:creator>Marilyn</dc:creator>
		<pubDate>Mon, 11 Jul 2011 15:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53404</guid>
		<description>It would be nice it the problem would be stated in the web dashboard.  I called 3 times yesterday about an internet explorer script error.   The third time I was told it was a problem on their end and is being worked on.  It would have saved me a lot of time if they would have just taken the time to post a message.</description>
		<content:encoded><![CDATA[<p>It would be nice it the problem would be stated in the web dashboard.  I called 3 times yesterday about an internet explorer script error.   The third time I was told it was a problem on their end and is being worked on.  It would have saved me a lot of time if they would have just taken the time to post a message.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BEE</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53403</link>
		<dc:creator>BEE</dc:creator>
		<pubDate>Mon, 11 Jul 2011 11:57:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53403</guid>
		<description>David, it&#039;s my understanding that &quot;old search&quot; is no longer being supported - not quite sure exactly what that means, but it seems to be a dirty word with &quot;them&quot; - as &quot;they&quot; try to wean us away from it to &quot;new search&quot; so that it can eventually be dropped?
I just read through the 47 posts on the board Andy posted the link to - my head is spinning!
I sometimes feel like I&#039;ve been tossed into a foreign country, and everyone is speaking a  language that I&#039;ll never learn, because it keeps changing! 
I&#039;m just glad I started all my trees during the past 8 years and worked diligently on them to find as much information as possible, and not a &quot;senior&quot; just starting out!</description>
		<content:encoded><![CDATA[<p>David, it&#8217;s my understanding that &#8220;old search&#8221; is no longer being supported &#8211; not quite sure exactly what that means, but it seems to be a dirty word with &#8220;them&#8221; &#8211; as &#8220;they&#8221; try to wean us away from it to &#8220;new search&#8221; so that it can eventually be dropped?<br />
I just read through the 47 posts on the board Andy posted the link to &#8211; my head is spinning!<br />
I sometimes feel like I&#8217;ve been tossed into a foreign country, and everyone is speaking a  language that I&#8217;ll never learn, because it keeps changing!<br />
I&#8217;m just glad I started all my trees during the past 8 years and worked diligently on them to find as much information as possible, and not a &#8220;senior&#8221; just starting out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53401</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Mon, 11 Jul 2011 05:01:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53401</guid>
		<description>For those who missed it...

This thread link below will explain what is happening with NewSearch.

Ancestry is engaging in a system wide test and it seems all who use NewSearch are part of that test.

Please read the entire thread to understand exactly what is happening and what ramifications it has on your searches. If you have questions please post them to that thread.

http://boards.ancestry.com/thread.aspx?m=1998&amp;p=topics.ancestry.ancimprovements&amp;sort=asc</description>
		<content:encoded><![CDATA[<p>For those who missed it&#8230;</p>
<p>This thread link below will explain what is happening with NewSearch.</p>
<p>Ancestry is engaging in a system wide test and it seems all who use NewSearch are part of that test.</p>
<p>Please read the entire thread to understand exactly what is happening and what ramifications it has on your searches. If you have questions please post them to that thread.</p>
<p><a href="http://boards.ancestry.com/thread.aspx?m=1998&#038;p=topics.ancestry.ancimprovements&#038;sort=asc" rel="nofollow">http://boards.ancestry.com/thread.aspx?m=1998&#038;p=topics.ancestry.ancimprovements&#038;sort=asc</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David H. Calk</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53397</link>
		<dc:creator>David H. Calk</dc:creator>
		<pubDate>Sun, 10 Jul 2011 18:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53397</guid>
		<description>I have for many years used the OLD SEARCH function
and have found recently that the search is no longer complete. When I search for births by name only that actual birth shows up. Previously that
search would display even if that person searched were one of the parents rather than the actual birth person. Not near as valuable a tool as it once was.  Will it remain this way or return to the more complete search ?????????
Even the NEW SEARCH function does not display the information as it once was.</description>
		<content:encoded><![CDATA[<p>I have for many years used the OLD SEARCH function<br />
and have found recently that the search is no longer complete. When I search for births by name only that actual birth shows up. Previously that<br />
search would display even if that person searched were one of the parents rather than the actual birth person. Not near as valuable a tool as it once was.  Will it remain this way or return to the more complete search ?????????<br />
Even the NEW SEARCH function does not display the information as it once was.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BEE</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53394</link>
		<dc:creator>BEE</dc:creator>
		<pubDate>Sun, 10 Jul 2011 14:32:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53394</guid>
		<description>Madeleine, believe it or not, someone does read our comments and &quot;complaints&quot;, as I have actually received a personal email now and then with helpful suggestions, especially encouraging me to use &quot;new search&quot;.
I keep trying, but I still like &quot;old search&quot; better, although some strange things have been happening with it this past week. When I clicked on &quot;Census and Voter Lists&quot; a whole bunch of unrelated things came up, and &quot;See More&quot; was even worse.
Looks like &quot;they&quot; are paying less and less attention to &quot;old search&quot; no matter how much some of us prefer it.
Hopefully, all these other &quot;weird&quot; things mentioned above have been corrected!</description>
		<content:encoded><![CDATA[<p>Madeleine, believe it or not, someone does read our comments and &#8220;complaints&#8221;, as I have actually received a personal email now and then with helpful suggestions, especially encouraging me to use &#8220;new search&#8221;.<br />
I keep trying, but I still like &#8220;old search&#8221; better, although some strange things have been happening with it this past week. When I clicked on &#8220;Census and Voter Lists&#8221; a whole bunch of unrelated things came up, and &#8220;See More&#8221; was even worse.<br />
Looks like &#8220;they&#8221; are paying less and less attention to &#8220;old search&#8221; no matter how much some of us prefer it.<br />
Hopefully, all these other &#8220;weird&#8221; things mentioned above have been corrected!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Madeleine LaRose</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53314</link>
		<dc:creator>Madeleine LaRose</dc:creator>
		<pubDate>Fri, 08 Jul 2011 23:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53314</guid>
		<description>Oh, and by the way,I have the same problem that Courtney Mulroy has. And my final comment: 72 POSTS ON THIS TOPIC!!!!!!! IS ANYONE LISTENING?</description>
		<content:encoded><![CDATA[<p>Oh, and by the way,I have the same problem that Courtney Mulroy has. And my final comment: 72 POSTS ON THIS TOPIC!!!!!!! IS ANYONE LISTENING?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Madeleine LaRose</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53313</link>
		<dc:creator>Madeleine LaRose</dc:creator>
		<pubDate>Fri, 08 Jul 2011 23:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53313</guid>
		<description>Your posting states that &quot;all&quot; problems have been resolved as of June 30th. Well, I have to report that from my perspective they still aren&#039;t resolved. I start a search and then cannot move to the next page. I had one search going and had spent weeks reviewing entries from the Drouin collection, 1,991 pages!, and now I can&#039;t get back to that page!!!!!!! Grrrrrrrrrrr! I still had many more pages to go through.  I started a new search, back to square one, and tonight I again am unable to move forward to the next page. Really, I think at least you could post a message on the login page that lets us know that there are problems and how soon we can expect them to be resolved.</description>
		<content:encoded><![CDATA[<p>Your posting states that &#8220;all&#8221; problems have been resolved as of June 30th. Well, I have to report that from my perspective they still aren&#8217;t resolved. I start a search and then cannot move to the next page. I had one search going and had spent weeks reviewing entries from the Drouin collection, 1,991 pages!, and now I can&#8217;t get back to that page!!!!!!! Grrrrrrrrrrr! I still had many more pages to go through.  I started a new search, back to square one, and tonight I again am unable to move forward to the next page. Really, I think at least you could post a message on the login page that lets us know that there are problems and how soon we can expect them to be resolved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Courtnee Mulroy</title>
		<link>http://blogs.ancestry.com/ancestry/2011/06/30/temporary-site-problems-with-search-functionality/#comment-53311</link>
		<dc:creator>Courtnee Mulroy</dc:creator>
		<pubDate>Fri, 08 Jul 2011 22:29:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=5979#comment-53311</guid>
		<description>Search is still messed up. I type in Mulroy and get Miller results which isnt even close, maybe a few other variations like Mulrey and if I am lucky what I actually searched for may show up at the end of all that.</description>
		<content:encoded><![CDATA[<p>Search is still messed up. I type in Mulroy and get Miller results which isnt even close, maybe a few other variations like Mulrey and if I am lucky what I actually searched for may show up at the end of all that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
