Facet Mapping Overhaul: Type Auto-Detection, Every WordPress Source Mappable, Multi-Valued and Image Fixes

Four changes to Facet Mapping on Drupal and WordPress: the Solr type is now detected for you, every indexable WordPress source is selectable, multi-valued fields come out the same whether they were crawled or ingested, and image fields resolve to real URLs instead of attachment IDs.

01 The Solr type is detected for you

Pick a Drupal or WordPress field and the Solr Type dropdown auto-fills with the detected suffix. Every entry in the field dropdown also shows its detected type inline — post_tag — multi, string; _price — single, float — so you know before you click.

02 Every WordPress source is mappable

The field list is no longer a filtered subset. It now covers:

• Core post columns. post_title, post_content, post_excerpt, post_date, post_author and the rest.
• All postmeta keys. Including the underscore-prefixed WooCommerce core fields — _price, _sku, _stock, _thumbnail_id — which were previously hidden as private.
• Every public taxonomy, plus all WooCommerce pa_* attribute taxonomies.
• Synthetic aggregates. featured_image_url and gallery_image_urls.

03 Multi-valued fields come out identical either way

Drupal taxonomy terms, ACF Checkbox, Select-multiple, Relationship and Gallery arrays, and WooCommerce attributes are all stored differently — some as multiple rows, some as a serialized array. They now all emit as one <meta property="opensolr:X_sm"> tag per value.

The Web Crawler aggregates those repeated tags into a Solr array, matching what real-time ingestion already writes. Crawler and ingestion now produce identical documents.

04 Image and file fields emit real URLs

Image and File field mappings now emit a real URL instead of the bare attachment ID. Mapping a Drupal field_image, or a WordPress meta that stores an attachment ID — an ACF image field with Return Format set to ID, _thumbnail_id, a custom image_attachment_id — resolves to a working public URL.