Changes between Version 2 and Version 3 of Ticket #174, comment 26
- Timestamp:
- 07/19/2016 10:36:41 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #174, comment 26
v2 v3 1 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.1 It 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. 2 2 3 3 >p2p also already supports autocomplete for adding connections. … … 5 5 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. 6 6 7 A downside to using a (function) taxonomy is that 6430 terms need to be created for the users to choose from if we are planning to have related posts for all parsed post types. Upside is you only have to query taxonomy terms 7 A downside to using a (function) taxonomy is that 6430 terms need to be created for the users to choose from if we are planning to have related posts for all parsed post types. Upside is you only have to query taxonomy terms (function, title words, package, file name) 8 8 9 9 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-posts-to-posts 10 10 11 It creates fatal errors when parsing if both the library (used by the parser)and p2p plugin are both activated. So that has to be fixed before we can use the p2p plugin in the dashboard11 It creates fatal errors when parsing if both the parser and p2p plugin are both activated. So that has to be fixed before we can use the p2p plugin in the dashboard 12 12 13 13