- This topic has 4 replies, 2 voices, and was last updated 9 months, 2 weeks ago by
.
-
Posts
-
I have a ‘product’ post type that is indexed via regular engine (not index table) and it indexes primarily on the basis of a tag taxonomy that is called “models”. Each product post has various model numbers as tags, so that when someone searches a model, it pulls up the correct product post. This works wonderfully and has been working great for quite some time now, however my boss noticed today that on one page, which has a model tag for “1200”, this product is not returned in results. There are other tags for that page, such as 1203, and 1204, and those return results from the search, but for some reason 1200 typed into the search bar doesn’t return the proper product (https://www.newageindustrial.com/product/mobile-dunnage-racks/). In fact, it returns some other product and also some pages that I’ve included.
Any ideas why it would fail with just this one tag? Maybe others are failing too, but we have a thousand at least and this is the only one we’ve noticed where the tag is definitely present on the post but won’t appear in results.
Okay I need to update this. I realized something:
It appears that the correct product is displayed, but it is displayed at the very bottom in a second “Results from Products” section. So I guess my new question is: why is this result not the highest in the order? And why exactly are all these other results being triggered? You’ll notice if you type various other numbers, very few “pages” appear in the results, but for this numeric string (1200) every included page appears in the list. Seems something is not right. Usually if the search string corresponds to a “models” tag on a product page, then that product appears highest priority. Screenshot attached.
Okay, my apologies. I have one more update:
I toggled OFF the “Search in content” toggle and that fixed it. Now the correct post appears in the correct spot. But I’m still confused as to why “1200” brought up ALL the included pages when content toggle was on, especially when I couldn’t find that string on some of those pages. If you have any input on that, let me know. For now, I’ll just keep that “search in content” toggle off, although I liked the idea of having that on at some point so descriptive text on product pages can be taken into account.
Hi,
The post content field nowdays is very complex, it stores all the raw data, including all sorts of shortcodes, blocks and HTML – which is stored as plaintext. Sometimes those include classnames, IDs etc.. where numbers are very common. My guess is, that a stored HTML tag has a class name involving “1200” either fully or partially. But since it’s a text there is no way to differenciate, so it’s matched.
The index table engine resolves that to some degree by rendering the content first then reading everything “visually” and storing that. If however the issue is resolved, then I would recommend keeping the setting as-is.
- The topic ‘All Tags Seem to Work Except One – 1200’ is closed to new replies.