Search box swapping

Hi Majid,

Thank you for the details!

I have tried a couple of products, but all seem to have the default search bar instead of ajax search pro. It does not seem like a cache issue, but I suspect the product pages may use different headers as the home/search page.
If you are using a theme builder of some sort, check the product page headers template, it is very likely different. If it was the same, te same output would be displayed on the home and product pages.

Have you replaced it manually in the theme editor, or using code or..?

That should work, unless there is some sort of a custom code or a different plugin overriding the search.

You can try a custom code to forcefully deregister the flatsome search shortcode, and replace it with ASP. Try adding this code 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.

function search_shortcode2($atts) {
	extract(shortcode_atts(array(
		'size' => 'normal',
		'style' => '',
		'class' => '',
		'visibility' => ''
	), $atts));

		$classes	= array( 'searchform-wrapper' , 'ux-search-box', 'relative' );
		
		if( $class ) $classes[] = $class;
		if( $visibility ) $classes[] = $visibility;
		if( $style ) $classes[] = 'form-'.$style;
		if( $size ) $classes[] = 'is-'.$size;
		$classes = implode(' ', $classes);

    ob_start();

    echo '<div class="'. $classes. '">';
	 	echo do_shortcode('[wd_asp id=1]');
 	echo '</div>';
 	
 	$content = ob_get_contents();
    ob_end_clean();
    return $content;
}
remove_shortcode("search");
add_shortcode("search", "search_shortcode2");

Can you please add temporary FTP and back-end access? I will debug the code to see what is happening. It is probably a theme/3rd partys code issue, but I will double check.

Thanks!

Looks like it was some sort of an issue with the theme registering the shortcode too early, and no other shortcodes could be registered at that time. Interestingly it only happened in some cases.

It seems like this variation to the code has resolved the issue:

// Replaces Flatsome searhbar with ASP
function search_shortcode2($atts) {
	extract(shortcode_atts(array(
		'size' => 'normal',
		'style' => '',
		'class' => '',
		'visibility' => ''
	), $atts));

		$classes	= array( 'searchform-wrapper' , 'ux-search-box', 'relative' );
		
		if( $class ) $classes[] = $class;
		if( $visibility ) $classes[] = $visibility;
		if( $style ) $classes[] = 'form-'.$style;
		if( $size ) $classes[] = 'is-'.$size;
		$classes = implode(' ', $classes);

    ob_start();

    echo '<div class="'. $classes. '">';
	 	echo do_shortcode('[wd_asp id=1]');
 	echo '</div>';
 	
 	$content = ob_get_contents();
    ob_end_clean();
    return $content;
}

remove_shortcode("search");
add_action( 'plugins_loaded', 'my_plugin_override1' );
function my_plugin_override1() {
    // your code here
	remove_shortcode("search");
	add_shortcode("search", "search_shortcode2");
}

Although I still recommend investigating if you have any type of object cache active, to make sure the issue is not replicated.

Yes. On my end everything seems to work.

This is definitely not an issue with the plugin (and very likely not an issue with the theme either), it is not possible for the same code to execute with the same parameters and have different outputs.

The same pageview is giving different outputs, and that is not possible – unless there something in the middle, which changes the output at will – like a cache plugin, CDN or something on the server side – check opcode cache, other type of opcache, memcached and similar modules.

I could only replicate this one time – on the first pageview the old search was there, on the second (and every pageview afterwards) the new search. Even when I edited the theme code to not show anything, it had no effect – so some sort of a cache on the server side is present.