[wp-trac] [WordPress Trac] #30910: future post permalink can be revealed when blog article requested by url like ...?p={post_id}
WordPress Trac
noreply at wordpress.org
Sun Feb 1 23:15:10 UTC 2015
#30910: future post permalink can be revealed when blog article requested by url
like ...?p={post_id}
-------------------------------+---------------------------
Reporter: e.mazovetskiy | Owner: boonebgorges
Type: defect (bug) | Status: reopened
Priority: normal | Milestone: 4.2
Component: Posts, Post Types | Version: trunk
Severity: normal | Resolution:
Keywords: has-patch | Focuses:
-------------------------------+---------------------------
Changes (by DrewAPicture):
* status: closed => reopened
* resolution: fixed =>
Comment:
Looks like [31114] inadvertently introduced a regression in terms of how
the sample permalink markup is displayed in edit-form-advanced. I actually
noticed that while posting on the make/core P2 which runs trunk. The
sample permalink was neither visible nor editable for scheduled posts:
[[Image(http://f.cl.ly/items/2E2H0n0L241I1Y3E1K10/Screen%20Shot%202015-02-01%20at%204.02.01%20PM.png)]]
Turns out, we missed adding the 'future' post status to the exception list
in `get_sample_permalink()`. This is covered in [attachment:30910.diff].
Without adding 'future' to the exception list, when `get_permalink()` is
called with the `$leavename` parameter set to true, the permalink fragment
that gets passed through doesn't have the `%postname%` or `%pagename%` tag
included, which ultimately results in it failing checks for a sample
permalink in the UI. Interesting bug to track down.
[attachment
--
Ticket URL: <https://core.trac.wordpress.org/ticket/30910#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list