Duke Oliver

Heya! I love this tool, but am having an issue. Only about half of our articles get backed up (I'm using v0.6). The ones not getting backed up seem to be random, though I wonder if it's related to this message:

Depends on what kind of border, though it would most likely be the css "border" property instead of the "box-shadow" property. For example,

.markdown img {
    border: 1px solid black;
}

You can read more about borders and border styles at these places:

http://www.w3schools.com/css/css_border.asp

https://developer.mozilla.org/en-US/docs/Web/CSS/border-style

I was under the impression that a ticket going from Pending to Open via a requester's response was a non-configurable option, and as such should happen automatically. Does your previous IT director have a custom trigger that overrides this?

Hi Jason,

You have a lot of ways to achieve this! I'll show you what it's like in my own theme. 

In my theme editor on the Article page, I have {{article.body}} inside of a div with the classes "article-body" and "markdown":

{{article.body}} renders the entire article, including the images I placed with the article editor. If I go to any of my articles and use my browser's 'inspect' tool (right-click > inspect) I can see that there is indeed an image inside my "article-body markdown" div:

So now I need to go into my css and figure out how to target the image so I can give it a shadow. I believe the original theme I built on top of used "markdown" as the go-to classname for these kinds of edits, so I'll do just that. Here's the css selector:

This is selecting all img tags inside of the "markdown" class. Here's my shadow edit. I went ahead and targeted every single browser I could think of (except older opera versions, woops!), but really all you'll likely need are the ones I underlined:

Now if I preview my changes, I can see all my article images have shadows!

I hope this helps. Let me know if you'd like to know more

There's kind of a way with javascript. You're able to target the role of whoever is logged in (manager, agent, end_user, anonymous), and from there you can inject html or css. For example, typing HelpCenter.user.role into my browser's console will retrieve this:

From here, you could do a number of things. For my page, I'm using code similar to what's talked about here:

https://support.zendesk.com/hc/en-us/articles/203661316-Hide-or-show-HTML-based-on-user-s-role-or-group

Essentially, you'd have the comments only render on the page via javascript if the person logged in is an agent or manager. The caveat is that it gets complicated if you still want end-users to comment on articles too. I still think it's doable though.

If you'd like help setting it up, I'd be glad to help out!

Hi Rosie,

Is it possible to get a screenshot of your email template? It may be related to an issue I recently had. Gmail was adding a css class called .im to most of our zendesk emails, which made the text purple. So in my email template, I targeted the css and told it to be black instead:

What you could do is view the source of the email once it's sent, and do some poking around to find out what class you need to append your color to. If this is related to your question, I'd be happy to help out