Jamie O

I have released an updated version (1.2) to co-incide with the release of WP 2.8. The comments at the top of a category template file are no longer manditory. Full release notes are available here – https://idealienstudios.com/projects/ice/v12release/

Check out https://www.jackmcintyre.net/2009/05/07/when-wp_list_pages-cant-do-it/

@partireper.it:

What is the filename for that template file?
What do you have in the category template prefix field?
Is ‘Enhanced Categories?’ set to Enhanced (On) in the options window?

@musnake – “Where do I assign the template to that post?” You create a category template and then assign that to the category. With that done you can create a post file with the same naming (category-portfolio.php begat single-portfolio.php) and that post template will get picked up at render time of the page. Currently you cannot select a post template from within the admin console, though that is something I want to add to the next release.

@Partireper.it – Make sure the filename you save your files as match to that category Template Prefix so category-blog.php by default. There is an issue currently if you are using a child theme. One workaround is to put the template files in the parent theme folder, but that is obviously not an elegant solution. Working on a better one.

Building on what codeispoetry said, have a way that the community can vote on the outstanding ideas to indicate what they want prioritized. From a release management point of view, those ideas that are ranked at the top could be assessed from a standard set of criteria to help explain why certain features are / are not happening: complexity, scope, resources (time, money, people, technology, etc), dependencies, etc. I’m sure a portion of this happens internal to trac, but it could be useful information to understand the interests of the different user groups of WOrdpress: developers, wp users, automattic, etc.

The more active use of the dev blog that Jane has been using is a great thing in this capacity.

Any improvement in this with version 1.2.10 of the plugin? Revisions are a necessity when building sites that need to “save clients from themselves”.

For any developers looking into this – I think this Trac ticket might be related: https://core.trac.www.ads-software.com/ticket/9089

Based on my last post and experimenting with the arguments passed from the function (cat_rows) which is called in generating the table of categories, I have a “working solution” for those who are affected by this problem.

NOTE: This is very much a short-term solution for those noticeably affected by this problem – use at your own risk!

• Find and comment out the following code on line 43 of /wp-admin/includes/template.php
  $args = array('hide_empty' => 0);
• Replace it with the following code:
  $args = array('orderby' => 'ID', 'order' => 'ASC','hide_empty' => 0, 'child_of' => 0, 'depth' => 0);

I would hope someone more intimitely familiar with the backend code of WordPress will follow-up on this. There are quite probably more better ways to resolve this based on what the functions associated are doing throughout the site. But I’d like to think that I’ve helped the conversation enough that a resolution could be put in place for the next release.

This problem is affecting me as well, beginning to search for where the problem is. This is just my efforts to probe inside core WordPress and perhaps the info may help. All references are based on WP 2.7.1 version code:

• /wp-admin/categories.php at line 209 calls:

  <?php
  cat_rows(0, 0, 0, $pagenum, $catsperpage);
  ?>

• /wp-admin/includes/template.php at line 23 creates the internalized version of this function:

  function cat_rows( $parent = 0, $level = 0, $categories = 0, $page = 1, $per_page = 20 ) {
  	$count = 0;
  	_cat_rows($categories, $count, $parent, $level, $page, $per_page);
  }

• The internalized function just below in template.php calls get_categories on line 46:
  $categories = get_categories( $args );
• get_categories function is in /wp-includes/category.php starting on line 39 and is reasonably documented at get_categories Codex page.

At this point I did some variable output tests to see the arguments being passed to different instances of get_categories:

Output from the category parent drop-down list (which seems to show entire tree structure and nested levels properly):
Array ( [type] => category [show_option_all] => [show_option_none] => None [orderby] => name [order] => ASC [show_last_update] => 0 [show_count] => 0 [hide_empty] => 0 [child_of] => 0 [exclude] => [echo] => 1 [selected] => 0 [hierarchical] => 1 [name] => category_parent [class] => postform [depth] => 0 [tab_index] => 0 [include_last_update_time] => 0 )

Output from the category list which is where we are having our problems:
Array ( [type] => category [hide_empty] => 0 )

The difference being that the drop-down calls get_categories by way of wp_dropdown_categories instead of cat_rows. Here’s the relevant portion of wp_dropdown_categories from /wp-includes/category-template.php/ starting on line 370:

function wp_dropdown_categories( $args = '' ) {
	$defaults = array(
		'show_option_all' => '', 'show_option_none' => '',
		'orderby' => 'ID', 'order' => 'ASC',
		'show_last_update' => 0, 'show_count' => 0,
		'hide_empty' => 1, 'child_of' => 0,
		'exclude' => '', 'echo' => 1,
		'selected' => 0, 'hierarchical' => 0,
		'name' => 'cat', 'class' => 'postform',
		'depth' => 0, 'tab_index' => 0
	);

	$r = wp_parse_args( $args, $defaults );
	$categories = get_categories( $r );

More to come…..

Sorry you had such troubles musnake – it was my first real forray into WordPress plugins and the actions / hooks / logic. I’ve just released a new version with support for WP 2.7 (still back supporting to WP 2.5).

I just found this comment after releasing it – so I’ll take a look at a better way to do the drop-down. If the theme doesn’t have a commented name use the filename minus the category identifier.

If anybody has any other suggestions of related functionality they’d like to see for this, I would love to hear it.

It appears – atleast in my case – to be specific to Firefox. Disabling all of my FF plugins didn’t fix it. Version 3.0.3 of firefox.

I am encountering the same issue – flash uploader sends the window to a view of my landing page. Using the html version works for now, but a very strange issue that I would love to know the solution for it!