Diego Hernandez

Hello, we have been able to sync our Zendesk themes to a GitHub repo with the integration feature.

Afterwards we were able to setup local development via the ZCLI tool as described here.

this all works flawlessly, however I am missing two things for which I could not find any explanation in the documentation nor in the product's git repo:

• Dynamic contents are not loaded, the Preview loads instead "could not find placeholder for dynamic content *name of dynamic content" messages. Since a Zendesk theme dynamically loads a specific localized dynamic content as specified in the Dynamic Contents section of the Admin area, this content is not downloaded or included along with the local copy of a Theme, therefore shoud I assume that {{dc }} placeholders cannot be loaded when developing the theme locally?

• Theme assets are not displayed. Inspecting them in the DOM tree does not show any network errors but the URL begins with $assets - so this mean a specific URL is not generated. I thought this might related to the mixed contents topic discussed here: https://github.com/zendesk/zcli/blob/master/docs/themes.md  but it seems that running the theme:preview command with added certificate parameters does not make any difference
  
  

thanks, /Diego

The ZCLI is an improvement to the previous options, thanks for that.

What I am currently not achieving:

• theme assets are not displayed. Inspecting them in the DOM tree does not show any network errors but the URL begins with $assets - so this mean a specific URL is not generated. I thought this might related to the mixed contents topic discussed here: https://github.com/zendesk/zcli/blob/master/docs/themes.md  but it seems that running the theme:preview command with added certificate parameters does not make any difference
• Dynamic contents are also not loaded, the Preview loads instead "could not find placeholder for dynamic content *name of dynamic content" messages. I could not find any info on the documentation / KB articles.

thank you,
/Diego

Hi, our SSO setup is currently not working, the login attempt does not redirect to our zendesk instance , instead the return url is as follows:

https://*remoteURLdomainName*/en/?email=&external_id=&kind=error&logout=1&message=Please+use+one+of+the+options+below+to+sign+in+to+Zendesk.

JWT has been configured in the Admin center with the correct remote login URL . Any hints as to what this error above could indicate? Our hosting team does not identify that error as coming from them. 

thanks,
Diego

When I preview my theme via $zat theme preview and paste the /start link in my Chrome URL, I receive a 'blocked by CORS policy' error in the console. The origin is my own subdomain URL as expected, and it attempts to fetch at *myMappedDomain*/hc/activity. , which is a URL that throws a 404 error so as far as I can tell, the theme loads trying to fetch data from a page that doesnt exist. This is not part of our code in the templates.

I did allow for mixed contents to be loaded as per a this article, but there is no mention specifically about the CORS issue.

While I do use ZAT Tools in this case the troubleshooting step of the Troubleshooting CORS article:

As part of the Apps framework, a back-end proxy server is available via the client.request() call. Use this proxy by setting cors:false in the client.request's settings (note: false is also the setting's default value).

does not help since I have the "special case" of previewing the Zendesk Theme which I downloaded from the Guide, there are no explicit client requests being made in the theme files .

/thanks,

Diego

Hi Karen, thanks for the swift reply!

Indeed this change took place after I had been pasting some code in the current sandbox theme in order to test the unified search features. By debugging the code I have not yet been succesful at determining what causes the change- for one, the article suggestions box is generated dynamically so a script should be triggering it... I may still be able to find the cause but thought also about asking here in parallel.

As for your question, yes I also had to look around to find out how to pause the code execution. The trick is, you right-click on  the class="community-enabled"> element in the Elements inspector and from the context menu select Break On > subtree modification. Now if you type a term in the search bar, when the autosuggestions menu is being generated, the code pauses because a DOM subtree has been added to the body element. You may have to do 1 or 2 "next step" clicks in the Sources debugger but then the entire menu shows up along with its elements and properties.

Thanks for the support,
Diego

Hi, I am encountering a problem related to the zd-autocomplete-multibrand style, which has changed and am not able to backtrack when this new style overtook the previous one.

In the below screenshots I show

1. the code for an earlier theme with the usual autocomplete style, which includes a zd-autocomplete-header and multiple zd-autocomplete-option entries.

2. the code of the current theme which displays a different style with no header and zd-autocomplete-multibrand entries.

The code is generated from the template helper {{search}} I believe, but I would not know what options control the style. There is a class parameter as documented, but no examples. 

https://developer.zendesk.com/apps/docs/help-center-templates/helpers#search-helper

Any ideas how this new code could have slipped in? //thanks