Skip to content

Troubleshooting

Quick answers to the things people ask most.

  • Make sure the plugin is installed and activated under Extensions → My extensions, then clear the cache and let the administration rebuild.
  • The bar is added to the product, order and customer listings only. It is not shown on other admin pages.
  • If you collapsed it earlier, look for the small floating Show filter bar toggle at the edge — click it to bring the bar back.
  • The field list deliberately hides purely technical fields, internal identifiers, secrets, and admin-only records. Everyday catalogue and order fields are all present.
  • If the field belongs to a related record, look for it under the matching relation (drill in with the arrow) rather than at the top level.
  • If it is contributed by another plugin, enable Extension relations in the field list in the Options.
  • Reverse relations (fields that point back to the record) are off by default — enable Reverse relations in the field list in the Options if you need them.
  • Only one condition per field is kept — adding a second on the same field replaces the first. This is intentional; see Applying conditions.
  • If a condition matches one already in a saved group, it is merged into that group instead of added twice, and a short note explains it.
  • An unnamed group dissolves once its conditions change or leave the bar. Give a group a name to keep it.
  • Defaults only fill the empty starting state. If the bar already has conditions of your own when you open the listing, defaults do not override them.
  • Personal defaults take precedence over global ones — if you have your own, the shop-wide defaults do not apply to you.

A relative date filter shows the wrong range

Section titled “A relative date filter shows the wrong range”
  • Presets like Last 14 days are re-evaluated each time they apply, against the current date — that is by design. If you need a fixed window, pick explicit From and To dates from the calendar instead of a preset.

Global groups or defaults aren’t there for the team

Section titled “Global groups or defaults aren’t there for the team”
  • Publishing and removing global groups and global default filters requires configuration rights. A user without them can use shared groups but cannot create or delete them.
  • A user’s personal defaults always win over global ones, so a colleague with their own defaults will not see the shop-wide set.

Reach us at p2lab.eu. Note which listing you were on and what you clicked — it helps us reproduce the issue quickly.