[Ernest Marcinko]

Hi!

Yes, I’m planning to make serious changes to the javascript code as well. This is definitely not a long term solution, that’s why I suggested only to finalize once it’s done.

Unfortunately the plugin code has grown seriously over the time, and I’m focusing on bugfixes and crucial updates as much as I can every day. It’s taking me quite some time. Plus when I created the plugin I wasn’t as much experienced as now, but I can transition the code to something entirely new, because of maintaining backwards compatibility. It’s catch-22 🙂

Plus if I make a mistake (and I did many times) within an update, a nice hug of support ticket is awaiting the following week, which takes away good amounts of development time.

No worries, I’m definitely going to do something to make this much easier for developers, I would say the next major update will already have this feature implemented 🙂

[Ernest Marcinko]

Hi!

I’m not sure I understand your requests correctly, because I can’t see an url with the ticket. Can you please send it again with your next post?

[Ernest Marcinko]

Is there a site where I can check the problem? I need more information to find/fix issues. Is it not working at all, or are there some parts not working?

Can you please provide temporary FTP and back-end access to check on the problem?

[Ernest Marcinko]

Hi!

I just tried both iPad and iPhone and it’s working for me. I also tested the demo to make sure it’s all right, and it’s also working.

It might have been only a cache issue?

[Ernest Marcinko]

Finally I’m able to get to the login screen. I was always getting an under construction message, it must had been some aggressive caching or something.

1. I’m not sure if I get it right, but I tried the post and page search function on the back-end: http://i.imgur.com/4tnD1jt.png
To me these look all right. Let me know if this is what you meant.

2. I selected:

Exact matches only
Search in title
Search in content
Search in posts
Search in pages

I just tried searching for “francis” and I got a good amount of results.
Then I tried “sfl” got these: http://i.imgur.com/ugtxyyU.png
Then I tried “francis brassard” without Search in content, because I saw there a post with his name in it, and I got it as result: http://i.imgur.com/yg6TCu8.png
Then I tried again “francis brassard” with the Search in content enabled: http://i.imgur.com/51ihWRR.png

Based on this it looks to me that it’s working correctly. Does the problem occur on another specific example?

Also, I turned off the attachment search to test these options, I guess you only want to search in posts and pages.

3.
– It was a CSS bug. The vertical options color was applied there, so I changed it to transparent as it should have been by default.
– It is not possible to change the spacing, it’s adjusted by the isotope script. Now there is a visible spacing, since the backround is finally transparent.
– The tick color is inherited from the default theme layout to match, the only way of changind that is to use custom CSS, like so:

.searchsettings .option label:after {
border: 3px solid #00FF00 !important;
}

Change the code color in the code above to your liking and add the code to the search instance options Theme Options -> Custom CSS panel.

4. It’s most likely theme related bug, or some javascript files are not loaded every time correctly. The results are presented as simple links to click on, so there is no way of any interference with the styling.

Let me know if you need anything more 🙂

[Ernest Marcinko]

Hi!

Found the problem. It was an issue with the taxonomy term exclusion part. I’ve fixed it along with other things, and a new version was uploaded to codecanyon just minutes ago.

It should be available in 48 hours (it usually takes them 12), you should get an email notification once it’s ready for download.

[Ernest Marcinko]

Thanks!

I will try to recreate this exact scenario now and see how the query looks like. It definitely seems something is not right with the exclusions. A post from 1 matching exclusion should not show up, no matter what.

[Ernest Marcinko]

Hi!

Sorry for the late response. Unfortunately I still can’t reach the login page 🙁

I tried with a few different browsers and a VPN provider as well, to make sure it’s not my cache doing it, but it looks like it’s not. Can you check again please?

[Ernest Marcinko]

Hi!

I think I know why. The widget position where the search is placed is set to “relative” in the CSS. It means, that it traps the fixed positioned search inside of it. I can suggest two solutions to this:

1. Setting the footer to the default, static position, with this small custom CSS snippet:

[code]#mk-footer {
position: static !important;
}[/code]

You can add this snippet to the search instance options Theme Options -> Custom CSS panel. Or perhaps your theme also has an option somewhere to use custom CSS.

