[DevHub] Document non-uniqueness of WordPress GUID
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- wordpress
- Domain
- documentation
Research direction
Open the_guid() at https://developer.wordpress.org/reference/functions/the_guid/ and read its Description section, then check similar pages mentioned in the issue. Update the documentation to explain that WordPress does not enforce GUID uniqueness and that multiple posts may share a GUID; the issue is done when this expectation is clear to developers.
Written by the indexing model from the issue text.
Description
Issue Description
I noticed that WordPress documentation describes the post guid field as a "Globally Unique Identifier". Unfortunately, WordPress does not enforce a uniqueness constraint. In practice I've found posts with duplicate guid values, especially when using plugins that publish posts without going through the draft state. These tend to have GUIDs that match the fancy permalink.
URL of the Page with the Issue
Section of Page with the issue
Description
Why is this a problem?
Developers who are familiar with Microsoft GUIDs or IETF UUIDs, as commonly used on other platforms, will expect these IDs to be strictly unique. Example bugs include querying for posts by GUID and getting multiple results.
Suggested Fix
I suggest documenting that WordPress does not enforce a uniqueness constraint on the GUIDs and that multiple posts can share the same GUID.
- Dominant language
- Shell
- Stars
- 109
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
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.
More from WordPress/Documentation-Issue-Tracker
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
WordPress/Documentation-Issue-Tracker#2512 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
WordPress/Documentation-Issue-Tracker#2511 · 1 comment ·
-
[Status] Review developer documentation (DevHub) plugins
Difficulty 1/5 Under an hour Newbie friendliness 92/100
WordPress/Documentation-Issue-Tracker#2510 · 4 comments ·
-
[Status] In progress contributor documentation
Difficulty 1/5 Under an hour Newbie friendliness 95/100
WordPress/Documentation-Issue-Tracker#2505 · 4 comments ·
-
[Block] Buttons [Status] Review 7.1 user documentation (HelpHub)
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
WordPress/Documentation-Issue-Tracker#2497 · 4 comments ·
All issues in WordPress/Documentation-Issue-Tracker
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·