In FTB 22.214.171.12434, in the "Edit Repository" window, if a change is made to the contents of the "Website/Link/URL:" field ONLY, this change is discarded even when "OK" is clicked - reopening the dialog shows the original value unchanged. To get the URL change to save, at least one other repository field (though I haven't check them all!) has to be altered as well.
I presume there's some "compare before/after field values" code that skips the update if nothing has been altered, and that the URL field was added later but someone forgot to add it into the list of fields to be checked (code factoring is everything)
Also, it would be nice if this Repository URL field was consistent with the "Page/URL" field in the citation window, and had an automatic "Open Browser" icon button next to it.
Hi Dean. My comment in the last paragraph was just a suggestion, but my post was mainly about the URL not being saved properly from the repository window. That seems to be a definite fault, so could you make sure it gets passed on to the development team. Many thanks, Ross
There seems to be a problem with the smart match status handling in FTB 126.96.36.19934, when different people with the same name are involved.
For example, I have smart matched and then confirmed someone, say "John Smith" born 1830, against the correct match in another member's tree.
I then add John Smith's grandfather who is also called "John Smith", born 1780. The smart match for the grandfather may then offer an incorrect match against the younger John Smith born 1830 in the other tree. That wouldn't be a problem, except that this new incorrect match ALREADY shown as confirmed, even though I haven't confirmed it and my actual confirmation was made previously on his grandson's record.
I don't think I can reject this new wrong match without effectively rejecting the original correct match - the status seems to be shared between the two different individuals in my tree.
It seems as though the smart match status (confirmed/rejected) is linked to the name, rather than the specific record, so fails as described above when identical names are involved. In this instance, if the status also took into account the date of birth that migh resolve the problem, but since the dates are not always known, the status really needs to be linked to the specific person record in some way.
PS I haven't yet published my tree, partly because it has over 250 names, which I know may affect the number of matches I get, but I don't think this could be the cause of the problem above.
I've found a minor but irritating bug in FTB 188.8.131.5234. If I edit the children details of a family, and tick the "known number of children" box and set it to zero, the box correctly says "Children: 0 (there are no children in this family)", but the "Place:" label then moves entirely OUTSIDE the marriage box, appearing to the right of it over the background, and any marriage place text isn't shown at all. This happens even if the FTB tree window is maximised and so the marriage box has expanded to full size, so it's not a "resizing" issue. It also works fine if I change the number of children to one or more.
Of course, I could just untick the "known" checkbox, but then the unnecessary "add son/daughter" box is always visible.
As I wrote to you by email, In order to find specific records for Australia, please first fill fields of the SuperSearch (location, name,...) as you did with the example that you sent, and click SEARCH.
Then, is important to user the filters located on the lower left hand corner of the screen.
Hope this is useful. Please contact me for further comments or questions.
I have divorced and reverted back to my maiden name. This is fine on Family Tree Builder (and in my profile), but has not updated on the online version. When you click on my profile, the name is correct, but not on the actual tree!
Also, my current partner (who is also female) has a daughter. How do we list her as my partner's child, and my step-child. We don't want to put the child's father in the tree, and we don't want to select her as 'adopted'.
Thank you for the message. You can view the tree - but you can not add more people online. All our users have the same rules. Basic account is up to 250 individuals, Premium 2500 and PremiumPlus no limits. As you are buidling your tree using Family Tree Builder you can add there as many as profile you would like to. However if you would like to add more profiles online please consider upgrade to Premium.
Data consistency checking is alarmingly weak on the Family Tree Builder. In conflict situations there are no standards and no error checking guiding how to resolve certain common issues. Together with Smart Matches this creates situations where the same issue is resolved in many different ways creating an even worse chaos than the one caused by the error prone and bugridden Smart Matches process itself.
1. There are many cases where the forename of a person is not known. The lacking forename could be subsituted with code indicating or there should be box to cross, that this is the case. Now you see forenames like Okänd (Unknown, in Swedish) or Dödfödd pojke (born dead, in Swedish) or NN. Smart Matches treats them all like they would be real forenames! A common but not too obvious error is that a unnecessary space is introduced before the first name. In the FTB name list spaces are not visible because they are probably stripped away. In the list, however, those names are shown first because the spaces are wrongly included in listing process. Remove bug please!
2. When you insert a location/position there is no advice to indicate the format. Should it be e.g. country, town, village or village, town, country? Could/Should country abbreviations be allowed, like D, GB, S, US etc.? Should there be commas? My preference is yes because the address may consist of several words for e.g. a village. Also, when you do a consistency check on your family tree you can see that most of your places are arbitrarily and wrongly spread all around the world. At least the country should be picked from an extended standardised list, also providing for countries that existed in former times. Perhaps also a possibility of providing an own alternative should be given.
3. In many northern countries person names consist of a numerous forenames, a middle name and a family name. Presently there are no provisions for middle names which means that people are inserting it either as the last forename or the first family name. That causes arbitrary results in search functions.
4. Most people insert forenames without commas between them, but unfortunately there are a small number of people who insist on inserting a comma. Smart Matches wrongly makes a diistinction between these two cases, even if the names are identical in all other respects. This slows down the manual Smart Matches process considerably. Either FTB should automatically remove commas altogether or disregard commas in the search process.
5. Are you doing anything about reviewing the bugridden Smart Matches process?
Have you at MyHeritage taken a look at these issues and what are you intend to do about them?
Thank you for your post and for these suggestions.I will be sure to forward them to the appropriate departments for future consideration.
Please let us know if you have any other ideas, either through message threads in forums or by directly mailing us at email@example.com. We take your suggestions seriously and value such input from our users.
I strated using the FTB, than I realized that I can't edit the tree from the web. I export my project from FTB and upload it as a GEDCOM, now I have 2 family trees on the web.
1. How to can I keep only the one from the web and open it for editing on web?
2. I saw you (MyHeritage as admin) can change that manually, but than I can't use the FTB again, What is the best strategy for editing the tree on web, and once in a while (for larger updates) export it to FTB and import it back again.
I'm having issues with associating documents/photos in the Family Tree Builder software (version 6.0)
I've uploaded many photo's and scanned images of documents that I wish to associate with people and facts in my family tree.
At first I was doing the associations for multiple documents before pressing the 'save' button and found when I checked the documents I'd done very often the associations had disappeared - but not always.
I then started pressing 'save' after every documents associations and while the associations are there when I check immedatley after when I check in a few days they've sometimes disappeared. The facts I create when associating documents are still saved with the person but the link to the picture disappears.
I loaded my project this morning and the software flagged me that there were no photos loaded. I confirmed that the pictures are still there in the data directory but the associations within the database are now gone. There are almost 1400 photos that I have to re-associate! What happened? Software is up to date and everything else appears to be OK.
I didn't give up - fortunately the software was making backups of the Database. The most recent backup had everything correct - scared the #$%^#$%^ out of me! A simple rename of the corrupted database and a copy of the most recent back restored things.
The saga continues - Now the system has me very confused. There is a photos directory in the MyHeritage data directory with the imported pictures 3 for each picture (thumb nails, the original picture and a mid size picture). I have not changed the location of this directory. There are 4075 items in this directory. However, I have reorganized my source file system to streamline getting to things. Apparently the PCSoftware is using both? its internal data directory and the original file location? Please confirm - Right now I have 0 - that's ZERO pictures/documents etc linked because the software isn't using its own data store. This will take me weeks to recover from.
there is a bug that MyHeritage has not resolved, despite being told several times. If you put a photo into a virtual cemetery (ie. a headstone associated with a burial event), then the published family tree loses its links to photos when the family tree is uploaded. The workaround is to keep FTB open and check if the online family tree retains its photos. If not, then re-save in FTB and republish. This seems to rebuild the index.
I went through teh same drama you did with many photos at risk. I recovred from a local backup too the first time. Then after a bit of trial and error I found the causing event (virusla cemeteries) and the workaround.
Unfortunately My Heritage continues to ignore this bug. This is a blemish on an otherwise superb product.