[Ernest Marcinko]

Hi!

The way these kinds of plugins work is the following:

• They hook to the “the_content” filter with a function
• Depending on the priority of the function, the display order is decided
• This priority is usually set to default, which is number 10
• The lower this priority number is, the sooner the plugin output is displayed after the post/page content
• Functions with the same priority are displayed by the call order
• Priority numbers below 10 are usually not working (not displaying)

The problem is that if every other plugin uses the default priority, then it’s not adjustable to higher (number 9 or below), because it won’t work.
In this case the only possible option is to change other plugin priority codes and then the Related Posts Pro priority codes. The problem is that this is only possible by editing the plugin codes, which is not recommended, because an auto update will override the changes.

I hope I explained it clearly, it’s a bit complicated issue. My overall answer is, that using the theme shortcode in your case is the best option you can do, unless you know how and which plugin codes you need to edit to change the layout priorities.

[Ernest Marcinko]

Hi!

I’m not sure if I understand correctly. By PDF you mean a PDF document?

For refunds, please contact the envato support, as they are responsible for the sales managment. I think you can reach them on the following link: https://help.market.envato.com/hc/en-us

[Ernest Marcinko]

Yes, will be uploaded later today with the new documentation. I expect it to be approved on later tomorrow or during the weekend, it depends on codecanyon.

[Ernest Marcinko]

Yes, you can work with this safely.

If you make a backup copy of the wp-content/plugins/ajax-search-pro folder, then it should be fine 😉

[Ernest Marcinko]

Hi!

I’ve noticed you moved from the test environment to live a live domain. Some options may change in the database when moving (due to the server url change), so I saved all the options again on the search backend.

I think it should work now.

[Ernest Marcinko]

Hi!

Thank you for the detailed description and the login details. The plugin needed a re-activation, now it should work as before 😉

When you are updating via codecanyon, please always do follow the safe update steps. You can find them in the documentation (first chapter) or in the knowledge base here: https://wp-dreams.com/knowledge-base/updating-from-older-versions/

An auto updater will be released with the upcoming version, after proper testing. After that, hopefully these steps will be unnecessary.

Sorry about the inconvenience.

[Ernest Marcinko]

The update should work fine, I don’t think that issue will come back.

If you want to be sure that everything is all right, then you can wait for the next bugfix update (end of this week), as I’m currently collecting possible bugs with the new version.

[Ernest Marcinko]

Sure, with a bit of a javascript tweak. Put this script to the footer file of your theme just before of the closing body tag:

[code] <script>
jQuery(function() {
if (jQuery(‘.probox .proinput input.orig’).length>0)
jQuery(‘.probox .proinput input.orig’)[0].focus();
});
</script>[/code]

[Ernest Marcinko]

Hi!

I could not connect with the ftp credentials, but I’ve found the problem and made a temporary solution via the admin panel. It’s the first bug found in the 4.0 version.

I’ll investigate further on my test environment, to make a correct fix for the next bugfix version release.

[Ernest Marcinko]

Indeed. Let me cross check the changes regarding this from v3.5 to 4.0.

I will most likely log in to your site both admin and ftp to run some tests on the plugin code, the search might not work for couple of minutes in the next few hours.

[Ernest Marcinko]

Sorry about not answering sooner.

I was waiting for version 4.0 to be approved on codecanyon – which makes result templating possible.

You will be able to make a few changes, but there are of course limitations, because the main result structure should remain the same – as there are javascript handlers attached to them, and too drastical changes might result in a malfunctioning search bar.

You will find the result template files in the ajax-search-pro/includes/views/results/ folder.

I think you are looking for the vertical.php file in that folder. It’s the template file for the a vertical result. On the beginning of that file you will find some advices and descriptions about accessible variables and stuff.

First of all, make a copy of this file, so if something goes wrong, you can still revert it.

This file is called every time a result is generated. The “$r” variable is an object holding some information about the current result. It has the following structure:

$r->id – the ID of the post, term or any result object [always set]
$r->content_type – the content type (post, page, term etc..) [always set]
$r->title – the title of the result [can be empty]
$r->content – the content of the result [can be empty]
$r->author – the author name [can be empty]
$r->date – the date [can be empty]
$r->post_type – the post type (if it’s a post) [can be empty]
$r->ttid – unfiltered list of terms related to the post in [deprecated, do not use]

and of course you can use any available wordpress or plugin function here.

I’m currently working on a new demo, features update and new documentation. After finishing those, there will be a new knowledge base article about this new templating system as well.

If you have experience in php/html/CSS I think you will be able to use it for now 😉

[Ernest Marcinko]

Yes, we are talking about the same thing.

I think I know why it isn’t working. Version 4.0 just rolled out a few days ago, you might not get a notification from codecanyon.
If you update, this solution should work.

If you don’t want to update (if you have custom code or something applied), then try this code instead, it will probably work with version 3.5:

[code]
add_filter(‘asp_results’, ‘asp_get_woo_term_image’);
function asp_get_woo_term_image($results) {
foreach($results as $k => $result) {
if (function_exists(‘get_woocommerce_term_meta’) && empty($result->image)) {
$thumbnail_id = get_woocommerce_term_meta( $result->id, ‘thumbnail_id’, true );
$image = wp_get_attachment_url( $thumbnail_id );
if (!empty($image))
$results[$k]->image = $image;
}
}
return $results;
}
[/code]

[Ernest Marcinko]

Hi!

I’m currently preparing new documentation, demo and a blog post for detailed descriptions about the new features – there is a lot. It should be up in the end of this week.

1. Yes, there is one implemented based on title.
2. Yes, rtl should work now.

[Ernest Marcinko]

I remember now. It’s the ubermenu CSS file, it’s not the same as on the live server.

This file: \wp-content\plugins\ubermenu\standard\styles\basic.css

You don’t need to copy the whole file if you don’t want to, but you need to add 2 more lines to the beginning of that file. So on the demo server where you see this on line 11:
[code]#megaMenu.megaResetStyles span,
#megaMenu ul.megaMenu,
#megaMenu ul.sub-menu,[/code]
change it to:
[code]#megaMenu.megaResetStyles div:not(.probox),
#megaMenu.megaResetStyles div:not(.probox *),
#megaMenu.megaResetStyles span,
#megaMenu ul.megaMenu,
#megaMenu ul.sub-menu,[/code]
and that’s it. Problem solved. I didn’t edit, because I don’t know where the demo files are.

[Ernest Marcinko]

Indeed, I made a syntax error there, change that code to:

[code]//*ADD SEARCH TO HEADER RIGHT MENU
add_filter( ‘wp_nav_menu_items’, ‘theme_menu_extras’, 10, 2 );

function theme_menu_extras( $menu, $args ) {
if ( ‘header’ !== $args->theme_location )
return $menu;

$menu .= ‘<li class="right search">’ . do_shortcode(‘[wpdreams_ajaxsearchpro id=1]‘) . ‘</li>’;
return $menu;
}[/code]

[Author]

Posts