Open cottage opened 1 month ago
Running into the same problem. From a quick investigation, it seems to be because the query is being cached by a websiteId|propertyName
pair value, but does not include the eventName
in the cache key:
Same problem here. Is there a planned version for this fix? Kinda trivial thing but breaks the UX quite badly.
Describe the Bug
when two or more Properties of different events use the same name, only one property's data can be displayed. Clicking on another property with the same name does not have any effect.
Database
PostgreSQL
Relevant log output
No response
Which Umami version are you using? (if relevant)
v2.13.2
Which browser are you using? (if relevant)
chrome
How are you deploying your application? (if relevant)
manual install