Custom fields column display in admin gui too basic. Fix included.

[GoogleCodeExporter]

Well, like it says in the title. The version of CCTM I have displays images and 
relations as just the urls to the front-end view. e.g. the image src and the 
relation url.

I wanted to have the image display as a thumbnail, and the relation as at least 
a link rather than just a url.

The attached file is an updated version of the CCTM_Columns file which does the 
above. I'm sure the code could be improved on to be more cctm-specific, but 
it's a start :)

Cheers
Alastair

Original issue reported on code.google.com by a...@perchten.co.uk on 7 Jan 2013 at 7:38

[GoogleCodeExporter]

Did you attach the file?

The custom column will display whatever you have set as the default output 
filter for a field.  So if you have "to_image_src" as the output filter, that's 
what will get shown.   I've had nothing but trouble with WP's image generation 
scripts (namely the thumbnail stuff) -- very inconsistent behavior across 
envrionments.  But I can take a look at your code.

Original comment by ever...@fireproofsocks.com on 7 Jan 2013 at 7:42

• Changed state: InReview

[GoogleCodeExporter]

Hmm, I think the file got lost when I switched it from a bug to a feature 
request. Sorry. Should be attached now.

Original comment by a...@perchten.co.uk on 7 Jan 2013 at 7:47

Attachments:

• CCTM_Columns.php

[GoogleCodeExporter]

I guess part of this is that the front-end default is different from the 
back-end default. For example, in the front end I always want stuff to display 
just as the raw ids because I'll handle the templating mysefl. In the backend, 
I'd rather have stuff displayed sensibly for my clients. 

Perhaps this feature should therefore really be "separate the default display 
option into two: frontend and backend".

Incidentally, it might also be nice to have a to_thumbnail_tag output filter 
which specified the image tag as a thumbnail. In the attached file above I had 
originally tried the :to_image_tag filter but went with a manual 
wp_get_attachment_image() call just to get the sizing I wanted.... or perhaps I 
missed that in the options somewhere. 

Original comment by a...@perchten.co.uk on 7 Jan 2013 at 7:50

[GoogleCodeExporter]

Frontend and backend displays are already separate.  I can however, add some 
tpls dedicated to the columns so you can customize the manager HTML a la 
http://code.google.com/p/wordpress-custom-content-type-manager/wiki/CustomizingM
anagerHTML

Setting options in the output filters isn't currently possible in the GUI -- 
the filter operates sans arguments.  You can pass sizing arguments to the 
to_image_tag filter already, but this must be done in your template file, so it 
wouldn't work for the custom columns without some code modifications. 

Original comment by ever...@fireproofsocks.com on 8 Jan 2013 at 12:49

[GoogleCodeExporter]

The submitted fix does removes taxonomy columns (e.g. categories).  I'm seeing 
if I can work those back in.

Original comment by ever...@fireproofsocks.com on 21 Mar 2013 at 12:15

• Changed state: InProgress

[GoogleCodeExporter]

Ah, I see what you did.  I copied only the populate_custom_column_data() for 
this and cleaned it up a little.  This will come out with 0.9.7.1

Committed revision 685001.

Original comment by ever...@fireproofsocks.com on 21 Mar 2013 at 12:44

• Changed state: Fixed

[GoogleCodeExporter]

One huge problem here is that WP will not execute the CCTM's callbacks for 
built-in WP columns.  So the workarounds get really wonky, e.g. hijacking a 
custom field so you can print the stuff you need in the list  view.

This seems to be a bit more flexible: 
http://shibashake.com/wordpress-theme/add-custom-post-type-columns

but I think I actually had that implemented before and it became untenable.

So the real trick is how to customize the built-in columns...

Original comment by ever...@fireproofsocks.com on 8 Apr 2013 at 8:36