Clicked on the Maps button today to fix some city names, and went through the process as always, only to have what used to be the map window load up, with nothing other than "Script Error" in the left bottom corner.
Looked at previous posts, and changed the IE 8 options that were listed, still no change.
Are you referring to version 22.214.171.12465? In this version we made specific bug fixes for some location related bugs. I'm sorry to hear that you are still unable to use the map feature. I can see that Isolda gave you 4 free months of the Premium plan, I am now adding another 4, as a compensation.
I too have the same error, as does EVERYONE that uses this software. I would like to enquire on receiving some months free as well, 8 months should do ... and I'd recommend starting to do one of the following:
a) automatically renew memberships for free until the bug is fixed (which I think is coming up on being one month old), or
b) FIX THE BUG!
PS - to my utter shock and horror, I see that my ORIGINAL thread about this, being 200 old was just above Patrik's message ... now I'm really mad ... I await your reply on my credit.
I added the 8 months, and I have great news! We were able to fix this bug for good, as we will start using a new method to display the maps, starting from the new version of FTB (version 6) that will be released in the next few months.
What happens if you click on Yes when getting the error message?
I have consulted the team leader of the program developers, and he requested you to go to My Computer > C > Program files > MyHeritage > Bin > Maps > look for MapPlaces.js file. Do you see it? How big is it?
Great news to hear that the issue has been resolved.
However, I gracefully suggest that FTB fix this in a bug fix version update sooner than leaving it for a version 6 update "in the next few months". I'm sure FTB users would be much happier getting this issue resolved now than in a few months time.
I'm glad to see this error is not on my end. I've been putting in addresses all week, and when I went to check out the map feature today (I think it's the first time I've tried to use it) I got a script error. Actually, I got 3 identical script errors, and then the blank page. I'm just glad it didn't freeze the program because my dumb self doesn't remember when I saved last... But here's the question I have. This post says that the bug would be fixed in version 6. As far as I can tell, I have version 6. I double check, and it says I have the most recent version. So what's the deal? Is this still a bug? Has it been fixed yet?
I haven't had any real complaints with the MyHeritage site, or with the FTB, but if I could make one request, I would love to see a list of changes, added or updated features, and known bugs, features that are currently being worked on, etc. Most of the programs that I use have this somewhere on their webpage, and I was very surprised that I couldn’t find one on MyHeritage…
Well, yes I think it’s practical to use RegCure to update software programs. Also, make sure to close all other applications while you’re at the process; and try to complete it fast before any Internet interruption occurs.
I experienced this issue a month ago or so where the "Merge" button on the SmartResearch screen is no longer accessable. Last time I saw this thread in the forum and installed ver 1189 version of FTB. This seemed to get rid of the problem.
Two nights ago-- it happened again. This time I found a newer version on the myheritage site-- rev 1198.
I installed this version but there was no remedy of the dimmed merge button.
Also the SmartMatching seems to be somewhat flakey-- on the FTB PC side it shows a match with multiple hits, and then when I select the match it says there are no matches available. This happens on many of the matches denoted but not all.
When this started happening again-- I had just crossed the 5000 person in my tree. I noticed that there was some message posts about a limit of 5000 matches due to a security limit. This seems a little odd that you would limit users to an arbitrary number when we have to pay extra to get the feature in the Premium package. A much more smart limit would be to have a date range on the limit so that a user can not match a large number within say a week or something similar.
Any assistance you can provide would be greatly appreciated-- sinice this issue has severly limited my use of the system.