Forum Replies Created
-
AuthorPosts
-
Ernest Marcinko
KeymasterNot just this plugin, but no search plugins will work if there is no post content available.
Visual Composer works because it stores the built data in the post content (within shortcodes) and not somewhere else. I believe most “content builder” plugins do the same – because it would break the default wordpress search as well.
The search is even a Visual Composer addon itself: http://vc.wpbakery.com/addons/ajax-search-pro/Ernest Marcinko
KeymasterHi!
Looks like an HTML tag remains unclosed in the product description (since it’s shortened).
If you open up the Advanced Options panel on the search plugin options page, there is an option called HTML tags exclude from stripping content.
Delete everything from it and it will hopefully solve the problem: http://i.imgur.com/lOxLy2Q.png
Ernest Marcinko
KeymasterHi!
I see now what you mean. That’s why I was asking in the comments section on codecanyon if you use any shortcodes or something else to display that content. As I opened up the page editor I noticed that the pages are built with some kind of page builder “Content Composer” I guess.
The problem is that “Content Composer” plugin does NOT store the text in the post database in the description field, but somewhere else. If you switch to the classic editor, you see that the actual post content is empty: http://i.imgur.com/08dyuY0.png
So there is nothing to search for in the database, since the post content is not stored there.Ernest Marcinko
KeymasterHi!
It should definitely work. I’ve tried the latest version on my local test environment and it gives results, so it might be a conflict with I guess.
Could you please provide temporary ftp and back-end details to check on the configuration and do some debugging on the queries generated?
Ernest Marcinko
KeymasterHi!
I’ve tried to log-in to the back-end but the details are not working, could you please check them?
Also, could you link me to a page where the plugin is enabled?
Ernest Marcinko
KeymasterI see, but I don’t know why. I have this exact change on my test environment and it “unfortunately” works.
Can you provide temporary back-end and ftp access to a test server where this issue occurs? I suspect that either a 3rd party CSS or javascript is conflicting, but I’m not sure.
Ernest Marcinko
KeymasterHi!
So I’ve checked the back-end.
I’ve opened the “Website Search” and tested, it works for me. I’ve typed in “home”, “cart” and the results were there. The title is there, but it’s not visible because you set the title font to white and the default background image is white as well: http://i.imgur.com/yoy4d7k.png
If you set the “Result Content Background” to some other color on the Theme Options -> Isotopic results tab to something else than white, then it may also help: http://i.imgur.com/MYdthEB.png
Ernest Marcinko
KeymasterHi!
I’m guessing you are using some kind of grouping of results? In that case there is actually a known issue, which is going to be patched in the upcoming version.
Until then I have a very quick fix for the issue.
Open up the \wp-content\plugins\ajax-search-pro\includes\views\results\group-header.php file on the server.
Go to the last line (21), which should be this:
[code]<div class="asp_group_header"><?php echo $group_name; ?></div>[/code]
Change that line to:
[code]<div class="asp_group_header group"><?php echo $group_name; ?></div>[/code]
That should solve the issue 🙂
Ernest Marcinko
KeymasterHi!
It looks like something is changing the input field width to 100 pixels in mobile view and the text is inputted into the autocomplete area.
I think I have a very simple solution. Use this custom CSS:
[code]input.orig {
min-width: 275px !important;
}[/code]You can add this to the custom CSS field on the search plugin Theme Options -> Custom CSS panel.
Ernest Marcinko
KeymasterHi!
No problem at all, happy to help you 🙂
I’ve found the problem. I suppose when copy-pasting from my previous post the double quotes (“) were glitched and displayed incorrectly.
I’ve changed them to single quotes in your theme footer.php, it seems to be working now.
Ernest Marcinko
KeymasterOh then, definitely that’s the problem. The script is trying to trigger a key-up event, which is not working of course.
So all you need to do is change line 16 of the code I’ve given you from:
$input.keyup();
to:
$($(“.promagnifier”).get(0)).click();
And that will trigger the icon click instead, which hopefully works 🙂
Ernest Marcinko
KeymasterOkays, I think I might know why.
I’ve made a modification to the code, please try again: http://pastebin.com/raw.php?i=6hymZi4h
Ernest Marcinko
KeymasterHi!
The only way is using a custom script code in your website footer. First you will need to change one setting though, in order to make the search work with 0 input characters.
1. Go to the General Options -> Behavior panel and change the “Minimal character count to trigger search” option to 0
2. Add this script to your theme footer before the closing body tag: http://pastebin.com/raw.php?i=6hymZi4h
You can change the searchPhrase variable in that code if you want to use a default search phrase.
Ernest Marcinko
KeymasterHi!
The only way is using a custom script code in your website footer. First you will need to change one setting though, in order to make the search work with 0 input characters.
1. Go to the General Options -> Behavior panel and change the “Minimal character count to trigger search” option to 0
2. Add this script to your theme footer before the closing body tag: http://pastebin.com/raw.php?i=6hymZi4h
You can change the searchPhrase variable in that code if you want to use a default search phrase.
I do not recommend changing the CSS files directly as most of them are generated dynamically based on back-end values. Moreover updating the plugin will override all of your changes.
Most of the settings you can change on the Theme Options -> Isotopic results panel.
Rather changing the CSS I recommend adding your custom CSS code to the Theme Options -> Custom CSS panel. It’s safe and does not get overridden by updates.Ernest Marcinko
KeymasterHi!
Try to go to the plugin caching options submenu on the back-end and save it without changing anything. It looks like an options incosistency, so it might help.
-
AuthorPosts