Harmonize some options with their UI label
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 66
- Forks
- 36
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Is your feature request related to a problem?
As time passes, our terminologies might change, and with it our settings page gets updates. Examples of this are "API Key" that has been renamed to "Site ID" and "Track as Page" that has been renamed to "Track as Non-Post".
In many of those cases, we quickly update the UI but not the underlying options. For example, the value of "Track as Non-Post" is still page. In large part, this is because renaming the options themselves can have undesired effects if not handled properly. However, this leads to out-of-sync code that can become harder to understand as time goes by.
Describe the solution you'd like
Find the affected options and give them a more representative name, making sure that:
- Nothing breaks.
- Upgrade path works.
- Downgrade path works.
Related PRs/issues:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the option names behind the “Site ID” and “Track as Non-Post” UI labels, along with the related issue #799 and pull request #1241. Identify all affected options and verify that upgrades and downgrades preserve existing settings without breaking behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100