Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #37336


Ignore:
Timestamp:
07/12/2016 07:17:11 AM (9 years ago)
Author:
swissspidy
Comment:

Thanks for your report! I could reproduce this by manually changing a post's slug in the database (simulating an already existing post with that slug).

This means a visitor cannot access a post with that slug, which is of course a no-go.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #37336

    • Property Keywords needs-patch needs-unit-tests added
    • Property Version changed from trunk to 4.5
  • Ticket #37336 – Description

    initial v1  
    1 In #34931, embeds were added to static frontpages, and there was a discussion of how this would affect an existing page with a slug of /embed/.
     1In #34971, embeds were added to static frontpages, and there was a discussion of how this would affect an existing page with a slug of /embed/.
    22
    33The solution was: