- Issue created by @broeker
We started out on version 8.x-1.x and we were successfully indexing our in Search API to provide heavily weighted search requests.
But it seems that somewhere with the the 2.0.x/2.1.x releases this functionality is no longer working.
Our field remains in the index, but nothing is actually is indexed in the database and no search results are returned for specific keywords. When you try to "add" new field to your index it shows this message at the bottom:
Skipped fields
The following fields cannot be indexed since there is no type mapping for them:
Layout (type "layout_section")
Metatags (type "metatag") <-------------------****
Metatags (Hidden field for JSON support) (type "field_item:metatag_computed")
If you think one of these fields should be available for indexing, report this in the module's issue queue. (Make sure to first search for an existing issue for this field.) Note that entity-valued fields generally can be indexed by either indexing their parent reference field, or their child entity ID field.
If I downgrade to the old 8.x-1.26 release, the index starts working correctly again.
Is this a known issue since 2.0, or are others still successfully indexing metatag fields? The docs still indicate this should work, and most of the issues I've found surrounding this are quite old and/or closed.
p.s. I added a related issue from the Search API queue but I suspect this belongs over here?
Active
2.1
Integration with other module