I need tech help on saving image description [closed]

Question

When I try to save the Find a Grave http address and the http address of the photographer, the code I typed changes. I had to try this a couple times before my brain believed what my eyes were seeing. Three apostraphes are exchanged for the equal sign in the http address, which results in a mess. Help please - I have put links into the descriptions box of images before and never had this problem.

Comments

Caution: not sure you're doing this, but all should be cautious about copying Find-a-Grave photos to wikitree or anywhere else online. There at least were (and probably still are, especially given the newish ownership by Ancestry) pretty strong usage rules against copying Find-a-Grave photos. Better to link to the pertinent entry.

---

Hi Jillaine,

↑ Find A Grave Memorial# 17835523 for Thomas Weller Created by: Jan Franco, Record added: Feb 06, 2007; Photo used with permission, thank you to Michael Ryley Bradbury.

Above is the entry under Sources on  http://www.wikitree.com/wiki/Weller-93 Thomas Weller profile.

I also add the source and any attributions in the comment box under the picture when I add a picture.

Michael is one of the wonderful volunteers who add thousands of photos of graves and cemeteries. He was very gracious to grant permission when I emailed him.

I agree totally with you Jillaine, we all need to be cautious about copying photos or text. We need to obtain permission, or use links and either way, to credit sources. It disturbs me when I see profiles where entire Findagrave entries are copied and pasted.

---

April, great example and model for all of us re: getting permission and citing it.

Answer 1

But the links work and goes to Find A Grave , right ? That's what I saw.

Comments

Thanks for checking Maggie. The links were to Thomas Weller's entry and to Michael Bradbury's profile (the photographer). Currently both links go to the search page. I am puzzled. Also - I used the normal [http: space name] to enter the links, but they are not showing as embedded links. I am dismayed.

---

I'm not sure if I was clear enough about what happens.

When I save, what I typed in CHANGES and apostrophes are inserted where I typed = signs.

I cannot imagine what can cause this!

Answer 2

After considering it, I think the only way anyone can see what happened is if you go to the  image and then try to add the embedded link to find a grave and the embedd link to Michael Bradbury. here are the links - as you can see they have equal signs not three apostraphes.

Also, did I mention that much of the link shows up in bold? why?

http://www.findagrave.com/cgi-bin/fg.cgi?page=gr&GSln=Weller&GSfn=thomas&GSbyrel=all&GSdy=1751&GSdyrel=in&GSst=8&GScnty=306&GScntry=4&GSob=n&GRid=17835523&df=all&

here is the second link:

http://www.findagrave.com/cgi-bin/fg.cgi?page=mr&GSln=Weller&GSfn=thomas&GSbyrel=all&GSdy=1751&GSdyrel=in&GSst=8&GScnty=306&GScntry=4&GSob=n&GRid=17835523&MRid=46850737&df=all&

Comments

I went to another computer with different software and it did the same thing. I copied and pasted the findagrave reference under Thomas Weller's profile (which is the same link and which shows up just fine on the profile page) iinto the comment box under the image - and IT DID THE SAME THING.

It is not something I am typing - it is something to do with the comment box. Hope a techie can unscramble this:)

I deleted the whole comment and started with a fresh comment box and copied the source from the profile page into the comment box under the image, and it did the same thing.

I have often copied sources into comment boxes under images, to properly source the image, and this has never happened before. I think there is a gremlin in the works.

---

I was under the impression that "Find A Grave" switched hands.  Ancestry.com is now the owner.  That might be a reason the links aren't working.

Mary

---

Thanks Mary but it changed hands some time ago and the links I made since it changed all worked until yesterday.

Maybe I didn't put this question in the right place. A WikiTree Technician needs to look at it.

---

It's the equal signs in the URL that are causing the problem. If you put the URL in the main body of the page it should be fine. In comments we restricted the code that could be posted for security reasons. Then we tried to make it easier by automatically translating certain code. That causes its own problems.

---

Thank you so much Chris. Now that I understand what is happening I will know what to avoid in the image comment boxes, and I can put the source reference in different terms in the comment box.

I love WikiTree. Thank you for keeping us and all our work safe!