[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

It will be okay do not worry 🙂

I suggest opening a different ticket for them, just to have this separate.

[Ernest Marcinko]

You should turn off WP_DEBUG and any level of error reporting for production, if this pops up in the browser then any minor notice will very likely show as well. Deprecation notices should not be shown only on test/dev interfaces.

There is no stable date yet, it is a major refactor. If you want I can suggest a quick fix, only a single file is affected.

[Ernest Marcinko]

Hi,

Make sure to switch to the Pro version of the plugin, and turn off the Lite version. After creating the search instance, please use the following advanced content field: https://i.imgur.com/sTVvAnj.png

{descriptionfield}{flexible_content_product_1_product_info_content}

Because you are using a custom field to store that product data, this should very likely do the trick.

[Ernest Marcinko]

Hi,

Thank you, we are aware of this tiny issue, it is because of a typo in the variable name. Luckily it does not effect anything at all, it will be addressed in the upcoming release. You can safely ignore the deprecation notice.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Okay – so make sure you don’t have any categories as results selected, filtering categories by categories has no effect: https://i.imgur.com/fRVtMUn.png
Instead choose the posts to be returned based on the category filtering: https://i.imgur.com/zjU4RPG.png

[Ernest Marcinko]

You are very welcome and thank you very much for your kind words 🙂

[Ernest Marcinko]

Hi!

This is the feature you are looking for 🙂 That should do the trick.

[Ernest Marcinko]

Thanks, that worked.

So I have added the strings, but that does nothing at all, they are not respected. I also added the full XHR path, that may have resolved it but I am not sure.
So far I can make queries, so that may have helped.

[Ernest Marcinko]

WPML, Loco and Polylang work perfectly fine, as they are not intercepting XHR request reponse bodies, but translating the individual components on the database layer. We can’t really do much to prevent these on-the-fly translations, it is out of the plugins reach.

I can check out the settings for this specific plugin, maybe there is something to change, but I can’t login, the username/password seems to be incorrect. Can you check please?

[Ernest Marcinko]

Hi Tom,

I’m afraid that will not work that way. Selecting the fields to earch for will not get the field values. There might be a way to do it via custom code, but I am not sure:

add_filter( 'asp_results', 'asp_custom_meta_to_wpjson', 10, 4 );
function asp_custom_meta_to_wpjson( $results, $search_id, $is_ajax, $args ) {

    if ( $args['is_wp_json'] ) {
		foreach ($results as $k=>&$r) {
			if ( isset($r->post_type) && $r->post_type == $post_type ) {
				// Declare the fields explicitly
				$r->my_field1 = get_field('my_field1', $r->id);
				$r->my_field2 = get_field('my_field2', $r->id);
			}
		}
	}

    return $results;
}

After this they should be popping up in the the $post->asp_data->my_field1 fields and so on..

[Ernest Marcinko]

Hi!

Sure, I will help you don’t worry.

So after one quick peek I already see the problem. After changing to that language, the search ajax response is altered (very likely by the translator plugin), which is causing the problem. The original response should start with this, but on the translation it is altered like this.
Those are basically special delimiters to filter the ajax request before showing the results. If they are changed, then the plugin can’t fetch the data.

Optimally XHR requests should not be altered, that is a very bad idea. However if you can somehow add these delimiter words to the translation exception list, that may work as well:

___ASPSTART_HTML___
___ASPEND_HTML___
___ASPSTART_DATA___
___ASPEND_DATA___

Unfortunately I don’t know how the translator works, but if you can add exceptions, then this could very likely solve the issue.

[Ernest Marcinko]

You cannot access this content.

[Author]

Posts