[Bug on plausible website] Error showing custom event goal

[bencresty]

Past Issues Searched

• [X] I have searched open and closed issues to make sure that the bug has not yet been reported

Issue is a Bug Report

• [X] This is a bug report and not a feature request, nor asking for self-hosted support

Describe the bug

Yesterday I opened this issue, but today I was unhappily surprised that somebody without even asking just closed this issue and converted this to a discussion while it's clearly a bug. It seems like the issue is not even read, because it's also suddenly placed in the 'selfhosting' category while it's obviously not about that, but a bug on the plausible website where we view the analytics and was working before.

Please fix this issue. We pay for Plausible every month and expect things to keep working, not suddenly break what was working for at least a year.

--

When clicking on a custom event an endless wait cursor appears and the data never shows. This was working fine in previous versions of Plausible. The code on our website didn't change and is not sending other data so something on the Plausible website did change.

Expected behavior

Plausible to keep working as before, not suddenly crash on a feature that worked in all previous versions for at least a year.

Screenshots

Environment

- OS: windows
- Browser: ms edge chromium for instance
- Browser Version: latest (99.0.1150.46 (Official build) (64-bit))

[metmarkosaric]

thanks for sharing @bencresty! if this is an issue with your Plausible account, then it's best to contact our customer support directly so we can take a look. if you prefer that we deal with it here on GitHub, please do share the website, goal name and account that this happens for and we will take a look. thanks!

[metmarkosaric]

hi @bencresty! do you still experience this issue?

[metmarkosaric]

we found a live example of this: https://plausible.io/elementary.io?country=US&country_name=United+States&goal=Download&props=%7B%22Version%22%3A%225.1.7%22%7D&period=all. looks like an issue with combining goal + prop + some visit filter. @RobertJoonas will hopefully take a look at it as part of the work he's doing on custom properties