Editing the article's author, date, and timestamp

Have more questions? Submit a request

43 Comments

  • Anthony de Bruyn
    Comment actions Permalink

    How can I change the published date of individual articles? I am migrating our blog content to Zendesk and would like to timestamp some posts in the past.

    0
  • Laura Hippert
    Comment actions Permalink

    Hi Anthony!

    The date helper will only display an automated date, based on when the article was created or updated. However, if you wanted to override the date helper for a few select articles, You could implement something like the following:

     <div class="article-updated meta-data">
    {{#is article.id 115002323527}}
    {{t 'updated'}} 2 Years Ago

    {{else}}
    {{t 'updated'}} {{date article.updated_at format="full"}}

    {{/is}}

    You would implement the #is helper to add a manual date (in my example I said "2 Years Ago") for the article that matches the ID that you have referenced. You would need to repeat the #is statement for each migrated article. Once you have done that, the else statement determines that the date helper is used for all other articles, that aren't specifically called out. I hope that helps!

    1
  • Anthony de Bruyn
    Comment actions Permalink

    Awesome, it works! Thank you!

    0
  • Anthony de Bruyn
    Comment actions Permalink

    Hello Laura, I was cheering a bit too soon unfortunately ... I'm getting a syntax error when repeating the #is statement:

    <ul class="article-updated meta-data">
    {{#is article.id 115000491434}}
    {{t 'updated'}} 2017-06-02
    {{#is article.id 115000559053}}
    {{t 'updated'}} 2017-06-01
    {{else}}
    {{t 'updated'}} {{date article.updated_at timeago=true}}
    {{/is}}
    </ul>

    What am I doing wrong?

    0
  • Laura Hippert
    Comment actions Permalink

    Hi Anthony! What you'll actually need to do is close out each individual #is statements at the end, which is why you are getting the syntax error. You'll also want to include the else after each statement, so we can nest them. It will look something like this:

    <ul class="article-updated meta-data">
    {{#is article.id 115000491434}}
    {{t 'updated'}} 2017-06-02
    {{else}}
    {{#is article.id 115000559053}}
    {{t 'updated'}} 2017-06-01
    {{else}}
    {{t 'updated'}} {{date article.updated_at timeago=true}}
    {{/is}}{{/is}}
    </ul>

    Basically, this allows you to nest multiple #is statements, while maintaining one #else statement for the whole lot. 

    Does that help?

    0
  • Anthony de Bruyn
    Comment actions Permalink

    Works like a charm, thanks!

    0
  • Heather R
    Comment actions Permalink

    Great article! We commented out the parts we didn't want to display so that we can add them back in easily if we change our minds.

    Thanks again.

    0
  • Stephen
    Comment actions Permalink

    How is the 

    {{t 'updated'}}

    field handled for different languages? I think this is not our own configuration, but if we wanted to change it, is the only option through Dynamic Content management? Specifically we find that the Spanish should be Actualizado instead of Actualización. Could Zendesk consider a universal update?

    0
  • Diogo Maciel
    Comment actions Permalink

    Hi Stephen!

     

    While this is not currently in our roadmap, it could be implemented in the future. Please make a post in our Product Feedback page, which is checked constantly by our developers when defining our future updates

     

    https://support.zendesk.com/hc/en-us/community/topics/200132066-Product-feedback

     

    Cheers!

    -1
  • Stephen
    Comment actions Permalink

    Sure - but I find it utterly ridiculous that I am paying you for a service, giving you feedback, and you are asking me to send my feedback again elsewhere. The Product Feedback page has 83 pages of ideas: some 2400 product feedback submissions. As a customer, I don't feel very well heard or valued throwing my feedback into a seemingly disorganized pot, nor do I want to try to organize my feedback on your behalf. In my opinion, if you value my feedback, you will handle the feedback yourself.

    0
  • Jessie Schutz
    Comment actions Permalink

    Hi Stephen!

    Thank you so much for sharing your input on this.

    I agree with you - the current process for collecting customer feedback and suggestions in the Community is far from ideal. The Product Feedback forum was started back when we were small, scrappy little start-up, and as we've grown the processes we put in place then have not aged well as we've grown.

    I spent a considerable amount of time over the last couple years working with the former Director of Product Management to understand the needs and pain points of the people who use the Product Feedback forum, including going to San Francisco to meet with our PMs at their annual summit, and Nicole is now working with our PMs and Voice of Customer team to continue those conversations.

    We've already implemented several new processes and policies to improve the experience of both our customers and our Product Managers, including aggregating thread information to pass along to Product Managers, consistent monitoring and updating of threads, content management to reduce duplicate and outdated posts, and starting pro-active conversations led by our PMs for customers to share their use cases.

    I completely understand why you don't want to re-post your suggestion in Product Feedback; asking our Community Members to re-post their feedback in another part of the Community increases the effort they have to put in, and we don't like having to do it. Unfortunately, our platform doesn't let us move thread comments to other parts of the Community; otherwise I would be happy to do that for you.

    I can definitely bring your feedback to the attention of the right folks; what I'm reading is that the {{t 'updated'}} placeholder is rendering something grammatically incorrect in Spanish. Am I understanding that correctly?

     

    1
  • Stephen
    Comment actions Permalink

    Thank you for the understanding and insight into the Product Feedback developments, Jessie. Much appreciated. 

    Yes, you are understanding correctly that I am concerned that the {{t 'updated'}} placeholder is rendering something grammatically incorrect in Spanish.

    0
  • Jessie Schutz
    Comment actions Permalink

    Thanks for verifying, Stephen!

    I'll pass that along to see if we can get that corrected on our end. Have a great weekend!

    0
  • Merav B
    Comment actions Permalink

    Hi Jessie,

    I was trying to change the date on the search results template page, because I'd like the date that the article was updated to appear on the search results, rather than the date it was created because many articles were created 2-3 years ago, but are constantly updated and still relevant. Users won't trust to click on a search result for an article 3 years old, even though it was updated 1 month ago.

    I am getting an error when I make the following change from "created_at" to "updated_at"

    Can you please assist me on this? thanks! 

    0
  • Jessie Schutz
    Comment actions Permalink

    Hi Merav!

    Offhand, it looks like your syntax is a bit off. Try this:

    {{date article.updated_at timeago=true}}
    0
  • Merav B
    Comment actions Permalink

    Thank you Jessie

    I tried that and it still get the same error as above "invalid reference"

    Anything else I can try?

    thank you

     

    0
  • Jessie Schutz
    Comment actions Permalink

    Hey Merav!

    Hm...I think, in that case, that you're having trouble because that placeholder can't be used on the search page. You'll probably need to use some JS to make those changes. Let me check with some of our Community Moderators; they should be able to help you out!

    0
  • Trapta
    Comment actions Permalink

    Hi @Merav B,

    Try using this -

    {{date edited_at timeago=true}}

    Team Diziana

    0
  • Merav B
    Comment actions Permalink

    Thank you @Trapta ! 

    That worked.

    Merav

    0
  • Hillary Deal
    Comment actions Permalink

    I tried this, and it worked for articles recently created/updated, but articles that we merged from our old Zendesk are not being affected. Thoughts?

     

    0
  • Jessie Schutz
    Comment actions Permalink

    Hi Hillary!

    I'm not sure why that would be the case. Can you give me more information about what exactly you're encountering here? How did you migrate that content?

    0
  • Hillary Deal
    Comment actions Permalink

    Well, it turns out not all new articles are updating with "updated date" as I previously thought (it was basically only 1. lol) I am not sure how our content was migrated over. That was done before I began working with this company. However, my goal is to show the updated "date" on the category page.

    0
  • Ray Roth
    Comment actions Permalink

    Hey Hillary,

    Unfortunately customizing the default theme code it outside the scope of support we provide, however our community is a great place to ask questions like this as many of our other users often have good feedback. 

    0
  • Ole Lindtveit
    Comment actions Permalink

    Hi, 

    I've successfully hidden article meta data in the article view. But when searching, the search results are provided with author and modify-date. Can anyone provide the "how-to" for removing meta data also in the search results? 

    1
  • Vera Henrichs
    Comment actions Permalink

    Hi! I've tried to follow the steps, but it has become much easier than what is written. If you go to Guide Admin > Customize design icon. Then in the Design editor, select view theme. 

    Instead of editing the code there is a whole row of options on the left and on the page you can easily uncheck the Author on the Article-section

    0
  • Jessie Schutz
    Comment actions Permalink

    Thanks for sharing, Vera!

    0
  • Merav B
    Comment actions Permalink

    I don't see the any row of options on the left  that Vera is referring to. Can anyone help me understand what she is referring to please? :)

    I am in my "View Theme" and I see Colours/Fonts/Brands/Images on the left pane, but no checkboxes for Author.

    thanks!

    Merav

    0
  • Vera Henrichs
    Comment actions Permalink

    Hi Merav, Sorry I should have be more clear. When in View theme you have "elements for articles" on the left and there's a checkbox for author. Here it's in Dutch:

    0
  • Merav B
    Comment actions Permalink

    Hi Vera, 

    Thanks for that. I checked where you indicated, and it's not there.  I have a heavily customized theme, so I suppose that's why I don't have the Elements of the Article component available.

    Merav

     

    0
  • Jessie Schutz
    Comment actions Permalink

    Hi Merav!

    What Guide plan level are you on? If you're on a lower plan it's possible that don't have access to that level of customization.

    0

Please sign in to leave a comment.

Powered by Zendesk