[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Without custom coding I don’t think it’s possible. Filter plugins/solutions work independently, unless they are specifically coded in a way to affect each other – which I have never seen before in any plugin, so I don’t know if it’s worth trying without customization.

If you need professional help, I recommend wpkraken, they did custom jobs for our plugin before, they might know a solution for a fair price.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi Matt,

In that case the layout of the results is controlled by Elementor itself, so it’s up to what Elementor can display.
Try editing the results template in Elementor, it is very likely that it is possible to change the layout.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

1. I’m afraid not yet. It will be added in a future release after the front-end options are reworked. It will take some time.
2. I don’t think they work together. Usually combining 2 filters result in either one or the other results to apply. They will probably work without conflict, but the results from Ajax Search Pro filter will not be applied to the other filter and vice versa – they work independently.

[Ernest Marcinko]

Hi,

If I have the plugin from Envato installed, and I over write it with the lifetime license I recently bought, will it hold all the old plugins settings? Other than the licensing part etc.

Everything will stay the same, the plugin files are actually the same on both sources, the license code is the only difference 🙂

Thank you for the kind words, I do my best. The Divi blog module filtering was a test for a much simpler filter integration system, so GeneratePress query loop is next on the list for the 4.27.1 milestone. It look possible from what I can tell so far.

[Ernest Marcinko]

Hi!

I’m afraid that is not possible to replace via a hook, I just checked, and it is unfortunately hard-coded into the header.php and the theme-header.php files.

The only way to make a change there is to edit those files directly, but that’s usually not a good idea, unless you are using a child theme. I managed to repace it, by finding this code in the header.php file in the Divi theme directory (around line 332):

<?php if ( $show_search_icon ) : ?>
<div class="et_search_outer">
	<div class="container et_search_form_container">
		<form role="search" method="get" class="et-search-form" action="<?php echo esc_url( home_url( '/' ) ); ?>">
		<?php
			printf( '<input type="search" class="et-search-field" placeholder="%1$s" value="%2$s" name="s" title="%3$s" />',
				esc_attr__( 'Search &hellip;', 'Divi' ),
				get_search_query(),
				esc_attr__( 'Search for:', 'Divi' )
			);

			/**
			 * Fires inside the search form element, just before its closing tag.
			 *
			 * @since ??
			 */
			do_action( 'et_search_form_fields' );
		?>
		</form>
		<span class="et_close_search_field"></span>
	</div>
</div>
<?php endif; ?>

And replacing it with:

<?php if ( $show_search_icon ) : ?>
<div class="et_search_outer">
	<div class="container et_search_form_container">
	
		<?php echo do_shortcode('[wd_asp id=1]'); ?>
		
		<span class="et_close_search_field"></span>
	</div>
</div>
<?php endif; ?>

But this is very far from a permanent solution, if the form were wrapped in a hook, that would make it possible to auto-replace. This still works if you use a child theme, but please mind that an update could cause issues, if they change the main theme header.php file structure.

The optimal solution would be to have hook in Divi to access the search form output. For example if the Divi header.php file search section would look like this:

<?php if ( $show_search_icon ) : ?>
<div class="et_search_outer">
	<div class="container et_search_form_container">
		<div class="container et_search_form_container">
			<?php ob_start(); ?>
			<form role="search" method="get" class="et-search-form" action="<?php echo esc_url( home_url( '/' ) ); ?>">
				<?php
				printf( '<input type="search" class="et-search-field" placeholder="%1$s" value="%2$s" name="s" title="%3$s" />',
					esc_attr__( 'Search &hellip;', 'Divi' ),
					get_search_query(),
					esc_attr__( 'Search for:', 'Divi' )
				);

				/**
				 * Fires inside the search form element, just before its closing tag.
				 *
				 * @since ??
				 */
				do_action( 'et_search_form_fields' );
				?>
			</form>
			<?php $header_search_form = ob_get_clean(); ?>
			<?php echo apply_filters('divi/header/search', $header_search_form); ?>
			<span class="et_close_search_field"></span>
		</div>
	</div>
</div>
<?php endif; ?>

Then a simple hook to ‘divi/header/search’ would do the trick permanently. If you want you can make a suggestion to them, although I don’t know how this will change once they update to divi 5. Maybe there is a hook planned already.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

Sure! I have logged in, and the issue was that the plugin was very outdated, almost 2 years old version was installed. I have updated to the latest and the issue is resolved – it was likely a bug that was solved previously.

[Author]

Posts