[Ernest Marcinko]

Hi!

I’ve found the problem. Since the site uses an older wordpress version, there was a missing function name I didn’t know about. I’ve disabled one line in the search plugin, it should work fine now 🙂

[Ernest Marcinko]

Hi!

It’s not possible right now. I understand your point, but the problem is that the posts (or custom post types) are not categorized by taxonomies (Importane, Inventor, Parent Status) but by taxonomy terms (Patent Pending, Patented etc..) on database level.

Even if this was possible, searching for example “Patented” won’t give you all the results from under the “Patented” category, because the category (term) selectors are filters.

To search in all term names (within all taxonomies) related to each post you can activate the “Search in terms? (categories, tags)” option on the bottom of the General Options -> Sources tab. Please be aware that this might affect the search performance greatly.

[Ernest Marcinko]

Hi!

Thank you for reporting this. The stackoverflow link was actually very useful. I’ve once experienced this issue, but I thought it was just some one time rendering problem.

It looks like that the problem is indeed the too early loading of the isotope, when the images are not loaded yet – and the block height calculation is incorrect. I think the best solution is to force a layout change when the images are loaded. That way the isotope loads with the page, and re-renders the correct spacing when the images are ready, without causing a lag.

You will have to do 2 things in order to fix this until I incorporate a bugfix:

1. Open up the plugin file plugins/related-posts-pro/js/nomin/type.wrapper.js and go to lines 89 – 107, where you should see this:
[code]
create_isotope: function() {
return isotope = new rpp_isotope( this.o.node, {
// options
itemSelector: this.o.elements,
layoutMode: this.o.isotopeLayout,
filter: this.o.filterFns[this.o.initiallyShow],
sortBy: this.o.defSortValue,
sortAscending: (this.o.defSortOrder=="desc"?false:true),
getSortData: {
rpp_title: this.o.titleSelector,
rpp_relevance: this.o.relevanceSelector + ‘ parseInt’,
category: ‘[data-category]’,
weight: function( itemElem ) {
var weight = $( itemElem ).find(‘.weight’).text();
return parseFloat( weight.replace( /[\(\)]/g, ”) );
}
}
});
},
[/code]

replace that function with this code:

[code]
create_isotope: function() {
var iso = new rpp_isotope( this.o.node, {
// options
itemSelector: this.o.elements,
layoutMode: this.o.isotopeLayout,
filter: this.o.filterFns[this.o.initiallyShow],
sortBy: this.o.defSortValue,
sortAscending: (this.o.defSortOrder=="desc"?false:true),
getSortData: {
rpp_title: this.o.titleSelector,
rpp_relevance: this.o.relevanceSelector + ‘ parseInt’,
category: ‘[data-category]’,
weight: function( itemElem ) {
var weight = $( itemElem ).find(‘.weight’).text();
return parseFloat( weight.replace( /[\(\)]/g, ”) );
}
}
});
$(window).load(function() {
iso.layout();
});
return iso;
},
[/code]

2. Change the javascript source to non-minified – because the change is applied only there. Go to the Compatibility Settings submenu and change the Javascript source option to Non minified: http://i.imgur.com/fsXFjNr.png

After clearing your cache and refreshing the page a few times the issue should be solved.

[Ernest Marcinko]

Hi!

You might have actually discovered a bug. Luckily it’s just a Notice, which might not have any effect at all.

I will investigate this issue further, as I don’t know the cause yet.

Until then please try the following solution:

1. Open up the \wp-content\plugins\ajax-search-pro\includes\views\asp.shortcode.categories_terms.php file, where you should see this line:
[code]$_invisible_terms = array_diff($_needed_terms, $style[‘selected-showterms’]);[/code]

2. Change that line to:
[code]$_invisible_terms = @array_diff($_needed_terms, $style[‘selected-showterms’]);[/code]

That might help.

[Ernest Marcinko]

Hi!

Sorry for the late response.

I see the problem now. Some of the features of of the settings box are not used when it’s in “block” layout mode.
When testing, I’ve found that most of the themes use better matching color schemes for fieldset elements. The “hovering” layout is different though, because it has to match the search settings icon as they are essentially connected.

I suggest using some custom CSS. If you need any help with that, let me know.

[Ernest Marcinko]

Hi Eno!

That is perfectly fine. A test server is not counted as an end product. You can use it in your development process as many times as you want it.

It’s very kind of you to respect the licensing, very few people value the work put in these stock products.

On a related note. I’m not sure if you are familiar with the referral program envato offers, which would benefit you I believe. Here are some details: http://themeforest.net/make_money/affiliate_program

Basically when you tell your customer to buy my or any other authors plugin, you can put your name as the referral, and earn a comission of 30% of their initial deposits as envato kredit (which you can use to purchase items). I’m not sure if you need to become an author for that, but it’s worth a try.

