[Ernest Marcinko]

Great!

Yes, sort of a hacky way, but I think using a custom CSS to force visibility is the simplest way:

.asp_ss {
    display: block !important;
    opacity: 1 !important;
    visibility: visible !important;
}

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Okay, let’s try something different.

On the index table settings, do NOT select the product variations, that may actually conflict with this. Try this code instead:

add_filter( 'asp_post_content_before_tokenize_clear', 'asp_tokenize_sku_variation', 10, 2 );
function asp_tokenize_sku_variation($content, $post) {
  if ( $post->post_type == 'product' ) {
	$_product = wc_get_product( $r->id );  
	$variations = $_product->get_children();
	if ( !is_wp_error($variations) && is_array($variations) ) {
		foreach ( $variations as $variation ) {
			$content .= ' ' . $variation->get_description();
			$content .= ' ' .  $variation->get_sku();
		}
	}
  }

  return $content;
}

If all goes well this should make some sort of a change.

[Ernest Marcinko]

Hi Leonidas,

I think so, but it may require a bit of custom code and special configuration.

Try adding this code via the Code Snippets plugin or to the functions.php file in your theme/child theme directory – make sure to have a full server back-up first for safety. For more details you can check the safe coding guidelines.

add_filter( 'asp_post_content_before_tokenize_clear', 'asp_tokenize_sku_variation', 10, 2 );
function asp_tokenize_sku_variation($content, $post) {
  if ( $post->post_type == 'product' && ($variations = $_product->get_children()) ) {
	foreach ( $variations as $variation ) {
		$content .= ' ' . $variation->get_description();
		$content .= ' ' .  $variation->get_sku();
	}
  }

  return $content;
}

Then you will have to enable and use the index table engine. It will then index the variation description and SKU for each product as part of a the product content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Oh, I’m sorry, I misinterpreted your query – that is not the button you want.

The actual settings button in the search input can’t be changed via templating, but there is still hope.

Try adding this code via the Code Snippets plugin or to the functions.php file in your theme/child theme directory – make sure to have a full server back-up first for safety. For more details you can check the safe coding guidelines.

add_filter( 'asp_shortcode_output', 'asp_change_search_button_class', 10, 2 );
function asp_change_search_button_class( $output, $id ) {
	return str_replace("<div class='prosettings", "<div class='sok-installningar-" . $id . " prosettings", $output);
}

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

On my end it works on any given page, home, subpages, regardless of the URL. I tried to trigger the error but no luck unfortunately.

If you want, you can add temporary FTP and back-end access, I can take a look.

Before that I would start by removing any custom code you may have, disabling all plugins temporarily, reverting the .htaccess file to default to see if anything changes. If it works then, then there is a conflict somewhere. If not, then it is still possible that the borwser just does not trigger a location change only based on the hashtag without query arguments.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

I’m afraid I am not available for custom jobs, I’m sorry. Discussion about the thumbnail we can continue here.

[Author]

Posts