[Ernest Marcinko]

I can’t change the thread to private, you wouldn’t be able to see it (wordpress only lets editor and admins to see private posts).

If you want to post sensitive information, upload it in a .txt file, that is only visible to me and you.

I still cannot see any of these errors on the page. The second one seems to be different. Is that visible on a specific action, like post editing or publishing or something else?

[Ernest Marcinko]

Hi!

It was a duplicate row issue, minor bug. I’ve found and fixed in the corresponding file. It should be working now.

I will include this modification in the upcoming version, so you don’t need to worry about loosing it when updating 🙂

[Ernest Marcinko]

Hi!

Thanks for the details! I cannot seem to have permission to change files with the FTP account. I can see the plugin files, but I can’t change anything. Can you please take a look at permissions?

The issue seems to be unkown yet. I will debug through the index table processing code to see if I find anything unusual. Let me know if I can try the FTP again.

[Ernest Marcinko]

Hi!

Just checked the page, no error message in the console and the plugin is working: http://i.imgur.com/xOD1AF9.png

Probably it’s only your browser or site cache.

[Ernest Marcinko]

Last time I gave up after 2 hours of trying, but I checked again and great news!

I’ve finally found the function responsible to replace the variables in post names. Please try this code:

[php]

add_filter( ‘asp_results’, ‘asp_get_seo_title’, 999999, 1 );

function asp_get_seo_title( $results ) {

foreach ($results as $k=>$v) {
// Continue if not pagepost
if ($results[$k]->content_type != "pagepost") continue;

// Get the seo title
$seo_title = get_post_meta($results[$k]->id, ‘_yoast_wpseo_title’, true);

// Modify it
if ($seo_title !== false && $seo_title != "")
$results[$k]->title = wpseo_replace_vars( $seo_title, get_post($results[$k]->id) );
}

return $results;
}
[/php]

It works on my test environment, and hopefully on yours as well 🙂

• This reply was modified 10 years, 7 months ago by Ernest Marcinko.

[Ernest Marcinko]

That’s definitely a good idea 🙂

[Ernest Marcinko]

I can’t see the range slider script loaded. Please check the Compatibility settings submenu for the Load the NoUI slider JS? option. If enabled, save the options and clear the site cache.

[Ernest Marcinko]

Ah, ok, you found it too 🙂

I’m adding it to the next release bugs list.

[Ernest Marcinko]

You are right, there is a bug, I just found it.

wp-content/plugins/ajax-search-pro/includes/views/asp.shortcode.custom_fields.php on line 40:

[code]echo strpos(‘**’, $matches[2]);[/code]

it should be

[code]echo strpos($matches[2], ‘**’);[/code]

[Ernest Marcinko]

Try leaving it as an empty value, like so:

||All
sample_value1||Sample Label 1
sample_value2||Sample Label 2
sample_value3||Sample Label 3
…

[Ernest Marcinko]

Scheduled to the next update, 10-20 days.

[Ernest Marcinko]

Hi!

You can update safely. I’ve fixed these issues in this release. You can follow the safe update guide to make sure everything goes smoothly.

[Ernest Marcinko]

The update has been approved finally, it should be available now.

[Ernest Marcinko]

The update is manual, but no need of FTP. Simply deactivating, deleting and installing the new is the best way of doing it 🙂

There is a safe update manual in the documentation, which you can follow if you want to: https://wpdreams.gitbooks.io/ajax-search-pro-documentation/content/update_notes.html

It mainly concerns updates from very old versions, but it does work with new ones as well.

[Ernest Marcinko]

No, you did nothing wrong. I get the same thing on my test environment, it’s definitely an unknown bug yet.

In one of the previous versions there was a major change regarding the data presentation and it seems that I’ve either forgot to change that code, or accidentally break it.

If it’s not an urgent case, I will release an update within 7 days that should solve this problem.

[Author]

Posts