[Ernest Marcinko]

Thanks, it works.

Currently however I see the search in the middle of the page, and it looks normal to me.

[Ernest Marcinko]

Hi!

You can safely upload private details in a .txt file to this thread, it’s not visible for public, or other users. (just me and you)

[Ernest Marcinko]

Well, I don’t see any usable reference here unfortunately. But, I was able to see the problem on my iPad, since I’m on a windows machine.

This is going to be a theme or plugin conflict, since it’s not happening on the demo page.

I tried to disable some of the javascript files to load via the plugin manager, but that didn’t help I think.

The resize issue was only happening on the front page of the site on my iPad, can you confirm that?

Unfortunately I can’t access the javascript files for debugging via the plugin manager, only the php files. If you want, you can provide ftp access and I can try to investigate further on this, but I can’t promise I find the source of the problem, since this is most likely related to other plugins as well.

[Ernest Marcinko]

Thank you 😉

After some debugging I was able to find the storage method of the images. I’ve implemented the following code to your themes functions.php file:

[code]
add_filter( "asp_results", "asp_extra_terms_image_results", 1, 1 );

function asp_extra_terms_image_results( $results ) {

foreach ($results as $k=>$v) {
// get the term images
if ($results[$k]->image != null && $results[$k]->image != "")
continue;

/* Try to get woocommerce image */
$x = get_woocommerce_term_meta( (int)$v->id, ‘thumbnail_id’, true );
if ($x != "") {
$im = wp_get_attachment_url( $x );
if ($im != ”) {
$bfi_params = array(‘width’ => 70, ‘height’ => 70, ‘crop’ => true);
$results[$k]->image = bfi_thumb($im, $bfi_params);
}
}

/* Other term image then.. */
$x = get_metadata("woocommerce_term", (int)$v->id);
if (isset($x[‘pa_merk_thumbnail_id_photo’][0])) {
$im = wp_get_attachment_url( $x[‘pa_merk_thumbnail_id_photo’][0] );
if ($im != ”) {
$bfi_params = array(‘width’ => 70, ‘height’ => 70, ‘crop’ => true);
$results[$k]->image = bfi_thumb($im, $bfi_params);
}
}

}

return $results;
}
[/code]

Since it is placed into the themes functions.php file, this code will remain in case of updating the search plugin.

[Ernest Marcinko]

Hi!

I can’t seem to log in to the site, it requests .htaccess authentication. Could you please check that, or upload a txt file with authentication details?

[Ernest Marcinko]

Hi!

Are there any more details on this, like error logs, error codes or anything similar?

Does the same thing happen if you try the demo page?

[Ernest Marcinko]

Hi!

It’s because on that example the results window is placed on a different location with the results shortcode. Also, the layout position of the search results is set to “blocking” and not “hovering” – meaning that it’s not hovering above the surrounding content, but rather pushing it down.

Here is a link to a guide on how that example was created: https://wp-dreams.com/knowledge-base/two-column-search-setup/

There is also a brief explanation on this in the documentation: http://wp-dreams.com/demo/wp-ajax-search-pro3/docs/#positioning_the_results_elswhere

The “hovering” result list is resized to the search width because of the absolute positioning. The “blocking” results list however has auto width, so it will be as wide as the container element.

[Ernest Marcinko]

Hi!

That would be a good solution I guess. The new search update is almost ready for release, which uses prefixed function names (including this one) to prevent these types of issues forever, so a temporary solution is also fine. (like commenting out the code, or removing it)

You can also edit the main theme to add the “function_exists” statement there as well, because after the search update, this function name will no longer be declared in the search code.

[Ernest Marcinko]

Hi!

1.00 is the latest.

[Ernest Marcinko]

Hi!

It didn’t work, because that function echos the content, and the part where you added was already echoed, so it run twice.

I’ve added the following lines to fix that:
[code]
ob_start();
dynamic_sidebar( ‘asp_top_searches_widget’ );
$asp_plus_sidebar = ob_get_clean();
[/code]

