Forum Replies Created
-
Posts
-
Great! I will make sure to have this included in the upcoming version 🙂 Thanks for the feedback!
If you don’t mind, I will close this topic soon and mark it as resolved, feel free to open another one if you have other questions or issues.
If you like the plugin and have not rated already, feel free to leave a rating on your codecanyon downloads page and on the wordpress plugin repository, it’s greatly appreciated.
Good news! I have very likely found the culprit. Because of a previous Yoast SEO plugin vulerability, Cloudflare has a trigger for a post variable “orderby”. This was detected falsely and triggered the block on our ends.
I’m attaching the patched version to this post, please install and activate it. After that the issue should go away.
I tried the file manager, but it is not working correctly, it’s not loading all the files, reverts back to the base directory and takes over 3 minutes to open a file – I guess the firewall does not like that either. If it’s possible to adjust the firewall, I strongly suggest that.
Either way, I will try to replicate this on one of our test servers with the highest firewall settings to see if I can get the same errror and go from there. This is unfortunately not a simple plug fix, first I need to be able to tell what exactly triggers it.
I will get back to you soon.
Hi,
Sure!
The block is reported by Cloudflare firewall – it is a false positive match. Unfortuantely there are no other details available. It happens because cloudflare heuristics picks up a “suspicious” payload when submitting the form. Cloudflare firewall is very complex and has hundreds of thousands of active rules, I have had similar issue with other plugins too, so it’s not uncommon. Most of the time a word or a string triggers it within the settings.
Can you please add temporary FTP access so I can make changes to the search plugin files? I will try to debug ste-by-step the submitted payload to see which value cloudflare doesn’t like. It’s a painful process, but at least I will know what to look for if this issue may repeat for someone else.
You are very welcome 🙂
Usually imported attributes are added as custom field value and not as taxonomy terms. I don’t exactly know how it works, but that’s my experience. There is probably a way to import them as taxonomy terms, but I’m afraid I don’t know how.
Either way if you don’t mind, I will close this topic soon and mark it as resolved, feel free to open another one if you have other questions or issues.
If you like the plugin and have not rated already, feel free to leave a rating on your codecanyon downloads page and on the wordpress plugin repository, it’s greatly appreciated.
It’s because these attributes are not stored as taxonomy terms, but as custom field metadata. If you check for example the product CAS page attribute page, it reports that there are no attributes yet.
Luckily these are still indexable, I have added the product_attributes custom field to the index and re-indexed. The number of keywords doubled, so all of them should be indexed now.
Thank you!
I found the issue, it was actually the search theme feature. The polaroid layout by default has an option to exclude resutls that have no images.
I switched to a different theme and now it’s all okay. Basically any theme that does not have “polaroid” in it should be all right 🙂
Hi!
Thank you very much for all the details, it helps greatly.
It’s most likely a configuration related issue, these usually happen when multiple browser tabs may have been opened with the configuration, and saving one tab and then changing on the other will revert back to the previous, earlier state. It could be a yet unknown bug as well, let’s try to figure it out.
I will try to guess the most likely configuration issues in relation to this:
– Double check if the index table is selected, just to be sure
– Make sure the exact matching is turned off – this will automatically turn off the indexed search
– Make sure there is no exact matches filter used, even if it’s not visible, it still has an effectThese are the most likely causes. In case these doesn’t help, can you please add temporary back-end details? I will have a quick look at all of the configuration and do a few test searches.
No problem at all, you are welcome! It’s easy to overlook a minor detail 🙂
If you don’t mind, I will close this topic soon and mark it as resolved, feel free to open another one if you have other questions or issues.
If you like the plugin and have not rated already, feel free to leave a rating on your codecanyon downloads page and on the wordpress plugin repository, it’s greatly appreciated.
Hi,
Thank you very much for the details!
I logged in to check, I think the issue was the wrong field selected. On the max SqFt field I saw the “acreage” custom field: https://i.imgur.com/m3PiVCV.png
I have corrected that, did a few test searches, it looks okay to me now, can you please confirm?
