On this topic, the new update, just available, fixes the ordinance
information problem, to some degree. There are still some things that
don't work quite like they are supposed to, such as, for example,
sharing ordinances with the church doesn't work now, which means that if
you want to do that, you have to go into the FamilySearch Family Tree
website to get the sharing done -- every time.
Nevertheless, I very much appreciate all that is being done, and if we
can be understanding and patient, I'm sure things will work out okay,
and in the meantime we can enjoy a happier life.
Joseph Leavitt
On 6/8/2017 5:42 AM, Janie Darby wrote:
I agree with you on coordination of changes. It makes it so much
easier for everyone.
We try - failure to coordinate can result in things going sideways in
a hurry.
Happy hunting.
Janie
On Thu, Jun 8, 2017 at 8:25 AM, Allen Prunty <[email protected]
<mailto:[email protected]>> wrote:
Janie,
API’s exist so that third parties can interface with their data.
I understand changes need to be made and we are not dealing with
high security information here… after all most of the people who
are listed in family search are dead.
You would think that any changes to the API would be sent to the
developers of those who use them so that they can make the changes
to their systems in advance of the new API deployment.
Or they could maintain backwards compatibility for some time so
that people can switch over to the new API smoothly.
As for the Govt… I’m former US Gov employee… I’ve seen many things
fixed until they are broken.
Allen
*From: *LegacyUserGroup <[email protected]
<mailto:[email protected]>> on behalf of
Janie Darby <[email protected] <mailto:[email protected]>>
*Reply-To: *Legacy User Group <[email protected]
<mailto:[email protected]>>
*Date: *Wednesday, June 7, 2017 at 11:23 AM
*To: *Legacy User Group <[email protected]
<mailto:[email protected]>>
*Subject: *Re: [LegacyUG] LDS members
Hey Allen,
I work for the US Government, and I resemble that remark! 😁
But you can't sit still. The computer industry is constantly
changing to provide better, faster, safer, and sometimes those
changes have unintended consequences when you are trying to
interface with applications you don't own/control.
Janie
On Wed, Jun 7, 2017 at 10:08 AM, Allen Prunty <[email protected]
<mailto:[email protected]>> wrote:
Why do they like to do things like this ☹ it was working just
fine. You would think that Ancestry and Familysearch were the
us Government where if it’s not broken they keep fixing it
until it is.
Allen
*From: *LegacyUserGroup
<[email protected]
<mailto:[email protected]>> on behalf of
Michele/Support <[email protected]
<mailto:[email protected]>>
LDS members - FamilySearch has changed their API (the
programming code we use to interface with them) so you won't
be able to see your Ordinance information on FamilySearch
through Legacy (via the Temple tab). Luc is working on fixing
the code on our side to match theirs and then we will get an
update out as soon as possible.
--
LegacyUserGroup mailing list
[email protected]
<mailto:[email protected]>
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/[email protected]/
<http://www.mail-archive.com/[email protected]/>
--
LegacyUserGroup mailing list
[email protected]
<mailto:[email protected]>
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/[email protected]/
<http://www.mail-archive.com/[email protected]/>
--
LegacyUserGroup mailing list
[email protected]
To manage your subscription and unsubscribe
http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
Archives at:
http://www.mail-archive.com/[email protected]/
