Currently the only way to overcome a machine-readable field's ugliness is to use PHP through computer fields, rewrite options, and theming.

There should be a way to pick a candidate 'display' field which will show instead, so people don't have to use PHP.

I don't know how well this will work out, but it's worth giving it a try.

Comments

danielb’s picture

danielb commented

Perhaps this should be done through views displays, and then they can pick whether to show the 'finder field' or the rendered display.

danielb’s picture

danielb commented
Version: 7.x-1.x-dev » 7.x-2.x-dev
dan_metille’s picture

dan_metille commented

This would be a good option. In the meanwhile, do you have a example about how to rewrite option for choices list in PHP?

danielb’s picture

danielb commented

I added a quick explanation of rewrite here #1561734: can't search strings in node bodies

danielb’s picture

danielb commented

Added documentation page http://drupal.org/node/1565024

bayousoft’s picture

bayousoft commented

I am having this issue with a select list finder. The option value (i.e. 2012 01) is displayed to the user instead of the desired display (January 2012). Could someone point me to an example to show the desired display instead? I am guessing it will involve the rewrite option.

Thanks!

bayousoft’s picture

bayousoft commented

Not glamorous but I coded something up.

danielb’s picture

danielb commented

You could also use a Computed Field as a workaround.

danielb’s picture

danielb commented
Status: Active » Fixed

There is now an option to use the rendered views display row instead of the field's value.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.