DonnaJ

But, it looks from what you provide, above, that I would have to run the 2nd option for EACH article to find which ONES have attachments. Is there no way for something to look at all articles and tell me which ONES have attachments?

Is there a way to find Help Center article that have attachments? I know we have only a few, but I don't know which articles!

I'm using Paligo to manage my ZD content and will publish from Paligo to Zendesk. I notice, in test publishes, that with existing ZD articles, when Paligo publishes to ZD, it ADDS a new set of images to the ones already there (because Paligo uses a UUID naming convention to ID images for their database.) What I'm left with, after the first publish into ZD, is a duplicate set of images, ones with the original names (stock_web_image.png) and another with a complex UUID named version (UUID-[bunches of numbers].png)

Is there any way to find and delete the original images without having to go manually through my 800+ article repository and use the clunky check and delete process for each article?

I don't think this is a "problem" of kBackup. Why can't I get anyone to just tell me HOW duplicate images are handled in Zendesk? If I use "icon.png" 3 times in a single article, but I've only uploaded it into that article ONCE - what's in the image repository?

I see this in the HTML code:

https://support.zendesk.com/hc/article_attachments/360052360694/i_icon.png" alt="i_icon.png"> each time the image appears, but I have no direct access to "article_attachments" to be able to see what's actually STORED there.

I've just posted this same question as a support request, but want to ask it here, too:

--------------------------------

Having recently used kBackup to download my entire Guide repository, I am trying to understand how Zendesk saves images.

I have one article that uses the same image (i_icon.png) three times in the article. When I look for that image in "Article Images" - I see it ONE TIME.

BUT kBackup has downloaded the same image THREE times, each named with numbers appended to the original file name. So I have:

* i_icon.png
* i_icon_1.png
* i_icon_1_2.png

The HTML in the article only refers to "i_icon.png", not the other names... WHY does Zendesk duplicate repeated images even in the SAME article.

This will cause problems when I'm moving my repository to another system, as I have to figure out how to clean up duplicate images without breaking my articles.

Because of this duplication, my Zendesk Guide repository has over 8000 images. I do not need to bring all 8000 into my new system, but de-duplicating is going to be a major project.

@...: Can you tell me how the file names that I get running kBackup are derived?

The article files often have "..." so I'm guessing that you're chopping the name at some point. What can you tell me about the image files? They can have ridiculously long names and do not seem to cut off the names like is done with the .HTML files.

How do these names relate to what Zendesk is actually storing?

Thanks,

Donna

I want to have multiple versions of an article and then deliver the right version to a user based on what COUNTRY they come in from. Is there a way to set this up? FYI, not talking about language support for this - all versions would be English.

I have individual articles with 36+ sometimes more labels. I want to bulk-delete all of these labels because when they were added, someone was under the impression that the more words in a label, the better. Ugh. This is stuff that should have been in there from the beginning... not as a 5-year-old afterthought that's just now getting some implementation attention.

Just wanted to add my thanks for a great tool. We have SSO and so Felix pointed out that I'd have to have a non-SSO login. Once I got that kBackup worked like a charm. We have (for now) a pretty simple configuration, so I just needed to get "Help Center" and not worry about anything else. But over 800 articles and 8200+ images all on my desktop now (well in a "Backup..." folder) so I can cull articles and images.

Thanks!

Donna