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

未关闭
#509 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
55/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
停滞
技术栈
php
领域
documentation

调研方向

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

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ExpressionEngine/ExpressionEngine-User-Guide 的其他 Issue

查看 ExpressionEngine/ExpressionEngine-User-Guide 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。