Users are discussing an issue with the topic filter in Discourse where filtering fails and becomes difficult to escape. Moin reports that once filtering fails, the sidebar link remembers the last filter applied, making it hard to try different criteria. chapoi confirms the issue and notes that a hard reload is needed to access the page again. awesomerobot identifies that the failure occurs when combining created-by and views- filters, providing a fix via a GitHub pull request. sam acknowledges the problem but suggests that 500 errors should not be left in the app, implying that the issue should be addressed at a higher level.
When filtering with the topic filter fails [1] it’s very difficult to get back to /filter to try filtering for different criteria because the link in the sidebar remembers what you filtered last.
I know filters are in general quite sticky (How do I remove the user filter at the groups page?), but in those cases you do not only get an error.
I am not sure why it fails in this case I tried an example from the documentation topic ↩︎
I can repro this @sam Need a hard reload to access the page again.
Also no idea why it fails tho.
Seems to fail when you combine created-by and views- specifically
I get a little more detail in logs locally: column reference "views" is ambiguous
This seems to fix it
https://github.com/discourse/discourse/pull/34033
(still hard to escape the error state when it happens tho)
I think this is generally fine cause 500s are not something we should ever leave in the app anyway.