Pesquisas recentes
Sem pesquisas recentes

Matt Dietsche
Entrou em 24 de out. de 2024
·
Última atividade em 24 de out. de 2024
Seguindo
0
Seguidores
0
Atividade total
1
Votos
0
Assinaturas
0
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Matt Dietsche
Matt Dietsche criou uma publicação,
We migrated our old WordPress-based help site to Zendesk's Help Center. Our plan was to set up an Nginx wildcard redirect from our old url structure to the new article url structure used by Zendesk. I thought it would be something like this:
server old.support.domain
location /old/path/to/(?.*) {
rewrite ^ $scheme://new.zendesk.domain/hc/en-us/articles/$article-name redirect;
}
This rewrite would catch any articles where the article name remained the same after migration. The problem is that ZD's url structure includes the article ID, which makes this approach impossible.
new.zendesk.domain/hc/en-us/articles/381290381290312-article-name
Is there a work around for this? Obviously would like to keep the SEO we've built for our support articles. Seems like the alternative is adding a custom redirect for every article, url to url, which is a daunting task with the number of articles we have.
Surely other companies have migrated help content over to Zendesk like this…
Publicado 24 de out. de 2024 · Matt Dietsche
0
Seguidores
1
Votos
1
Comentário