fireproofsocks

Sounds like a bug report should be filed. There are multiple ways to upload assets, so it’s important to list the exact steps you took.

Sorry, that’s not really a CCTM question, it’s a WordPress one, and yes, as I stated previously the WP functions are often confusing, poorly thought-out, inconsistent, and difficult to use. Any single post (of any type) can have many taxonomies, so it’s never as simple as just printing a single value (as is done with the print_custom_field() example): you are always retrieving a list of results, so you have to loop over them somehow.

The example on http://codex.ww.wp.xz.cn/Function_Reference/wp_get_post_categories is relevant to you. Here it is a bit more verbosely modified:

$post_categories = wp_get_post_categories( $post_id );
foreach($post_categories as $c){
    print '<li><a href="'.get_term_link($c->slug, $c->name).'">'.$c->name.'</a></li>';
}

It’s in the bug-tracker — I just need a paying gig so this can get on my radar.

Might be possible… WordPress’ implementation of its rich-text editor is problematic however, so it’s not easily manipulated. I generally do not recommend mixing and matching plugins like this: sometimes plugins cause as many problems as they solve. I would recommend you create a separate post-type for your needs and utilize that if needed — it’s always inefficient to “ignore” the built-in fields, and in the case of the post-title, it’s also problematic (WP is hard-coded to look for that value in certain random spots).

Sounds like this one:
https://code.google.com/p/wordpress-custom-content-type-manager/issues/detail?id=532

Sure. The fields are listed in a few spots in the (slightly disorganized) docs, e.g. under “Available Placeholders” https://code.google.com/p/wordpress-custom-content-type-manager/wiki/summarize_posts_shortcode

Sorry I’m late seeing this — I”m not sure what you’re trying to do… did you create a custom post-type named “FILE”? What browse button are you referring to? There is a bug in the plugin related to searches in the metabox that may be what you’re experiencing.

It’s not possible to hide it on the built-in content types. But you can disable fields on custom post types by de-selecting the post content checkboxes in the fields tab.