For example the link to Ajax Search Plugin would look like this with your username: http://codecanyon.net/item/ajax-search-pro-for-wordpress-live-search-plugin/3357410?ref=enoversum

So basically you add the ?ref=enoversum to the end of any codecanyon or themeforest page and the newly registered user becomes your referral.

[Ernest Marcinko]

Hi!

Could you please point me to a page where a search instance is active? I could not find any on the front-end and I do not want to touch anything but the search on your site 🙂

On the back-end preview the search looks all right, so I guess the problem only occurs on the site front-end.

[Ernest Marcinko]

Should work with any number, at least it does on my test environment.

[Ernest Marcinko]

Hi!

The logic is changeable, but it’s from an exclusion viewpoint for various reasons. (mostly because of how wordpress stores terms) By default it’s the AND logic that’s used, but it’s connected only with the exclusions.
I’m working on an update which will have a wider selection of term logics with a documentation as well.

Until then the best possible thing to do is to make a minor modification to the code to force an AND logic on the non-excluded categories.

1. Open up the plugins/ajax-search-pro/includes/search_content.class.php file
2. Go to lines 182-188, where you should see this:

[code]
if (count($all_terms) > 0) {
$words = ‘–‘ . implode(‘–|–‘, $all_terms) . ‘–‘;
if ($term_logic == ‘and’)
$term_query = "HAVING (ttid NOT REGEXP ‘$words’)";
else
$term_query = "HAVING (ttid REGEXP ‘$words’)";
}
[/code]

3. Modify those lines to this:

[code]
if (count($all_terms) > 0) {
$term_query = "HAVING (ttid REGEXP ‘–" . implode("–‘ AND ttid REGEXP ‘–", $all_terms) . "–‘)";
}
[/code]

Now, if you have all the other categories excluded but those two on the Advanced options panel, then this should probably work.

[Ernest Marcinko]

Hi!

There are two explanations I can see here:

1. Either one of the selected fields (title, content, excerpt etc..) has both words (or parts of these words) “nature” and “animals” in it. I’m suspecting the post content, which is usually longer than the title or other fields.

2. The plugin is functioning in fulltext mode. There is a known bug, where in some cases the plugin uses the fulltext mode even though it’s deactivated. In fulltext mode is no such thing as search logic, as it’s a natural matching database algorithm.
To get rid off this, go to the Fulltext search Settings submenu and make sure the Use fulltext search when possible option is turned OFF (https://i.imgur.com/IYO5eUx.png). Then save the settings even if you haven’t changed anything to make sure the values are synced to the database.

If you see an error message like “MyIsam tables are disabled, fulltext search not available!” when going to the fulltext options page, then the fulltext search definitely not the issue.

[Ernest Marcinko]

Integrating and customizing the plugin is not part of the support, but I guess I can help you with that.

The search is a dynamical element, placing into a javascript animated container might cause loss of some mandatory events.

I’ve added a few lines of CSS to make a difference.

You need an exact width and different z-index to avoid conflicts:

[code]
.ubermenu-content-block .asp_main_container {
width: 230px !important;
}

.ubermenu-content-block .asp_main_container .probox .proinput {
min-width: 100px;
}

div.ajaxsearchpro[id*="ajaxsearchprores"] {
z-index: 1100000 !important;
}
[/code]

[Ernest Marcinko]

Of course. The following custom CSS did the trick:

[code]
div.ajaxsearchpro[id*=’ajaxsearchprobsettings’].searchsettings {
text-align: right;
}

div.ajaxsearchpro[id*=’ajaxsearchprobsettings’].searchsettings fieldset {
text-align: left;
}
[/code]

[Ernest Marcinko]

Hi!

I’ve found the issues. Some of the CSS rules were overwritten by other files, but I’ve added the following ones to the search custom CSS panel to enforce the correct RTL layout:

[code].resdrg .image {
float: right !important;
margin: 0 -10px 0 10px !important;
padding: 0 !important;
}

.rtl .resdrg * {
direction: rtl;
text-align: right !important;
}

div.ajaxsearchpro[id*=’ajaxsearchpro’] .mCSB_container {
margin-right: 0px !important;
margin-left: 10px;
}

.orig {
width: 100% !important;
}[/code]

The text should appear correctly now, as well as the results.

[Ernest Marcinko]

Hi!

Thanks! I didn’t get the login details though. Could you please edit your initial post, or upload a .txt file with the details? Both methods are safe and not visible to others.

[Ernest Marcinko]

You are welcome and thank you for the kind words! 🙂

If you want you can rate this product on your codecanyon downloads page: http://codecanyon.net/downloads

Feel free to contact me here if you have any questions or problems.

[Author]

Posts