Simon

Hi Christopher Kennedy , any updates on this one?

Hi Christopher Kennedy,

Thanks for your reply.

The attachments are generally images embedded into the article. The script elementsToRemove is based on html such as and not the file type extension. Our content is structured as follows:

Category > Sections > Articles.

We have around 5 categories, 8 sections and 5-15 articles in each section.

Tagging Ifra Saqlain and Tipene Hughes who seem very knowledgeable in this area.

Hi Zendesk community,

It seems Zendesk's theming API has been upgraded from v3 to v4.

I have a question regarding the change to {{categories}} and the fact that "articles" has been removed entirely from being called from the categories object on the homepage. Our custom design relies on being able to list articles on the homepage under sections. Does this mean articles can be called via another object or has it been removed entirely?

Requirement

How can I call a list of articles that belong to a specific section on the home_page.hbs template?

Currently, on API v3 I use:

{{#each categories}}
{{#each sections}}

{{#is id 123456789}}

{{#each articles}}
   

   
{{excerpt title characters=40}}
   
{{excerpt body characters=100}}

   
{{/each}}

{{/is}}

Will I instead need to inject a list of articles via a script? If so, will I face an issue with API rate limiting or API limits?

Potential solution

I've been testing our a script which works well but I am running into an issue whereby the browser is downloading all attachments associated with the article as it's in the .json data.

My aim is to have two types of lists in the home_page.hbs.

• A list of articles that live under a section. Only the title is required along with understanding if it's an internal article or promoted.
• A preview of the articles that live under a section. Only the title and an excerpt are required.

1. How can I stop the browser/script from downloading the attachments associated with the article the script is access via the API? 
2. And how can I also limit the article list to a maximum of 6 and include a "See all X articles? button?

Thank you in advance!

Hi Zendesk community,

It seems Zendesk's theming API has been upgraded from v3 to v4.

I have a question regarding the change to {{categories}} and the fact that "articles" has been removed entirely from being called from the categories object on the homepage. Our custom design relies on being able to list articles on the homepage under sections. Does this mean articles can be called via another object or has it been removed entirely?

Requirement

How can I call a list of articles that belong to a specific section on the home_page.hbs template?

Currently, on API v3 I use:

{{#each categories}}
{{#each sections}}

{{#is id 123456789}}

{{#each articles}}
   

   
{{excerpt title characters=40}}
   
{{excerpt body characters=100}}

   
{{/each}}

{{/is}}

Will I instead need to inject a list of articles via a script? If so, will I face an issue with API rate limiting or API limits?
 

I've got a potential solution that I need some help with: https://support.zendesk.com/hc/en-us/community/posts/7551780567578-Listing-articles-in-the-home-page-hbs-template-via-curlybars-or-an-API-script-API-v3-to-API-v4

Problem

We are ingesting ticket information in bulk via the Zendesk incremental api (/api/v2/incremental/ticket_events.json?start_time={startTime}&include=metric_sets).The incremental ticket event API is not showing comment authors correctly for Messaging/Chat tickets. For example, when we pull the ticket events via the Zendesk incremental API (/api/v2/incremental/ticket_events.json?start_time={startTime}&include=metric_sets), comments are not assigned to an agent, but to user -1 which is a system user. We need to be able to see within the data which agent made comments, not just that they were made by the system.

Impact

Without this data available within the incremental ticket event API, we are unable to import data about which agent made the comment which is critical information for our reporting.

Potential Solution

Zendesk has suggested iterating through each ticket via  the comment_events API (sideloading) which will provide the author_id but this will increase API calls significantly and the cost may outweigh the benefit and add unnecessary load to our servers importing the data.

+1: This should be prioritised.

Gorka Cardona-Lauridsen does Zendesk have any plans to create such a feature to alert Zendesk admins when a connected email account fails authentication or disconnects via email, in-app or other means?

When will HTML be supported in content blocks? I agree with some in that it is a blocker for us as we use a lot of custom HTML elements within our articles. 

Max McCal

Do you know if there is a way to block certain filetypes from being attached via the contact form using Javascript?

Thanks for the update Gorka Cardona-Lauridsen.

I will follow the announcements and wait to see how it might help my specific need.