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)
Hello bricks team,
When we add a filter element, a record is added to the bricks_filters_element table in the database. But if we delete the element, the record remains and is not deleted. While this isn’t something that would easily impact performance, but it doesn’t seem to work as expected.
Hi Victor,
Thanks so much for your report!
The table is updated as soon as you insert a new filter element. As far as I can see, it is not the case that all filter elements ever created remain as data corpses. So overall, no problem or bug 
Best regards,
timmse
Hi @timmse,
Yes, you are right. After adding a new filter on the same page, the database is updated. But if we don’t add a new filter, its record remains in the database, right?
For example, we use a filter on a page, but later we decide not to do it and delete the filter. After that, a filter record for that page will remain in the database.
Aaah, you’re right 
I’ve added it to the bug tracker.
Hi Victor,
We fixed this issue in Bricks 2.0 alpha, now available as a manual download in your account (see changelog).
Please let us know if you are still experiencing issues.
As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.