Forum Replies Created
-
Posts
-
Hi!
This definitely looks like a javascript issue, since it’s working until you interact with the select box. An event handler is most likely connected in an incorrect way and it interacts with the search plugin as well. This can come from 2 places: 3rd party plugins or the theme
Since you tried to disable all the plugins, then the only thing left is the theme. There must be a file which is loaded by the theme. Try to switch the theme temporary, and the problem should go away immediately.
Let me know how it goes.
Hi!
It was a yet unknown bug, thank you for reporting it. I’ve fixed it with the provided ftp details. I’m adding it to the new update as well.
Hi!
I’m suspecting a settings-database inconsistency based on the error message returned in the ajax request.
Try to open the plugins “Cache options” submenu and hit the “Save Options” button without changing anything. It might solve the problem.
Hi!
3. I understand your point, but for these complex usages are the cases when the filters come in handy. As you can see the backend is already filled with various options and adding something even more complex like a content output builder just doesn’t make sense to me right now.
There is always something more that the user wants, that’s why the backend is overwhelmed with loads of options. At some point I had to say no, because these cases are too special to generalize into the stock version of the product, and 99% of the users won’t even notice it or used it.So in my opinion you should create a custom function which hooks onto one of the filters and modify the content as you want it to look like. Here is a knowledgebase article on how to do such things: https://wp-dreams.com/knowledge-base/showing-the-post-type-name-in-post-title/
Starting with this simple piece of code you can build up the fields you wanted. It gives you access to the final output array of objects with post ids, final content etc.. So you can easily retrieve the custom fields you need and change the content field to whatever you want.
1. Will test that out on my local server and make corrections 😉
2. It’s excluded on purpose. I switched up a few lines and now it should filter them out even if it’s a custom field content.
Hi!
That sounds like the ajax request is not returning anything, which happens if the code stumbles into an fatal error at some point and halts.
If you click on the network tab of your browsers developer tools and check the content of the ajax request after trying a search it should be empty.
Now, try to enable error reporting in the wp-config.php file and try searching again and then examine the new ajax response. It should contain some kind of fatal error message for sure.
WAMP server might have some core modules disabled. I switched to XAMPP a few years back, that’s my current testing environment and it corresponds with 99% of the hosting servers. If you don’t mind, I would recommend trying it 😉
Thanks for the ideas!
I’ll see what I can do about that. If it’s not too complicated, I might slip it into the next bugfixed version today.
Well it would be awesome, but I don’t know what else I could add to that field, or how to change it. I mean the “%GROUP%” variable represents the custom post type name or category name, so anyone can change it to for example “Results from %GROUP%”. Should I create a separate box for the “page” as well? If you have an idea, I’m happy to hear it.
I see now.
4. I’ve marked the code with comments that you can edit for this. Open up the wp-content/ajax-search-pro/includes/search_content.class.php file and go to line 819. That’s the variable you need. I made a few lines of comments to help you out.
Well, I’m trying 😉
Hi!
After a long debugging I have found the problems
1. You had a custom field filter created on the Frontend Options panel, but never used it. This restricts the results to show only those where this particular custom field is present. I removed that, since it wasn’t in use. Then in the Advanced option field there was a category excluded. The problem with that is that on a multisite install every single site has different category ID’s, moreover every custom taxonomy term is stored where the categories are, so if a term has the same ID on a different site as another category on the other site it will exclude the posts/custom post types related to that category or term. I don’t know if there is ever going to be a possible fix for this, it’s a very complicated issue. So I don’t recommend excluding categories or taxonomies on multisite installs for now.
3. On the advanced option panel you can find “Description Field” option, where you can select which custom field would you like to show instead of the description. Or there is another field called “Advanced Description Field” just below that, where you can merge multiple custom fields as well, or keep the original description along with a custom field content, like: “{descriptionfield} {custom_field_name}”
4. There is an option on the Advanced Options panel: “Group by default text (%GROUP% is changed into the current cateogry/post type name)” – it’s almost at the bottom. So in your case the %GROUP% will be the custom post type name, and you can add text before it, after it, or just remove it if you want.
Hi!
2. It was indeed a bug with multisite, I didn’t know that. Fixed it for you with minor modifications, this one goes as well into the next bugfix I’m uploading tomorrow.
As for the other issues, I need to leave right now but I will check them all tomorrow. Could you please provide temporary ftp access as well? I don’t want to edit the files via the plugin editor again, because if I make a syntax mistake then it will break the site and I would not be able to fix it. You can upload a txt file with the details, it’s not visible to others.
I will go through the issues tomorrow morning.
I see. I tried the default search engine, same results: http://www.rtoinsider.com/?s=million
What happens if you disable temporary the ajax search pro plugin and visit the url above? I think it might be unrelated to the search, but I’m not sure yet.
If the url above returns results with the same issue, then it’s not the ajax search pro.
Yes, I changed via the plugin editor, so you don’t have to wait till the next bugfixed version is up.
I think I have unchecked the ‘Notify users about the upgrade’ earlier when I uploaded a bugfix which affected only 1 user and it might have stayed that way. I will double check that when I upload the next bugfix.
No problem at all, have a nice day!
Oh, I think I see the problem now.
I indeed somehow messed up and forgot to incorporate the change to the current version, damn. I also found the issue why it showed up wrong results. It used the blog ID ‘1’ instead of the current blog id. I changed those faulty codes in the plugin editor, now you should see the correct results.
I’m going to make some tests now and correct these errors and upload them to codecanyon ASAP.
Sorry for the inconvenience. I hope you get notified this time.
