![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 14 years ago
Closed 11 years ago
#23166 closed defect (bug) (duplicate)
Post/Page slug collision
| Reported by: | AKTed | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Permalinks | Version: | 3.4.1 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
If you create a page with the same slug as a post or vice versa, WordPress doesn't notice the slug collision. It doesn't append a -2 like it would if the collision were post/post or page/page. The post becomes inaccessible; the page effectively "owns" the slug.
I'm not sure if this is a bug, or just the way it's supposed to be.
Change History (6)
#3
@
11 years ago
- Resolution duplicate
- Status closed → reopened
- Version 3.5 → 3.4.1
Sorry, a Version is 4.3.1
#4
@
11 years ago
- Resolution → duplicate
- Status reopened → closed
- Version 3.4.1 → 3.5
Duplicate of #13459.
#5
follow-up:
↓ 6
@
11 years ago
- Resolution duplicate
- Status closed → reopened
- Version 3.5 → 3.4.1
Yes @helen I already through out the ticket [ #13459] provided patch is only applicable on 2.9.2 while I am using latest Version 4.3.1.
I have searched several and no luck at all. If you want to reproduce the bug I will write a step of the process.
I don't understand why this is not fixed on Wordpress Core since 2.9.
I am not able to modify ticket for latest Version 4.3.1
Thank you.
Duplicate of #13459.