Forum Replies Created
-
Posts
-
Hi,
Thank you very much for the details it helps a lot!
It seems like there was comething conflicting so I have anbled the soft-check for the query compatibility, and that seems to have resolved the issue.
Hi,
Thanks for all the details, it helps a lot!
The filter is there, but it’s empty at the moment. Just to test I have made sure to enable the visibility here as well as added categories to it, now it should be there.
Yes, definitely. We eventually want to move it to a separate menu with a possibility to select which result types the synonyms should apply to.
Well on the results page I see the divi module attached, but on the home page it’s not present, so the loader has no reason to show up.
The loader icon displays whenever it is loading the results – either in it’s own container or within the attached divi module.
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.
Hi!
From the looks of it the trigger for typing was disabled for the non-elemntor type results, you can re-enable it here: https://i.imgur.com/AVFUvEL.png
That will do the trick 🙂
Indeed, this might be a yet unknown bug, I have noted it for more investigation.
Until then, I have enabled a requirement on the filter, so no search can be initiated unless a checkbox is checked in the post types: https://i.imgur.com/gxRzNOg.png
That will prevent the issue from happening.
