Article 1
We talked about this in IRC. The idea is to make it easy for custom taxonomies to generate columns on CPT WP_List_Table screens, just like the Categories and Tags columns on wp-admin/edit.php Here's...
View ArticleArticle 3
Here's my proposal: register_taxonomy( 'presentation', 'presentation_type', array( ... 'show_admin_column' => true ) ); This would create a 'Presentations' column in WP Admin -> Presentations....
View ArticleArticle 4
Well, if you have the same taxonomy registered for multiple post types, you can't control on which screens it shows up. Maybe besides 'show_admin_column' => true we could also have...
View ArticleArticle 5
I think I may be partial to adding the flag to the register_post_type parameters instead of register_taxonomy. Normal workflow is to add custom taxonomies TO a custom post type rather than the other...
View ArticleArticle 6
My thinking was that you need to register the post type before the taxonomy, but that isn't really a problem, since the column rendering is done much later.
View Articlecc changed
cctravis@… added +1 to adding it to CPTs. To me it's more logical workflow and since the screen is a CPT screen. However, it would be even better if it didn't matter. Replying to jtsternberg: I think I...
View ArticleArticle 8
You bring up a good point. If we store it on the CPT, then it won't work if you a have a user taxonomy.
View ArticleArticle 9
So should it have a separate complementary function for flexibility? something like register_taxonomy_columns( $taxonomies, $object_types, $args );
View ArticleArticle 10
21240.diff looks like a step in the right direction. Any particular reason for making get_taxonomy_column_headers() a stand-alone function? What is the purpose of the 'taxonomy_column_header' filter?
View ArticleArticle 12
Replying to scribu: 21240.diff looks like a step in the right direction. Any particular reason for making get_taxonomy_column_headers() a stand-alone function? What is the purpose of the...
View Articlekeywords changed
keywordshas-patch added vs rolling it into the get_column_headers() function? No, vs making it a protected method. __( 'No '. $taxonomy_object->label ) You can only pass plain strings to __(). But...
View ArticleArticle 14
Replying to scribu: vs rolling it into the get_column_headers() function? No, vs making it a protected method. Do you envision this being incorporated into class WP_List_Table then? We'll probably...
View ArticleArticle 15
Do you envision this being incorporated into class WP_List_Table then? Into WP_Post_List_Table for now, but keeping it as a function works too.
View ArticleArticle 18
In 21240.4.dff I added $this->taxonomy_columns = apply_filters( 'show_taxonomy_columns', $taxonomies, $post_type ); This line allows plugins and themes to filter the taxonomy columns. i.e....
View ArticleArticle 21
21240.5.diff is another take. As far as I can see, there's no need for no_items label to be based on menu_name (this wouldn't be localizable). It can fall back to "No Tags" / "No Categories", like the...
View ArticleArticle 22
In 21240.5.diff, aren't these lines redundant: 46 'labels' => array( 47 'no_items' => __( 'Uncategorized' ), 48 ), ?
View ArticleArticle 23
Also, I'm not sure these two lines have the intended effect: $taxonomies = array_diff( $taxonomies, array( 'category', 'post_tag' ) ); $this->taxonomy_columns = array_merge( array( 'categories',...
View ArticleArticle 24
My suggestion would be to transform the taxonomy names into the desired column names later, right before rendering.
View ArticleArticle 26
Replying to scribu: In 21240.5.diff, aren't these lines redundant: Currently the category column says "Uncategorized" if there's no categories:...
View Article