[wp-trac] [WordPress Trac] #16303: Improve documentation and usability of WP_Rewrite Endpoint support

WordPress Trac wp-trac at lists.automattic.com
Thu Jan 26 19:13:38 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                                       |
-------------------------------------------------+-------------------------

Comment (by lgedeon):

 Hi duck_

 Thanks for the feedback. I wrote this before the documentation update and
 missed that when I copy/pasted. BTW, thank you so much for updating the
 docs. This is a really cool feature and the doc helps make it available to
 more devs.

 I did see that add_rewrite_endpoint() adds the query_var but since I only
 need to call add_rewrite_endpoint() when rewrite rules are flushed and
 need the query var all the time, it almost makes sense to split them. The
 other option as you mentioned is to call add_rewrite_endpoint() all the
 time, on init. The function is light enough that it probably wouldn't
 hurt. I just had not decided yet... so I did half of both. :)

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


More information about the wp-trac mailing list