[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

It all depends on the keyword suggestion sources.

For the maximum relevance I would suggest not using the google, and trying to use post titles and taxonomy terms (order also matters): https://i.imgur.com/5SjIvD4.png
The keywords index from the index table is not taken into account, unfortunately most servers would not be able to handle that. We are working on a possible workaround for future release that may allow that as well.

The plugin can’t randomly guess/correct the words linguistically, that would require a 3rd party AI to make auto-corrections like the google search engine does. Unfortunately we can’t integrate those, they would be extremely for users and require a connection to a 3rd party service.

The suggestions are based on the existing data sources. A very efficient algorithm takes at most 50 000 phrases from the source and tries to get the closest possible matches within a threshold. It is fast and does not require a 3rd party service to pay for – however it is not as clever as an AI autocorrection.

[Ernest Marcinko]

Thank you very much 🙂

[Ernest Marcinko]

Hi,

You can find all of these options under the theme & styling panel.

Width & Height & Color here: https://i.imgur.com/RGwwAke.png
Search input font size and color: https://i.imgur.com/jdhyx9r.png
Other results text typography options here: https://i.imgur.com/ABUV0Rh.png

I hope this helps.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Great 🙂

I have also made a feature request which I already resolved, so from the upcoming release the text/vtt type is going to be supported by default.

If you don’t mind, I will close this topic soon and mark it as resolved, feel free to open another one if you have other questions or issues.

If you like the plugin and have not rated already, feel free to leave a rating on your codecanyon downloads page and on the wordpress plugin repository, it’s greatly appreciated.

[Ernest Marcinko]

Oh, the file may be parsed very well, the code just does not include that part, try this:

add_filter('asp_index_file_custom_parse', 'asp_index_file_custom_parse_vtt', 10, 2);
function asp_index_file_custom_parse_vtt($text, $post) {
	if ( $post->post_mime_type == 'text/vtt' ) {
		$content = file_get_contents(get_attached_file( $post->ID ));
		update_post_meta($post->ID, '_asp_attachment_text', $content);
		return $content;
	}
	return '';
}

If all goes well, then after indexing it should show the file contents.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

This is the feature you are looking for.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi Karen,

I see you opened a separate ticket, I will try answering there.

[Ernest Marcinko]

I just tested but it seemed to work okay on my end.

If you haven’t, then can you please try to add text/vtt to the index list and create new index?
If no luck, then can you add temporary back-end and SFTP access? I will try do debug manually.

[Ernest Marcinko]

Hi,

I believe you are looking for the front-end filters section here.

In your case I would suggest creating a sidebar and placing the search and the settings shortcodes there. You can also pair it with the results page live loader feature, so when you change the filters the results page reloads on the fly as well.
Unfortunately front-end sorting options are not available yet.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Author]

Posts