Forum Replies Created
-
Posts
-
Hi!
Could you be more specific about which one? There are a plenty of examples there. I can then try to fetch the code from it.
I cannot promise it will look exactly like that, as your page layout depends 99% on your theme.
Hi!
You have posted this topic once, and I replied already here with the solution: https://wp-dreams.com/forums/topic/ajaz-search-not-showing-results-on-iphone/
Please check on your last topic.
Hi!
Just took a look at the problem. Luckily it’s just a styling coming from the theme which overrides the upper margin on content elements below screen sizes of 1000px to -100 pixels, so the content is not visible, instead you can see the white background.
The easiest way to fix it is to override that rule, so the content in the search results do not apply to it. Open up the search settings and go to the “Theme Options -> Custom CSS” panel, there is a field where you can put custom CSS code in. Paste this code there:
[html]
.resdrg .content {
margin-top: 0px !important;
}
[/html]After saving the search instance, it should be fixed immediately.
Hi!
Sorry, I forgot to update you on this. I’m implementing this feature to the next version, which comes out very soon (4-5 days with approval). It will have some other cool new features as well. Thank you for the patience!
Hi!
Could you please check if the settings are saved correctly? This sounds like either a database issue or an unknown incompatibility(?) perhaps.
The line where you get the error merges the default options with the options from the database. So it basically means that the options from the database are incorrect or does not exist.
Could you please check on the database if the tables wp_ajaxsearchpro table exists? If so, then please send me a screenshot of how the data in that table look like.
Could you also send the exact php version you are running? I remember a similar issue from some time ago and it was related to a php module some sort.
Also, if you know how to use the your browsers developer tools, it would be nice to check if the ajax request is not interrupted by anything, and how the header looks like.
I can only hope we can resolve this by guessing. Once you got any temporary online version of it, I’m more than happy to take a look at it.
Hi!
This is a problem on your side. It means that the CSS directory is not writable. You can change the permissions on it, or enable force inline styles.
Please read the related knowledgebase article on how to do that: https://wp-dreams.com/knowledge-base/the-layout-and-theme-is-not-changing-after-saving/
Don’t forget to save the search settings again after changing the folder permissions.
Hi!
I checked on the plugin, but I needed to do a quick debugging as well and it turned out that some values on the options page were not consistent with the database. In this case the best and safest option is to start over, so I deleted the search you have configured – sorry about that – and created a new one. You probably will re-configure the search, I hope it won’t happen again. If so, then it’s definitely an unknown bug.
You can actually change the grouping header on the advanced options page. Under the “Group results by” option there is an input field where you will see the following text: “Posts from: %GROUP%”. Change it to whatever you want, and it should show on the frontend. Currently the isotopic layout is used so I turned it off as it only applies to vertical results.
I have also applied a few custom css rules, which you can see under the “Theme options->Custom CSS” panel, because some rules were conflicting from the theme. You should make a copy of that text in case you create a new search.
Hi Ken!
As for the first question, taxonomies can’t be returned as results, only terms.
As for the second, I’m guessing you are having images from a different domain or url. There is a quick solution to this, here you can find it in the knowledgebase: https://wp-dreams.com/knowledge-base/some-images-are-broken-what-to-do/
Thank you for the very clear explanation and proper ticket!
Hi!
If you mean custom post types, then yes it can. You can find more about it in the documentation here.
If you are referring to taxonomy terms, then it’s also possible. It’s not yet documented, but you can easily do it on the General Options -> Sources 2 tab.
Hi!
This time I needed to change one file in the search plugin directory. I don’t know what caused this exactly, but it’s fixed. You should see the search bar now as before.
Hi!
There is a guide in the knowledge base for safe upgrading, as well as in the documentation:
https://wp-dreams.com/knowledge-base/updating-from-older-versions/
http://wp-dreams.com/demo/wp-ajax-search-pro3/docs/#important_upgrade_notes
I believe you missed one step. The cache options have changed in the new version, so there is a possibility of database inconsistency. Since you give me access I did solve this for you, by simply saving the cache options without change. It should be working now correctly.
No problem at all.
This makes it a bit more difficult, as the tags search is a bit simplified, because it can make the search really really slow if someone has got a bigger database. So in this case changing the keyword logic won’t help you, simply because it’s not implemented to the tags search.
I made however a quick modification to the search code, but I cannot guarantee a proper speed, but in your case it might just work fine.
Do the following:
0. Make a backup copy of the wp-content/plugins/ajax-search-pro/ directory, just in case.
1. Open up the wp-content/plugins/ajax-search-pro/includes/search_content.class.php file and replace it’s contents with this: http://pastebin.com/raw.php?i=SRD34HnM
2. turn OFF the “Show exact matches only?” option on the General Options->Sources panel (at the bottom), this is very important
3. Change the keyword logic to “AND” or “AND with exact word matches” (if you want more strict results) on the General Options->Behavior tabNow the keyword logic will respect the terms search (in your case woocommerce tags) as well.
