I am sorry, byt this experiment does not make any sense to me and will not solve, in my opinion, the problem with the mess.
As I understood, according to a new system, posts written while staying in, say X language mode, will be visible only for those who are in the same, X mode of the site, right? But that does not specify the language of the posts. The posts can be written in English, Chinese or any other language of the UTF-8 set, provided the corresponding language support is enabled for the computer keyboard. But only those, who has their site screen modes switched to X language will be able to see the posts (not necessary to read, unless they use some translation tools).
One might say that after creation the posts will be sorted according to the laguage used. But some post are multilingual (I myself wrote several of those). How to sort out those?
So, I think, the mix of posts written in different languages will continue to reside mostly in English section of the forums. The users using languages other than English will have to switch to English to access the majority of posts or make their own (hoping to access the largest group of users ) and then back to their language to continue working with their tree.That is exactly what I am doing right now.
The proposed system is just simple annoyance. That is what I feel already. Please let the developers know.
On the Dynastree site it says the tree will be transferred. Where is it? The only thing transferred so far is 5 of my 13 emails. I've looked through the help pages and sent 2 messages but no one has replied.
I sent you and email 2 days ago and still not heard. Did you get it? What's with the transfer? If you didn't get it, my email is the same. As stated in first message, they managed to transfer 5 of the 13 messages in my inbox to myheritage but nothing else.
You can quit looking for an answer. The only thing I've gotten by email is a ticket number which is Ticket#2010030810000264. I've contacted the person I was on the tree with at dynastree and they didn't transfer the tree here, they made their own website. I won't be putting my information here either because it's not user friendly and there is no help.
Somehow I have managed to list some people in my family twice on the list of names on the left side of the screen.One of the double names state that they are not related to the primary head of family while the other is listed correctly. I cannot figure out how to delete the incorrect entry. This issue throws off the number of people in the whole family. When I post a chart the correct information is there. Can some one help me with this? I would sure appreciate the help
Hur anger jag födelse-/dödsplatser så de dyker upp i "kartan"? Vilket format ska de anges i - socken, ort, län, landskap, stad? De orter som hittills är angivna verkar inte . . . finnas och dyker således inte upp i kartan över födelseplatser, trots att det är orter som Stockholm, Kristinehamn osv.
Could you please send me a screen shot of this problem to
To take a screenshot, press the print screen key on the keyboard, it is the key labeled as “PrintScreen” or "PrtSc". This will copy an image of the MyHeritage screen to your clipboard. Once you have done this, click the Windows Start button in the bottom left corner and run MS Paint. It should be under All programs > Accessories > Paint. Once it's open, click Paste from the Edit menu, or simply press CTRL-V. Now you can save the screenshot and attach it to an email and send it to me.
Hi as I know you like a challenge and things being tested on this fantastic site, here is a problem I have found.
When adding people to a Photo or document and you have more than 8 or 9 it is difficult to do, the reason is, the box that you type the name into stays in a fixed position on the screen and doesnt move down the page. to overcome this problem I had to shrink the screen using control and mouse wheel to make the screen smaller so I could see the box, the problem I had then was I had to use a magnifying glass to see the people that came up on the search.
I just thought that I would bring this point to your attention as it has only been a problem the one time out of the hundreds of times ive done it
Just to finish the new updated features on the people search is great and now you can see more details of the people.
Actually it must have been the time of night and my brain wasnt working, as I was entering the names about 20 in all, the "add a person" button was going down and the box was going up, all I should have done was scroll back to the top of the page. I just tried it,
The Search feature for Keywords in Photos & Documents doesnt seem to work, (or is it Just me)
If in the photo section I search a keyword say "James" and then change the peramiter to within search results and search "ROUT" I should get all the James from that search that are named "ROUT", But I dont. It flicks back to new search and I get everybody that is named "ROUT"
If I click on a Keyword in a photo or document, "Swaffham" I should get at least the one I clicked on in the search but sometimes it doesnt.
One of my members' daughter has a significant birthday on 29 February, which appears in calendars only in leap years. What happens regarding birthday notifications for 29 Februrary in non-leap-years? The website appears to not recognise that 29 February is an upcoming date (ie. No balloons), not listed under events. The same would be true for anniversaries too I suspect.
PS. I just noticed the Events calendar highlighted date does not recognise the time zone of the viewer (ie. me). Ijust looked and although it is 10:30am 20 February here in Sydney, the highlighted date is 19 February, which it can be only in the USA. Bug?
one year down the track from the issue of 29 February reporting of birthdays (and no doubt other events) and no solution as yet I presume. Can you please provide an update on this issue? My member has once again complained that no notification has come through.
Thank you for writing to us.
I have looked into the issue of individuals born on February 29th on a leap year.
There is currently a problem with the way that we treat these events in a normal year.
Thank you for pointing this out to us. We are working on fixing this for the near future.