Trouble with URLs

[AndrewLeonard]

1. Create a page called "XXX"
2. Make it private
3. Make a Post called "XXX"

If you can, look at the archive posts for today and you will find your Post
If you click on the title of the Post, "XXX", if you are logged in you will be sent to your private Page, if you are not logged in you will get a 404

I am using theme 2014 with all the plugins disabled

[joyously]

You didn't state what your permalink structure is set to, but it sounds like you chose to use the post name. You are getting the expected result when naming a post the same as a page. The pages are checked before the other types since they are unchanging.
The question is really about whether the post should have a slug of xxx-2 or not.

[SergeyBiryukov]

Hi there, welcome to WordPress Trac!

Thanks for the report, we're already tracking this issue in #13459.

[AndrewLeonard]

What is the point you are making?
#13459 was created 12 years ago and the same problem persists?
Why is this important?
In my case, our WordPress site is used by more than one person, so it is quite possible for someone to create a post with the same name as someone else who has created a page, or the other way around. Google Console then flags up a coverage issue saying that an indexed page is returning a 404.
Would it not be better to fix this issue rather than accumulate multiple duplicate reports and then set the status to closed - what is the point of that?

[costdev]

@AndrewLeonard Having multiple tickets that report the same issue, each with a different amount of information and possibly with different fixes means that whichever fix is committed may not take all available information into account.

The point of marking a ticket as a duplicate is to keep the discussion surrounding the issue and the fix in one place.

While I agree that it's disappointing that this issue has not reached resolution, we try to fix all verified bugs that are reported.

In this case, the issue has persisted for a very long time. We run bug scrubs to try to pick up some of these older issues and move them closer to resolution. Marking as a duplicate verifies that the issue is still a problem in the current version of WordPress and reinforces the need for the issue to be resolved.

[AndrewLeonard]

12 years?
I apologise for bothering you, I won't make this mistake again