2. Moving the search shortcode directly to the theme footer file.
The theme footer file is usually named as footer.php in the theme directory. You can put the search PHP shortcode there, just before the closing body tag (usually just before the end of the file). So it’s something like this:

[code]
<?php echo do_shortcode(‘[wpdreams_ajaxsearchpro id=2]‘); ?>
</body>
</html>
[/code]

I would prefer the 2. solution, as it does not change any styling. But if that’s not possible, the first suggestion should also work 🙂

[Ernest Marcinko]

Hi!

The problem with re-initialization is that there is no automatical way of doing it, as it’s not possible to detect from an outside scope that there was an ajax request finished and if it should re-initialize the plugin or not.

The plugin initialization is bound to the window ready event, which cannot be triggered twice. That would have been a good solution though.
What you can do is to search for the initilaization script on the page. Keep in mind that it contains parameters, which are generated dynamically if you change the settings on the back end. So I suggest only implementing this once you are done configuring the plugin.

If you open the page source and look for something like:

[code]
jQuery(document).ready(function () {
jQuery("#ajaxsearchpro1_1").ajaxsearchpro({
homeurl: ‘http://wp-dreams.com/demo/wp-ajax-search-pro/&#8217;,
……
……
});
});
[/code]

Its a long long code with lot’s of parameters there. What you can try to do is to put the inner part of this script into the success ajax handler function body, so your code should look something like:

[code]$.ajax({
type: ‘GET’,
url: ‘page-to-request.html’,
success: function (data, textStatus, jqXHR) {

// Here is your code and stuff…

// Reinitialise ajax search pro, make sure the window.ready part is NOT here, only the inner part!
jQuery("#ajaxsearchpro1_1").ajaxsearchpro({
homeurl: ‘http://wp-dreams.com/demo/wp-ajax-search-pro/&#8217;,
……
……
});

}
});[/code]

I have no idea if this is going to work, but it’s definitely going to trigger something.

[Ernest Marcinko]

Hi!

I can’t see the plugin anywhere on the page right now active, can you please place it somewhere.

I checked the error console, and there is an error reported from the jQuery, see screenshot: http://i.imgur.com/v4GbzSw.png
I’m not sure if it’s related, but it’s definitely not good. There is no information however what’s triggering the error. Can be any plugin or some other javascript file.

[Ernest Marcinko]

Hi!

I’m working on that documentation part yet, but it’s a different topic.

Currently it’s hard coded as a pageview in the code, but you have an excellent point. I should probably add more options and make it possible to change the pageview type to an event. I honestly didn’t think of that when creating this feature.

I’m very close to releasing a minor update regarding a few bugfixes and such. I’m going to add a few more options to the Analytics panel before the release to make this change possible.

[Ernest Marcinko]

Hi!

If you mean post tags, then it’s unfortunately not possible yet. Every other taxonomy term should work, except for tags.

It’s a long story why it’s not implemented yet, but I’m working on it 🙂

[Ernest Marcinko]

Hi!

Thank you for the kind words!

1. Yes, exactly.
2. Not yet. This feature was requested by many, I’m definitely going to implement it as soon as I can 🙂
3. Not neccessarily, it works without the index table just like in older versions. You can use the index table engine as well, but you will have to configure it first under the index table submenu page. Think of the index table engine as a different way of looking up results – the plugin basically will use it’s own database table of generated keywords to look through instead of the whole posts table. It’s a huge CPU saver for big databases. I strongly recommend reading all four Index Table chapters in the documentation to get the idea what exactly this is, and how it works.
4. Statistics database contains all the keywords that had been searched for with the plugin (if the search statistics is enabled, on the Search Statistics submenu). So if you have the statistics enabled and someone searches for “xyz”, then it’s logged.
5. By default it will look in the page Title, content and the excerpt (if available), so you don’t have to put keywords anywhere. You can configure this on the General Options -> Sources panel.
6. Yes, there is. The rounded edges in web-development are defined by a property named “Border Radius”. On the Theme Options -> Overall box layout panel you can define this border radius: http://i.imgur.com/3IvV6CI.png

[Ernest Marcinko]

Hi!

You can disable the description and the images as well, so only the title is visible – that’s as close as it gets to google suggestions.

To disable the images go to the General Options -> Image Options panel.
To disable the description, author etc.. go to the Layout Options -> Results Layout panel.

[Author]

Posts