Thanks Brian. As you surmised I don't use the LDS functions, they're not
relevant to my research. So I will stick with the 8 June update.
Regards
Mary Young

On Sun, Jul 30, 2017 at 1:51 AM, Cathy Pinner <genea...@gmail.com> wrote:

> Mary
>
> If update from the Legacy Home tab, you'll get Legacy 8.
> Or you can go to here to download it.
> http://support.legacyfamilytree.com/article/AA-00899/
>
> Note only the Legacy FamilySearch section was changed so if you don't use
> that, you don't need the update. I suspect you don't or you would have
> found it was broken unless it was just the LDS functions that were broken -
> but I think initially it was more than that. They're the only ones not
> working normally currently. I understand that instead of doing something
> internally, it is directing to the website.
>
> Cathy
>
> Mary Young wrote:
>
>
> Brian
> So does the link take me to another "final" update of Legacy 8, or
> would I inadvertently be upgrading to Legacy 9? Which I don't want to
> do, especially as I understand there is no option to run both versions
> s ide by side.
>
>
> On 29 Jul 2017 10:19 p.m., "Brian Kelly" <exma...@gmail.com
> <mailto:exma...@gmail.com>> wrote:
>
>     Although Millennia did plan that the 8 June build would be the
>     last update to Legacy 8.0 their plans changed when the LDS church
>     FamilySearch website made a change to their API that broke the
>     integration with FamilySearch Family Tree.
>
>     In order to maintain FamilySearch compatibility in Legacy 8 an
>     update was issued with fixes to the LFS module.
>
>     I understand from chatter on the Facebook page that there is still
>     an outstanding issue with the LDS component in LFS because the
>     church has not finalized changes at FamilySearch Family Tree. I
>     suspect once that issue is settled there will be another Legacy
>     8.0 update to bring LFS into compliance.
>
>     Brian Kelly
>
>     On 29-Jul-17 2:15 PM, Mary Young wrote:
>
>         Having updated Legacy 8 with the June 8 2017 "final build", I
>         was surprised, on opening Legacy today, to see a notification
>         "An UPDATE for Legacy is available. Build Date: Jun 13,
>         2017".  [capitals are mine]
>         When I click on "See What's New" there's no list of amendments
>         and corrections to Legacy 8.
>
>         The Page is headed Legacy 8.0 Revision History, Current
>         Version i 9.0.0.189 Build Date of: 13 June 2017.
>    &n bsp;    8 June 2017 - Version 8.0.0.603 - Build . THE END. Final
> Build
>         of Legacy 8.0.
>
>         Now I'm totally confused. Was there a later, final final
>         version of Legacy 8, issued 13 June.  Or Is  9.0.0.189
>         actually Legacy 9. Is this an UPDATE to version 8. Or an
>         UPGRADE to Version 9?.  And if I click on the Install button
>         for June 13, 2017, would I be installing Version 9?  Which I
>         don't want to do.
>         Mary Young
>
>
>
>     ---
>     This email has been checked for viruses by AVG.
>     http://www.avg.com
>
>
>     --
>
>     LegacyUserGroup mailing list
>     LegacyUserGroup@legacyusers.com
>     <mailto:LegacyUserGroup@legacyusers.com>
>     To manage your subscription and unsubscribe
>     http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.
> com
>     <http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.
> com>
>     Archives at:
>     http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>     <http://www.mail-archive.com/legacyusergroup@legacyusers.com/>
>
>
> --
>
> LegacyUserGroup mailing list
> LegacyUserGroup@legacyusers.com
> To manage your subscription and unsubscribe http://legacyusers.com/
> mailman/listinfo/legacyusergroup_legacyusers.com
> Archives at:
> http://www.mail-archive.com/legacyusergroup@legacyusers.com/
>
>
-- 

LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe 
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Reply via email to