Menu Close

Blocksify Pro Docs

Loop Filter troubleshooting

Blocksify Pro Loop Filter troubleshooting helps restore counts, facets, filtered URLs, index jobs, results, and swatches.

Counts are missing or stale

Totals may be absent or trail the Target Loop. Results remain current because Blocksify Pro hides counts when its prepared information is unavailable.

  1. Go to Blocksify → Dashboard → Settings → Loop Filter and confirm Indexing is Enabled.
  2. Check Pending jobs, Processing, Progress, and Lock.
  3. Click Run jobs now, reload the panel, and confirm that progress advances.
  4. After a large import, click Rebuild index. See Manage the Loop Filter index for recovery controls.
The Loop Filter Status panel shows indexing enabled, pending and processing jobs, build progress, and a free lock.

A zero beside an available choice can be valid: it means the choice has no matches alongside the visitor’s other active facets.

A facet is greyed out or disabled

An unusable facet is marked Hidden and omitted from the published page. A protected field shows: “This facet will not appear on the site: the field is protected and cannot be exposed publicly.”

For other problems, the editor adds one of these exact reason fragments after “This facet will not appear on the site:”

  • “this field type cannot be used as a filter”
  • “its data source does not apply to this loop’s post type”
  • “its data source is not available for this loop”
  • “the filter is not bound to a published loop yet”
The complete Reference facet popover shows its protected custom field marked Hidden with the warning that it cannot be exposed publicly.
  1. Confirm Target Loop points to a published Content Loop.
  2. Choose a field whose type and data source apply to that loop’s post type.
  3. For custom meta, use a public field and its exact key. Update the page and confirm Hidden is gone.

Filtered URLs show unfiltered results

A cache or CDN may ignore or remove query strings, then serve one unfiltered page for every address. See Filter URLs, shareable links and the results index.

  1. Confirm the facet keys remain in the address after loading.
  2. Purge page, object, and CDN caches.
  3. Vary the cache by query string or exclude the listing page. Include long cl_ keys and aliases in the cache key.
  4. Retest the address in a private window.

Two facets fight over the same URL word

An alias must be unique site-wide. A clash marks the facet row Long URL and shows: “URL alias unavailable (already in use by another filter on this site) — this facet uses the long URL form (?cl_…). Pick a different alias.”

The Loop Filter facet popover shows a URL alias collision warning beneath the location alias field and says the facet will use the long URL form.
  1. Open Data and click Unlock alias if needed.
  2. Enter another URL alias, or enable Namespaced URL.
  3. Click Update and test new and shared addresses.

For different fields sharing one slug, “Slug used by another facet on a different field” appears. Give each field its own URL slug.

The index will not build or jobs stay pending

Jobs can remain pending when WordPress scheduled tasks are disabled, local requests are blocked, or hosting security prevents background work.

  1. Click Run jobs now, then reload the panel.
  2. If Progress advances, let scheduled tasks continue.
  3. Otherwise, ask the host to allow scheduled events and local requests; check security, maintenance, and basic-auth rules.
  4. If Lock stays Held, stale, click Clear stuck jobs, then Rebuild index.

Results are empty after filtering

Active facets narrow the results together: a post must match every active facet, not just one. The selected field may also have no values in the Target Loop.

  1. Click Reset, then apply facets one at a time.
  2. Confirm source entries have saved values for the selected field.
  3. Verify that the field belongs to the Target Loop’s post type.
  4. Within one checkbox facet, choose Match → Any unless every value is required.

The Swatches option does not appear

Swatches needs a taxonomy with a configured, supported colour or image source. WooCommerce alone does not make every attribute visual.

  1. Confirm the facet uses a product attribute taxonomy.
  2. Configure the attribute in a supported visual setup and add term colours or images.
  3. Reload the editor and select Display → Swatches. See Facet displays and swatches.

Was this helpful?

0

Updated