Feedback llinks inoperative

If I click on "Feedback" at the bottom of a page, I get a message saying "there was a problem transmitting your message, please try again later."
The message was itself about two other similar feedback links which also are not working and have not been for several days. Here is the message I'm trying to submit:

On your help page, https://www.churchofjesuschrist.org/hel ... t?lang=eng, the link for "Do you have feedback", https://www.lds.org/tools/feedback?lang=eng, does not work. Also, the link for "Help Us Improve", https://www.churchofjesuschrist.orglds. ... J&lang=eng, says there is a problem with a security certificate.

I recommend you try a different page. I have seen some links that are broken because they have not all been updated yet and if you can provide the information in your post using a different page, they will look into it. There is little likelihood anyone who can fix this will see your post in this user-to-user help forum.

I have tried three different pages with a feedback link and so far none have worked.

I just tried the Feedback link from the main page, from the Portland Oregon Temple page, and from the Book of Mormon page (from Gospel Library). All three brought up the form. (I was signed in to my Church Account at the time, so it pre-populated my name and email address.)

Yes, I have been able to fill out the form but clicking on "Submit" gives a message that there was a transmission error and try again later.

snows wrote:Yes, I have been able to fill out the form but clicking on "Submit" gives a message that there was a transmission error and try again later.

At times recently, it appears Church servers and/or networks have been overloaded to the point that symptoms like that are showing up. One partial workaround for the latest symptom is to save the text to a file so if the attempt to file feedback fails you can copy-paste it back for the next attempt.

Another possible workaround would be clear your browser's cache and delete relevant cookies. There are some indications that corrupted cache and/or cookies _might_ be a factor.