[wp-trac] [WordPress Trac] #16303: Improve documentation and usability of WP_Rewrite Endpoint support
WordPress Trac
wp-trac at lists.automattic.com
Wed Jan 25 22:34:58 UTC 2012
#16303: Improve documentation and usability of WP_Rewrite Endpoint support
-------------------------------------------------+-------------------------
Reporter: westi | Owner: westi
Type: defect (bug) | Status: new
Priority: lowest | Milestone: Future
Component: Rewrite Rules | Release
Severity: normal | Version: 3.1
Keywords: westi-likes has-patch commit dev- | Resolution:
feedback |
-------------------------------------------------+-------------------------
Changes (by duck_):
* keywords: 3.3-early westi-likes has-patch commit dev-feedback => westi-
likes has-patch commit dev-feedback
Comment:
I attached a new version of the improved functionality patch.
However, there are a couple of issues:
* Should EP_ROOT be included in EP_ALL_ARCHIVES? It depends on the
page_on_front option as to whether or not it's an archive.
* Is EP_CPT_ARCHIVE usable? This was alluded to in previous comments.
register_post_type() uses WP_Rewrite::add_rule() when creating rewrites
for CPT archives, and this means no endpoints.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/16303#comment:17>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list