SOLVED: Filter: indexing/saving isn't possible with huge number of posts

  1. Filter indexing does not work on a site with a large number of records. After indexing is enabled, it freezes and does not complete.

  2. When the applied filters are completely reset or canceled, all products from the database are displayed in the cycle on the taxonomy term page. To display the products of the term correctly, you need to reload the page.

These issues were in beta and remained stable. I waited a very long time for the filters to finally work properly, but unfortunately, this did not happen again :roll_eyes:

2 Likes

The filter is still in experimental.

If you read the most recent changelog you’ll see there’s been no change with it as of yet.

Hi Evgeniy & Chris - first of all: I have deleted all comments that are not bug-report-relevant, as they are not helpful to anyone. Thanks for your understanding.

To the actual problems: As Chris said, the feature is still experimental, and we are continuously trying to improve it and solve bugs.

  1. What exactly does “huge number of records” mean? Currently, the query filter index does not have any logic to handle the indexing process in batch, which can probably lead to a “freeze”. But what number are we talking about?
  2. Should already be solved… :thinking:

Please send temporary login credentials, information on where we can see the issue, and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.

Best regards,
timmse

1 Like

Screenshot_2

There are now more than 120,000 records (products) in the database. Indexing filters just freezes on such a site. If there is a bricks filter in the template, then because of it, the template cannot be saved, because indexing starts every time it is saved.

  1. It would be nice to make mandatory indexing of filters in the template optional. Update always or only if necessary.
  2. When working with a large number of entries in the indexing of filters, you need to divide them into separate packages in order to avoid a time limit on waiting for script execution.

Hi guys,
Sorry for the late reply. We have added the issue to the bug tracker and are working on a solution.

2 Likes

Hi @parktechno ,

We got a potential fix for filter index hang issue.

Do you have a cloned site for us to test the fix?

If so, please send it to our support email.

Thank you!

Regards,
Jenn

Hi guys,

We’ve implemented this improvement in Bricks 1.10, now available as a one-click update in your WordPress Dashboard.
You can see the full changelog here: Bricks 1.10 Changelog – Bricks

Please let us know if you are still experiencing issues.

Best regards,
M

On the third day, indexing on the site looks like this.

Hi @parktechno ,

Please may I know does the progress runs if you keeps opening this tab?

Does the normal WP Cron on your website work?

Regards,
Jenn

Greetings!

No. Indexing has stopped and is no longer restarted when the page is opened.

WP Cron is running. It is disabled on the site and runs through the server Cron every second.

define( 'DISABLE_WP_CRON', true );

* * * * * wget -O /dev/null -t 1 -q 'https://site.url/wp-cron.php'

If in this case, please provide a temp admin access to help@bricksbuilder.io and include this forum thread URL for me to investigate