[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi Dušan,

The option is used to store and register Polylang String Translations for the plugin. If you don’t use Polylang anymore you can delete it, otherwise you can set the autoload row to “no” or “auto” in the database if you want to.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Great work!

I will keep this in mind and recommend to others if they have a similar issue. Thank you for sharing!

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi!

It is very likely possible, but some custom code will be required, depending on how these roles are set. I found a previous topic, where someone else had a similar request, and this custom code was suggested:

add_filter( 'asp_results', 'asp_filter_posts_by_capability', 10, 1 );
function asp_filter_posts_by_capability( $results ) {
	foreach ($results as $k => &$r ) {
		if ( !current_user_can('read_post', $r->id) )
			unset($results[$k]);
	}
	return $results;
}

This however may need to be edited with the correct capability or a function to check if the user is a customer.

[Ernest Marcinko]

Hi Yan,

Some rules are indeed enforced to ensure maximum compatibility, as many themes do override paddings and margin (and other rules as well) very agressively.

You can still override these by making higher specificity CSS rules, for example:

div#ajaxsearchpro4_1 .probox .proinput input.orig,
div#ajaxsearchpro4_2 .probox .proinput input.orig {
    padding: 12px !important;
}

However if you are looking to increase the spacing between the search input and the container, you can use this option too: https://i.imgur.com/zvBqmyQ.png

[Ernest Marcinko]

Hi Christian,

Luckily the error is nothing serious, it’s only a forced type coercion issue report.

Can you add temporary back-end and sFTP access? I will try to debug the issue directly as the exact location is not reported in the error message. I have a suspicion where it might be, just want o be sure.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi Emiel,

I’m afraid there is no possible solution for it. As far as I remember Weglot stores the transalations on the remote server and the content is translated on the fly whenever a request is made. So the plugin only sees the original data, the translation is applied after that.

I usually recommend WPML or Polylang plugins for searchable contents – those are stored locally and are accessible for search plugins.

[Author]

Posts