최근 검색


최근 검색 없음

Lilian Herman's Avatar

Lilian Herman

가입한 날짜: 2021년 11월 09일

·

마지막 활동: 2024년 6월 20일

팔로잉

0

팔로워

0

총 활동 수

27

투표 수

0

플랜 수

11

활동 개요

님의 최근 활동 Lilian Herman

Lilian Herman님이 에 댓글을 입력함

댓글Using the knowledge base in Help Center

No, I'm not referring to the number of subsections under a section.   I'm talking about the levels as in hierarchy structure.

From a ZD article:  You can have a maximum of six levels using nested sections: Category > section > section > section > section > section.

This states 6 levels, but that includes the Category.  I was referring to the number of section levels under a category. 

댓글 보기 · 2024년 6월 20일에 편집됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

댓글Using the knowledge base in Help Center

Is there any way to add more than 5 levels of sections?  Any one out there figured out a workaround for this?

댓글 보기 · 2024년 6월 13일에 게시됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

커뮤니티 댓글 Q&A - Help center and community

Thanks Jon. Unfortunately, I was not with the company when the custom code was implemented and there is no record of changes made, or why the changes were made.  I realize you cannot help with custom code, but do you have a list of changes to code that might have a negative downstream impact?  If not, something like a "tips and best practices when customizing your theme" article would be very useful in the future. 

댓글 보기 · 2023년 11월 17일에 게시됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

커뮤니티 댓글 Q&A - Help center and community

I'm trying to find out how to enable the language drop down selector for users who are NOT signed in.  We do not have 'require sign in' checked for our KC. We have visibility for some articles set to 'everyone.'  However, when viewing those pages, the language drop down is not enabled.  Our company recently merged with a company whose ZD KC is available to users not signed in, and they can access the language selector drop down, so I know this is possible. Any idea how I can replicate this behavior?

댓글 보기 · 2023년 11월 02일에 게시됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

댓글Working with articles in the knowledge base

Katarzyna,

Thanks for the response.  It would be much more useful if we could view which articles an image is in without having to access the replace modal. Hopefully, that's on the roadmap for an upcoming release. 

댓글 보기 · 2023년 6월 13일에 게시됨 · Lilian Herman

0

팔로워

2

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

댓글Working with articles in the knowledge base

Does the image gallery provide any indicators for which articles the images are inserted into? 

댓글 보기 · 2023년 6월 09일에 게시됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

댓글Supporting multiple languages in Help Center

Sorry I couldn't help! Our email address isn't in our footer, so I have no reference to offer more suggestions.  Good Luck!

댓글 보기 · 2023년 3월 03일에 게시됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

댓글Supporting multiple languages in Help Center

Have you tried using dynamic content?  Create a variant for each language that contains the appropriate email address, then replace the existing email address in the footer.hbs file with the dynamic content - something like this:  {{dc 'home_page_footer_office_email_address'}}.

댓글 보기 · 2023년 3월 03일에 게시됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

댓글Using themes and customizing your Help Center

Is it possible to use dynamic content in the javascript file?  I'm trying to localize the Contact Us button text:

 $('.request-callout a').text('Contact Us ').attr('href','/hc/requests/new');

I have the dynamic content {{dc.kc-footer-contact-button}}.

I know how to add these to the .hbs files and use them in many places. However, I'm not sure how, or if, it can be used in the javascript.

댓글 보기 · 2022년 7월 12일에 게시됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글


Lilian Herman님이 에 댓글을 입력함

댓글Supporting multiple languages in Help Center

Hi Erica,

Thanks for the quick response! 

The best outcome would actually be if articles only showed labels for the current browser language.  Showing all labels regardless of the language is going to be a huge issue once we add several more languages. 

But if we can't accomplish that, then this is an issue:

When you click a label in an article it opens search results based on that label.  Clicking a label always opens the results in the default language for the site, regardless of the language the browser is currently using. The preferred, and expected, behavior is that when using a browser in a language other than the default, and clicking a label in the translated language, the search results open in the translated language.  Perhaps the following image will help:

 

 

댓글 보기 · 2022년 5월 13일에 게시됨 · Lilian Herman

0

팔로워

0

투표 수

0

댓글