[wp-meta] [Making WordPress.org] #174: Link to generally related functions/classes

Making WordPress.org noreply at wordpress.org
Tue Jul 19 22:20:13 UTC 2016

#174: Link to generally related functions/classes
 Reporter:  samuelsidler   |       Owner:
     Type:  task           |      Status:  assigned
 Priority:  high           |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:  has-patch      |

Comment (by keesiemeijer):

 I doesn't matter if it's another taxonomy or a p2p connection. It's just
 that we cant use the title keywords taxonomy for user contributions. I
 would rather see the title keywords terms be added when importing or
 updating functions with the parser. By using another taxonomy or p2p
 connection (for functions) you have a list of functions for users to
 choose from. That was the main idea.

 >p2p also already supports autocomplete for adding connections.

 You also get autocomplete for free with a taxonomy in the edit posts
 screen (when adding a term) as all posts will have their own name as a
 term to begin with. I don't know p2p well enough to know if it supports
 autocomplete on the front end as well.

 A downside to using a (function) taxonomy is that 6430 terms need to be
 created for the users to choose from. Upside is you only have to query
 taxonomy terms

 Another thing to think about is that the parser ships with the p2p library
 only, without the admin functionality. https://github.com/scribu/wp-lib-

 It creates fatal errors when parsing if both the library (used by the
 parser) and p2p plugin are activated. So that has to be fixed before we
 can use the p2p plugin in the dashboard

Ticket URL: <https://meta.trac.wordpress.org/ticket/174#comment:26>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list