Establish protocol/procedure for issues discovered with README.md file found in bp-documentation /data/

[emaralive]

Since each entry has key elements/attributes/cells such as Page ID and Link (contains the Page ID), should a ticket be opened so that someone who has access to see the Page ID can make a correction to the README.md file located within bp-documentation /data/?

Case in point:

https://github.com/buddypress/bp-documentation/tree/trunk/data#:~:text=2013/04/02-,29,-%E2%80%94%20%E2%80%94%20FAQ

The following represents line 249:

---

29 | — — FAQ | https://codex.buddypress.org/?p=29 | 2008/07/16

---

The link leads to a 404 page, the intended page is located at the following (utilizing a menu on codex.buddypress.org):

https://codex.buddypress.org/legacy/getting-started/faq/

However, this is the pretty URL and not the URL with the Page ID, thus, someone other than me, needs to make the correction.

I just want to confirm that this is the process/protocol/procedure that should be used (open a ticket) and depending on the actions/steps that need to take place will determine the assignee for the remedy..

Edit - Just remembered something that happened to me during a dev-chat whereby a link with a Page ID was posted which resulted in a 404 page for me which was due to me not being able to view that specific page. Not sure if this is a similar situation, in case the page link is actually valid.

Edit 2 - See issue #28 which is setting this page to ignore.

[imath]

Hi @emaralive

In such a case, you can directly edit the data/README.md file on GitHub.com or from a local clone of the repository. In both cases you'll need to write a commit to explain what you changed. Eg: fix a wrong link or mark a line as ignored or to inform an issue was created.

It's not the same situation than last time, it's weird WordPress doesn't manage to redirect the plain link to the pretty one.

[emaralive]

I utilized the pretty URL in the issue and set the issue to ignore.