Portrait remains in gallery after photo attached to wrong person is detached (computer bug).

LegacyUser

Don M Thomas said: Martin Lehmann, I got the same message, "We had a problem on our end. Please try again later." After two days of getting the same message, I went to "Firefox" (a different browser), and tried it there and it took the Portrait.

LegacyUser

Jeff Wiseman said: Martin Lehmann

This is an old topic from over a year ago. Your description may be of a bug that was fixed and has now re-appeared. It sounds important enough that it might be a good idea to create a brand new topic on the mis-behavior that you are seeing. It will likely get more visibility that way.

LegacyUser

Don M Thomas said: Martin Lehman - In making a new Feedback to FamilySearch, you could call it - Attaching a Portrait and getting "We had a problem on our end. Please try again later." Then state it has been going on for weeks. I had the same problem over a month ago.

LegacyUser

m said: Seems like a totally different computer bug than this thread. It might be a good idea to make a new thread and title it "computer bug - error message upon attempting to attach a Portrait" and in the body write the whole message out and say it has been going on for a month and what browser you are using.

LegacyUser

joe martel said: are you still having the problem? Could you open a new thread and describe if the problem is the GetSat image attach or the FamilySearch produtc.

LegacyUser

m said: No. Someone is attempting to get help for a DIFFERENT problem using this thread.

I wrote the following suggesting the creation of a NEW thread to address the new problem:

"Seems like a totally different computer bug than this thread. It might be a good idea to make a new thread and title it "computer bug - error message upon attempting to attach a Portrait" and in the body write the whole message out and say it has been going on for a month and what browser you are using. "

LegacyUser

Martin Lehmann said: Thanks for the help. Someone suggested using Firefox rather than Chrome and it worked. Problem solved.