Larisa Moore

Awesome, thank you so much!

@Wes - where I'd really like to do this is our category pages. We're currently using Humble Squid and have customized our home page already with image/text boxes for our four categories--but two of our categories have 8 sections and even cutting the article list to show 3 instead of the standard 6, makes for a long page (see https://customer.real.com/hc/en-us/categories/200569228). Can this code be adapted to the category page? If so then I might consider switching to Copenhagen if that's a requirement for this to work.

Thanks!

I'm not hiding the text on the home page, it's still what I think was the default:

and on the other pages it's

Here's what I put in the JS:

   //change search box text
  $('#query').attr('placeholder','Start typing to find answers!');
 
  if(lang == "en-GB") {
$('#query').attr('placeholder','How can we help you?');}

  if(lang == "de") {
$('#query').attr('placeholder','Wie können wir helfen?');}

if(lang == "it") {
$('#query').attr('placeholder','Cosa possiamo aiutarti?');}

if(lang == "fr") {
$('#query').attr('placeholder','Comment pouvons-nous vous aider ?');}

if(lang == "es") {
$('#query').attr('placeholder','¿En qué podemos ayudarle?');}

if(lang == "pt-BR") {
$('#query').attr('placeholder','Como podemos ajudá-lo?');}
 
  if(lang == "ko") {
$('#query').attr('placeholder','검색');}
 
  if(lang == "ja") {
$('#query').attr('placeholder','検索');}
 
  if(lang == "zh-TW") {
$('#query').attr('placeholder','搜索');}
 

Hi, me again. We just realized that while the customized text is appearing correctly localized on the home page, on the section and article pages and contact page only the English-US customized text is appearing, regardless of the language in which you are viewing our site (http://customer.real.com). Since the code is in the JS I assumed it would carry through all the applicable pages. Any idea what I might have done wrong?

Two (somewhat related) questions:

1. Is it possible to use dynamic content for the text? We have 9 languages so it's going to be a LONG string of code if I have to hand-code it separately for each language. I can do that, of course, I'm just lazy and we already have the dynamic content set up for the text I want to use. :)

2. Is it possible to change the text just for one language, and leave the rest as the default? We were thinking of testing the change just in English first, as we have a few different phrases we want to try out to encourage more searching.

We miss the ability to tag threads in the Community, as we could in Web Portal! This was a helpful feature for us when multiple threads were created about a broken feature, because we could then easily find all the threads to update them when the feature was fixed. We just fixed some things that had been broken for a few weeks and agents are having to scroll through all our many threads to find which ones to update.

The dedicated email address/inbox is a cool idea. If you use that, does that mean you also get notified of comments beyond the original post in a thread? This is the main change I've noticed in moving from Web Portal to Help Center. Since our customers tend to piggy-back onto existing threads (much as all of us do on this Zendesk support site), some questions are getting missed due to lack of notification to those who are following Community topics.

As always, Wes, super-helpful! Next up: how to get rid of the social share links entirely? I've deleted just about all the social share code I can find under CSS and JS, and the icons are gone, but now text links to Facebook, LinkedIn, etc. appear. :(

Hi, I'm trying to figure out how to change the search results to make them more compact. I like having the KB results on one side and community on the other, but I want to hide the part where it shows who posted it and when it was updated.  (Also, on the community side of the page, can we restrict the language that appears? I saw that there was a way to do this on the community home page.)

Also, just FYI, when I'm previewing as an end-user (since I'm still setting up our Help Center), I'm seeing agent-only articles in the search results, is this a known bug? I'm assuming it won't work that way for a real end-user?