I can't "send a message" to another user who has made a change on the tree. Is this where to ask questions?
when you say "you cant send a message"
what precisely do you mean?
You dont know how?
you dont find any contact info for the person?
you sent a message but no one replied?
what is the exact scenario?
what is the PID of the person record that was changed?
If you are trying to send a message via the user's name from the Change Log, there is currently a bug that doesn't allow any typing in the message fields.
General speaking (But, there is a 'caveat'), you can always, send a 'Message', through "User Messaging" of 'FamilySearch', to an ACTUAL User/Patron (except, of course: 'FamilySearch') who has done something (ie. added; changed; merged/combined; etc) to an individual/person in "Family Tree" of 'FamilySearch'.
You may even be able to manually send an "E-mail" to the SAME, provided that their "E-mail Address" is "Public" (ie. viewable).
The real crux of the matter is whether or not, you will get a response.
Not all Users/Patrons respond. And, there are many reasons for such - eg. But, not limited to ... Dead; No longer a User/Patron; Infrequent User/Patron; inexperienced (ie. not aware of such 'Messages'); etc.
Here is a "Knowledge Article" in 'FamilySearch':
How do I send a message to someone who contributed to Family Tree or Memories?
That said ...
That 'caveat' ...
Worst case scenario ...
The User/Patron may have "Muted" YOU from sending THEM "User Messages" ...
How do I mute or block someone from messaging me?
I hope this helps.
Maybe not such a good idea to highlight this (muting) option here, Brett. Okay, if Sue had been reporting a problem with unwanted / abusive messages from a particular user, but it appears she just had difficulty in sending a straightforward message. Unfortunately, some users will read the article and might act negatively - i.e. block messages just because they don't want to collaborate with anyone.
Perhaps your response was being typed as Amy posted hers, but there seems no complicated issue here - as she reports there was / is just a bug that is causing the problem.