Channel Entries Tag > dynamic_parameters links to itself instead of further info
還沒有人認領這個 Issue。
評估
- 難度
- 1/5
- 預估耗時
- 1 小時以內
- 新手友好度
- 55/100
- Issue 類型
- 文件
- 描述清晰度
- 描述清楚
- 活躍度
- 停滯
- 技術堆疊
- php
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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 :)
- 主要語言
- CSS
- 星號
- 22
- 分支
- 79
- 平均合併
- 2 天 1 小時
- 30 天內合併 PR
- 6
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
ExpressionEngine/ExpressionEngine-User-Guide 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 72/100
-
難度 1/5 1 小時以內 新手友好度 55/100
-
難度 2/5 1-3 小時 新手友好度 45/100
-
難度 1/5 1 小時以內 新手友好度 55/100
-
難度 2/5 1-3 小時 新手友好度 46/100
查看 ExpressionEngine/ExpressionEngine-User-Guide 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
Textualize/textual#6753 · 1 則留言 ·
-
area: core area: docs good first issue help wanted lane: free-agent priority: P3 roadmap size: XS type: task
難度 1/5 1 小時以內 新手友好度 86/100
arminazimi/seaworthy#701 ·
維護者通常 1 天內回覆
-
Use registered media types for HDF5 and NetCDF, and stop claiming media_type must be IANA-registered未關閉documentation metadata
難度 2/5 1-3 小時 新手友好度 87/100
維護者通常 1 天內回覆
-
bug good first issue
難度 1/5 1 小時以內 新手友好度 90/100
elhajahmadj/offline-emergency-library#156 ·
維護者通常 1 天內回覆
-
7.2 user documentation (HelpHub)
難度 2/5 1-3 小時 新手友好度 72/100
WordPress/Documentation-Issue-Tracker#2559 · 1 則留言 ·