[wp-trac] Re: [WordPress Trac] #9825: Enforce permalink history, outright

[WordPress Trac]

#9825: Enforce permalink history, outright
-------------------------------+--------------------------------------------
 Reporter:  Denis-de-Bernardy  |       Owner:  Denis-de-Bernardy
     Type:  enhancement        |      Status:  accepted         
 Priority:  normal             |   Milestone:  2.9              
Component:  Permalinks         |     Version:  2.8              
 Severity:  normal             |    Keywords:                   
-------------------------------+--------------------------------------------

Comment(by Denis-de-Bernardy):

 @mike: Dunno... Just for reference, what I'd like to do is add some extra
 meta:

 On display with permalinks active, store the permalink in meta for future
 reference in case it's not in the meta already. In such a case, scan
 post_meta for other occurrences of this permalink. On conflict, delete the
 older one in order to give pre-eminence to the newer data.

 (It's worth discussing doing the same for unpaged taxonomy and author
 pages as well.)

 On 404, the canonical redirect would then scan old permalinks in case the
 REQUEST_URI is a known one, and redirect with a 301 code if a piece of
 data is found.

 So, basically the same as what's done with the old_slug meta, except that
 it would work for anything stored in the posts table (rather than merely
 posts), and that it would work when the post's date changes, when a page's
 parent changes, when the site's permalink structure changes, etc.

 Anyway, I'm assuming your plugin would continue to work fine as long as WP
 isn't returning a 404 error when your data gets called.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9825#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software