I see you also wanted to make those keywords white, so I added a CSS rule, because putting them into a paragraph will not help. The following rule is added to the search custom CSS section:

[code]
.asp_top_keywords {
margin: 0 12px;
}

.asp_top_keywords a {
color: #ffffff;
}
[/code]

[Ernest Marcinko]

Hi again!

First of all check if fulltext search is not activated. If you go to the Fulltext Search Options submenu you can check if it’s indeed deactivated: http://i.imgur.com/9Mzc5tG.png
Even if so, save the settings, just in case. In fulltext mode the adjustable relevance is ignored, because fulltext search database uses internal relevance values.

After that, you should adjust the Relevance Values. You can read more about them in the documentation: http://wp-dreams.com/demo/wp-ajax-search-pro3/docs/#search_relevance_options

Basically you want to decrease the terms weight, increase the title weight, and decrease the content weight.

Try values like:
Title weight: 10
Content weight: 5
Terms weight: 2 (or 1)

These should increase title relevancy, and decrease content and terms relevancy by a bigger factor.

[Ernest Marcinko]

Hi!

d. I can’t see this setting anywhere. Do I need an add-on for that setting to appear? I have a clean woocommerce installation with no addons.

[Ernest Marcinko]

Nice, at least we know where the problem is.

However I can only offer very limited 3rd party support. I hope you understand, that authors simply can’t buy all the conflicting plugin combinations (there are like 1 million commercial, and another 2 million non commercial plugins available) just to test them. There is not enough time or money to do that.

If you don’t want to provide details to your live server, you can still create a test or development environment with login and ftp access, where both plugins are active and conflicting, I’m more than happy to check that and fix it if possible.

And, if none of this is possible, then probably the only solution I can see here is to add the correct script manually to one of the theme files, possibly the footer. I have grabbed the related posts pro script with the syntax errors from your site and corrected it. All you need to do now is to add this to the footer of your site. You will have to edit one of your theme files for this via FTP. In the active theme directory there should be a file called footer.php or something very similar. The active theme directory is usually wp-content/themes/{theme-name}/, you should look for that file there. On the very very bottom of that file there are usually these 2 lines present:
[code]
</body>
</html>
[/code]
These are the closing tags for the body and the html element. Above the closing body tag, add the following lines:
[code]
<script type="text/javascript">
rppjQuery(document).ready(function ($) {
rppjQuery(‘div[id^="relatedpostspro_0_"]’).relatedpostspro({
"node": null,
"elements": ".rpp_item.rpp_visible",
"elementsAll": ".rpp_item",
"visibleClass": "rpp_visible",
"fadeoutClass": "rpp_fadeout",
"titleSelector": ".rpp_title",
"loadingSelector": ".rpp_cssloading_container",
"relevanceSelector": ".rpp_relevance",
"type": "isotope",
"isotopeLayout": "fitRows",
"transitionAnimation ": "fxFerris",
"initialFilter": "post_type",
"autoplay": true,
"autoplayTime": "6000",
"overrideFilter": true,
"minShow": 8,
"defSortValue": "rpp_relevance",
"defSortOrder": "desc",
"showSettings": 1,
"showSearchByDefault": 0,
"exactSearchMatchOnly": 1,
"dots": true
});
});
</script>
[/code]

This will add the declaration code statically, and the plugin should start working. The downside is, that this is a static code, so changing some of the settings on the plugin backend may not have effect here.

[Ernest Marcinko]

Hi!

Sorry about the late response.

Well, currently it’s not possible, because the layout is created inside the javascript. And even if the html would be possible to append (the button), the functionality still needs to be programmed.

I can’t accept custom work unfortunately.

[Ernest Marcinko]

Hi again!

Try the following custom CSS:
[code]
.proclose,
.promagnifier,
.prosettings {
z-index: 4 !important;
}
[/code]

[Author]

Posts