Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Atributes with variable characters
This topic contains 13 replies, has 2 voices, and was last updated by Ernest Marcinko 5 years, 8 months ago.
- AuthorPosts
- September 19, 2017 at 1:12 pm #14787
Hi Ernest,
we want to add attributes to products with variable characters, but they do not appear in the search. Example: 12345 and 12345 (). Where () can be a number from 0 to 9 or letters from A to Z. Is it possible? Or some other solution?September 20, 2017 at 10:18 am #14799Hi,
Can you please be more specific about ‘they do not appear in the search’? Does that mean the plugin is not searching for them, or are they not displayed somewhere?
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
September 25, 2017 at 11:01 am #14865Hi Ernest,
I send you an image of how it works now. Everything is correct. If I look for rbj102440 look for correct product. What I need is that if we put a value between the parentheses, when the user searches without the parenthesis find it. Example: Attribute rbj102440 (123) the user searches for rbj102440123 and finds it.
Thanks
Attachments:
You must be logged in to view attached files.September 25, 2017 at 10:53 pm #14885Hi,
I understand what you need now. Currently this is not possible, but I think I can probably make an adjustment to the index table engine to make this work in the upcoming release.
Keep an eye on the next update, it should be out within 7 days. After that, all you need to do is just re-creating the index table, and it should register these types of strings with both parentheses and without them as well.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
October 9, 2017 at 11:18 am #15068Hi Ernest,
The new release is not yet available. True?
You already have the documentation to be able to configure table engine to get what we are looking for?Best regards,
Fernando
—October 9, 2017 at 11:38 am #15069Hi Fernando,
Unfortunately not yet, I had to revert back a few changes within the 4.11.5 release, there was an issue with the approval at my fault.
Best,
I’m pushing 4.11.6 out this week, which includes an index table code that should work as you expected. Sorry about the inconvenience.
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
October 30, 2017 at 1:19 pm #15339Good morning Ernest,
is this release the one we need?
If yes, where can I see the information I need to deploy index table and configure the searches?Fernando
—October 30, 2017 at 2:11 pm #15343Hi Fernando,
Yes, this one has the modification. Let’s hope it will work. You only need to create a new index table, by clicking on ‘Create new index’ button, everything else should work.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
December 12, 2017 at 12:32 pm #15856Hi Ernest,
It has not been clear to me how I should proceed to get the search configuration.
Can you help me please.December 22, 2017 at 10:43 am #16007Hi Ernest,
I need to finish the work of my Client.
I need your guidance to make the searches discussed above work. I have already created the index table. What is the next step?Fernando
—December 22, 2017 at 11:07 am #16009Hi Fernando,
There is no other step required. If the index table was re-created, it should hopefully work now.
Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
January 15, 2018 at 11:30 am #16302Good morning Ernest,
after setting the table index we found two problems. The first problem is that it does not identify the new attribute “Test” to include it in the list of “Source2”, as you can see in the image. Second problem, not find the product if I add (4), (45) or (456). What solution can we apply?I attach images, if you need something else do not hesitate to ask me.
Attachments:
You must be logged in to view attached files.January 15, 2018 at 11:31 am #16307January 15, 2018 at 3:49 pm #16314Hi,
If the attribute was added in the post editor screen via WooCommrece drectly, it may not be registered as a custom taxonomy term, but as a custom field. I’m not sure how WooCommerce determines which one to use, but sometimes it becomes a custom field.
Try looking for attribute_pa_test or attribute_pa_ or ‘attribute_’ within the indexed custom fields list under the index table options panel: https://i.imgur.com/MgMUVNX.png
Best,
If it shows up, select it, and then save the product again, so the new field is indexed.
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)
- AuthorPosts
You must be logged in to reply to this topic.