Please look at https://support.zendesk.com/hc/en-us/community/posts/5069348265242-Recently-Updated-Articles-Feed-?page=1#community_comment_5128638579738 

This is very good use-case where anonymous read would have helped. I implemented whole feed thing using custom objects but it works for signed_in users and require me hardcoding (a dummy end-user) credentials.

Why doesn't Custom Objects API respect agent/admin session on help-center pages? Why am I required to pass authorization header if I am already logged in help-center, and javascript is trying to read/write/update?

Hi Oliver

This can be easily implemented using some javascript, and Custom Objects. That said, right now there is limitation in custom object:

• Custom Object doesn't allow anonymous reading
• Custom Object write/update requests (jquery ajax, or fetch) don't honor current admin/agent session; that is, we are required to pass authorization header -- with username/password or token.

After reading your post, I wrote a quick POC code and it works fine for end-users (signed in users).

I guess, you can easily implement this kind of feed using Firebase or similar systems.

Let me see if I can show something in some days.

Edit: I think, you are looking for an internal page that allows your team to see what are changes; I guess, then it makes whole thing easy; I will share my code in some days.

Thank you

Abdul Qabiz

Diizana

I think, we can do a lot of good things if we have ability to allow anonymous users read (or probably do more CRUD stuff). I have to use firebase for some use-cases; if you can update permissions UI/API for custom objects to support anonymous use-cases, we can do a lot.

Hi

As of now that's not doable without using javascript; we don't recommend doing that. You can build your custom form, and use Zendesk API -- but then you have to maintain another piece of code; and you might not be able to use various other features (conditional fields, etc.).

Thank you

Abdul Qabiz

Diziana

Availability of Guide Help Center themes on Zendesk Marketplace has made it easier for customers to find and use good custom themes.

However, a lot of customers have reached out to us (Diziana - a Zendesk Authorized Partner) complaining that they aren’t able to upgrade the standard version of themes to developer version by paying the difference. They are required to purchase developer version separately, and reconfigure/customize it again.

We have tried to help some customers (who didn’t want to buy a developer version by paying full amount) by offering them a full version directly. This is something we can’t keep doing as a business, and we will really want customers be able to upgrade versions by themselves by paying the difference.

As a theme author and seller in the marketplace, we don’t even have tools to see who is trying our themes, who has purchased our themes, and to upgrade versions for our theme customers.

I have raised this concern with Zendesk directly a couple of times; and have requested many of these customers to share their feedback to Zendesk. Hopefully then this important feature might find a place on product development roadmap. I will request the concerned team to add essential features, as marketplace should have, for customers and sellers.

Thank you

Abdul Qabiz

Team Diziana

Hi @...

You can do something like this:

New Request Page:

New Request Page with a selected Form:

The selected form's card will be shown as active (blue color), and the form's card will be moved to first position. This is to make it easy to understand and related. As you can see Ticket Form 3 was moved to be in first position. This can be removed from the code.

You can open new_request_page.hbs of your theme, take back up of existing code, and replace code in the template that with the code shared below.

I have inlined all the styles and scripts, and the html structure is based on what we have in Copenhagen; it should work fine, but if it doesn't you can tweak. This is a good start.

If it doesn't work in your theme, then you should only copy the code within the comments (as highlighted below) and put in respective places in your template.

  

  

    {{t 'submit_a_request'}}
    
      {{follow_up}}
    
  

 
  {{!-- Tiles Code Starts Here --}}
  

    

      {{#each ticket_forms}}
        
            

              
              
{{display_name}}
            

        
      {{/each}}
    

  

  {{!-- Tiles Ends Starts Here --}}

  

    {{request_form}}
  



{{!-- TILES CSS and JavaScript Code Starts --}}


{{!-- TILES CSS and JavaScript Code Ends here. --}}

DISCLAIMER. THIS CODE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.

Thank you

Abdul Qabiz

Team Diziana

Hi Katie

It’s little tricky but doable. I will see if I can share a code snippet with you.

Cheers.

Abdul Qabiz
Team Diziana

Hi David

A custom js plugin can be created to to pull data from API, and sort in a way you wish; of course you will need to specify sort-order in labels.

I have another solution, appears to be cluttered but it works.

1. Add sortorder as label to your articles, e.g. sortorder:1, sortorder:2, sortorder:3, ...., sortorder:12; The article with sortorder:1 will appear on the top.
2. Modify your template to have something like following:

    {{#if promoted_articles}}
   
     
   {{t 'promoted_articles'}}
   
     
   
       {{#each promoted_articles}}
       
                   data-position="2"
               {{/is}} 
               {{#is identifier "sortorder:3 "}}
                   data-position="3"
               {{/is}} 
               {{#is identifier "sortorder:4 "}}
                   data-position="4"
               {{/is}}
               {{#is identifier "sortorder:5 "}}
                   data-position="5"
               {{/is}} 
               {{#is identifier "sortorder:6 "}}
                   data-position="6"
               {{/is}}
               {{#is identifier "sortorder:7 "}}
                   data-position="7"
               {{/is}}
               {{#is identifier "sortorder:8 "}}
                   data-position="8"
               {{/is}} 
               {{#is identifier "sortorder:9 "}}
                   data-position="9"
               {{/is}} 
               {{#is identifier "sortorder:10 "}}
                   data-position="10"
               {{/is}}
               {{#is identifier "sortorder:11 "}}
                   data-position="11"
               {{/is}} 
               {{#is identifier "sortorder:12 "}}
                   data-position="12"
               {{else}}
                   data-position="13"
               {{/is}}
                   
               {{/each}}>
                 
                   {{title}}
                 
               
   
             {{/each}}
           
   
         
   
       {{/if}}
     
     
     

That's it. Your promoted articles will follow the sort-order dictated by sortorder:X label. Of course, above code only support sorting up to 12 articles, you can extend the code to go further.

Regarding displaying in two columns, you don't need table. What you need depends on how you are showing things -- do you use bootstrap, or plain-vanila css, etc. If you can display a html list in multi-column layout using CSS multi-column which apparently works for all browsers except IE9. Of course, if your layout is based on CSS Flex or CSS Grid, you can do lot more.

You can see a simple example (showing multi-column list view) here: https://jsfiddle.net/abdulqabiz/o0usqy74/4/

Cheers

-abdul

--

Abdul Qabiz
diziana  •  twitter  •  linkedin  •  blog

Team Diziana

Diziana is creator of awesome ready-to-go Zendesk Help Center Themes, and has helped hundreds of organizations/companies with Help Center Branding and Customization.

@Felix - Awesome! This has been on list for long but I have been super lazy. Thanks for great work, a lot of people are already using it.

I would love to port it to Mac OSX, can we collaborate on that? 

Thank you

-abdul

--

Abdul Qabiz

Diziana