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

Offen
  • Stimmt etwas nicht?
#509 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
1/5
Geschätzter Aufwand
Unter einer Stunde
Anfängerfreundlichkeit
55/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
php
Bereich
documentation

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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 :)

Vorherrschende Sprache
CSS
Sterne
22
Forks
79
Ø Merge
2 T. 1 Std.
Gemergte PRs (30 T.)
6

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ExpressionEngine/ExpressionEngine-User-Guide

Alle Issues in ExpressionEngine/ExpressionEngine-User-Guide

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.