Blog Post
mdfw well, in the specific case we had to deal with the "original" (old) text key is:
form.SearchForm.field.messageSearchField.placeholder@page:ForumPage.<customQuiltName> = <YourPlaceholderText>
the new one that is not documented in the changelog is:
searchgranularitysearchbar.placeholder.text@page:ForumPage.<customQuiltName> = <YourPlaceholderText>
you can find the new textkeys by going to Studio > Text Editor > Advanced > Show Text Keys (do not navigate away from that page!) then go to the frontend, reload and you'll see the text-keys in "raw" form.
You either switch them out or duplicate the values you already had for the new text key(s).
The problem here is not really how to fix it, it's just a problem that breaking changes like that are just pushed into a release without any way of knowing about them and then we hopefully/accidentially discover them... IMHO such changes should only be done with a new Feature version, in this case for the "Search" feature of Khoros, which is currently at v3.4, a breaking change like this should be v3.5 with the appropriate documentation of what changed and what one should be aware of if a community is upgraded to that new version. That is not the case here as a breaking change is simply pushed into the current 3.4 version without anyone documenting it or communicating.