String / text facets with apostrophe are encoded with "&#39"

Hi grendzy.

Thanks for the detailed steps on how to reproduce this issue and the excellent debugging. My one comment on this patch, though, is that I don't want to make assumptions in Facet API based on the backend. For example, if the core Search module doesn't return encoded HTML strings, than it should not run through a link function that decodes html elements to account for how Apache Solr stores it's values.

What I would recommend is creating a "map callback" for your facet to act on the values accordingly. For example, modify your snippet using the code below:

function mymodule_apachesolr_field_mappings_alter(&$mappings) {
  // Single string fields
  $ss_mapping = $mappings['list_text'];
  $ss_mapping['map callback'] = 'mymodule_map_series';
  $mappings['per-field']['field_series'] = $ss_mapping;
  $mappings['per-field']['field_series']['multiple'] = FALSE;
}

function mymodule_facetapi_facet_info() {
  $facets['ss_field_series'] = array(
    'name' => 'ss_field_series',
    'label' => 'Series',
    'description' => 'Series',
  );
  return $facets;
}

function mymodule_map_series(array $values, array $options) {
  $map = array();
  foreach ($values as $value) {
    $map[$value] = html_entity_decode($value, ENT_QUOTES, 'UTF-8');
  }
  return $map;
}

This will have the benefit of decoding the HTML entities only for the effected facet.

Thanks,
Chris

grendzy,

Sounds good. I will leave it open.

Regarding hook_facetapi_facet_info(), Apache Solr Search Integration does have a higher level hook which defines all Solr fields, and then implements hook_facetapi_facet_info() automatically. Check out the hook_apachesolr_field_mappings() implementations for examples of how this is done. Some of the keys are simply passed along to Facet API, for example the "query type" and "map callback" keys just to name a couple. This way you can define a field that is available to Apache Solr Search Integration and expose it as a facet all in one shot.

Hope this helps,
Chris

I don't think this should be in the main module but in a custom module of your own? I am going to close this one but it is very useful for future references as I can imagine more people will have similar questions.

I'd surely consider an API only patch. Feel free to provide one, with a link to this issue.

Closing this as fixed since the solution is here but no documentation patch was written. At least people can find it here :)

add missing cron step