SOLVED: Query Filter indexing not working / stuck

Bugs
1

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Link to a page that illustrates this issue
Video: Short screen recording that illustrates this issue (free tool: jam.dev)

My Query Filter indexing is stuck.

Bricks > Settings > Query Filter > Regenerate filter index

I’m not using HTPP authentication and I tried with WP Cron enabled and disabled (cron job at server level). Nothing works.

None all my Filters work.

457173683_8288475514506515_8155918754601073148_n
457173683_8288475514506515_8155918754601073148_n1129Ă—348 26.7 KB

2

@Lucian ,

As per my email reply, we can replicate this bug when a filter element’s job already queued but removed before the completion of the job.

Working on a fix now.

Anyone encountering a similar issue can send admin credentials to help@bricksbuilder.io and include this forum thread URL as a reference.

I will apply a potential fix on your site.

Regards,
Jenn

1 Like
3

Hi guys,

We’ve fixed this issue in Bricks 1.10.2, now available as a one-click update in your WordPress Dashboard.

Please let us know if you are still experiencing issues.

You can see the full changelog here: Bricks 1.10.2 Changelog – Bricks

Best regards,
M

4

@Matej
Doesn’t seem solved, stuck on my wordpress instance, using local wp on my desktop.

image
image885Ă—599 63.6 KB

image
image1006Ă—332 10.1 KB

5

Hi @davig ,

Please place this PHP code on a Code element in a new blank page.

Enable Execute code and let use know what you see.

<?php
$url = add_query_arg(
	[
		'action' => 'bricks_background_index_job',
		'nonce'  => wp_create_nonce( 'bricks-nonce-indexer' ) 
	],
	admin_url( 'admin-ajax.php' )
);

$args = [
	'sslverify' => false,
	'body'      => '',
	'timeout'   => 10,
	'cookies'   => $_COOKIE,
];

$response = \Bricks\Helpers::remote_post( $url, $args );
if( is_wp_error( $response ) ) {
	echo '<pre>';
	var_dump( $response->get_error_message() );
	echo '</pre>';
} else {
	// Get the body of the response
  if ( isset( $response['response'] ) ) {
    echo '<pre>';
    var_dump( $response['response'] );
    echo '</pre>';
  } else {
     echo '<pre>';
    var_dump( $response );
    echo '</pre>';
  }
	
}

?>

Can you see something like this?
image

If not, your Local WP might have some settings causing wp_remote_post not to work.

Regards,
Jenn

WAIT: filter is indexing forever!
SOLVED: Wp_remote_post request failed
NO BUG: Stuck in "Indexing in Progress"
6

@itchycode

image

And now working
image

image
image826Ă—380 37.5 KB

Error - wp_remote_post request failed
7

Hi @davig ,

If the code returns message “OK”, means your local WP is not blocking the background task / wp_remote_post().
Your filter indexing not running should be able to solve by clicking the “Continue index job” button.

Regards,
Jenn

8

Hi guys,

We’ve improved this in Bricks 1.11 BETA, now available as a manual download (Bricks – Account)

Please let us know if you are still experiencing issues.

You can see the full changelog here: Bricks 1.11 Changelog – Bricks

As with any beta release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

Best regards,
Matej

9

image
image1348Ă—400 17.1 KB

Hi, I followed by playing the code

<?php
$url = add_query_arg(
	[
		'action' => 'bricks_background_index_job',
		'nonce'  => wp_create_nonce( 'bricks-nonce-indexer' ) 
	],
	admin_url( 'admin-ajax.php' )
);

$args = [
	'sslverify' => false,
	'body'      => '',
	'timeout'   => 10,
	'cookies'   => $_COOKIE,
];

$response = \Bricks\Helpers::remote_post( $url, $args );
if( is_wp_error( $response ) ) {
	echo '<pre>';
	var_dump( $response->get_error_message() );
	echo '</pre>';
} else {
	// Get the body of the response
  if ( isset( $response['response'] ) ) {
    echo '<pre>';
    var_dump( $response['response'] );
    echo '</pre>';
  } else {
     echo '<pre>';
    var_dump( $response );
    echo '</pre>';
  }
	
}

?>

But gotten error instead of OK message

10

When will this no longer be in Beta?

11

Hi,

this issue was resolved in Bricks 1.11 BETA, but we are now on 1.12.3, so it’s not in beta for a long time.

It was only in beta before 1.11 was released.

Best regards,
Matej

12

Oh right, duh :sweat_smile:. Thanks!

1 Like
13

Currently on stagingsite bricks 2.0.1 and filter index gets stuck. On live site it all works. Any thoughts or snippets for current version?

14

Same, but on a live site. Filter indexing stalls at 0%. I’ve done everything feasibly possible to my knowledge. Deactivated all security. Deactivated every plugin. Even tried on staging, absolutely nothing is working - it continues to sit at 0%.

15

By happenstance, I figured it out after hours of hair pulling. I had a security plugin installed and deactivated. Even though the plugin was deactivated, the htaccess file was still in effect. I figured this out when I couldn’t get to the login page in an incognito window. Once I disabled the file, filter indexing started working again. I hope this helps someone!

1 Like