Channel Entries Tag > dynamic_parameters links to itself instead of further info

Aberta
  • Algo errado?
#509 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
1/5
Tempo estimado
Menos de uma hora
Facilidade para iniciantes
55/100
Tipo de issue
Documentação
Clareza
Claramente especificada
Status de atividade
Estagnada
Stack de tecnologia
php
Domínio
documentation

Direção de pesquisa

The issue identifies the Entries Tag documentation and the incorrect Dynamic Parameters link, with the intended destination at channels/dynamic-parameters.html. Find the notes beneath the code example in the Entries Tag page and update the link to that destination. Done when the link opens the Dynamic Parameters documentation.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

If we go to Channels → Entries Tag → dynamic_parameters= here we can see that, in the notes under the code example, the link to Dynamic Parameters just takes us to the very place we're already at.

I think it was meant to link to Channels → Dynamic Parameters here instead? Certainly would make more sense, and it's a pity if people miss all the excellent notes on Dynamic Parameters available there.

By the way, does anyone ever check these Documentation Issues? Does anyone ever fix them? There are open ones going back to 2018/2019, and the last closed one is from January.

Seems low priority, and of course, it is, compared to "real" bugs. Just remember that the Docs is what newcomers to EE meet first, and even a wrong link can be the straw that breaks a potential new users back, and sends them looking for a nice WP theme instead — ewww, I mean just ewww! ;-)

I would help more than just adding these issues, but I'm just not comfortable enough with GitHub, that pushing and pulling doesen't terrify me, and makes me certain I'll break a lot more than I'll fix :)

Anyways, would be nice to see some of these fixed — and maybe I should look more into doing these myself instead of complaining, but in the meantime, there are many 10-second fixes (like wrong links) in here, for those who are GitHub Pros :)

Linguagem predominante
CSS
Estrelas
22
Forks
79
Merge médio
2d 1h
PRs com merge (30d)
6

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ExpressionEngine/ExpressionEngine-User-Guide

Todas as issues de ExpressionEngine/ExpressionEngine-User-Guide

Issues semelhantes

Mais issues de Documentation

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.