v3.0.0 #5318
Unanswered
aerosol
asked this question in
Self-Hosted Support
v3.0.0
#5318
Replies: 1 comment 1 reply
-
|
v3.0.1 patch is in the works to address #5319 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Warning
Please use 3.0.1 patch that contains fix for #5319
The highlights of this release are:
Upgrade
Update the image used for
plausiblecompose.yml
and restart the containers
console
$ docker compose up -dThis will boot up the new version of the app.
Changelog
The following changes have been made since 2.1.5:
Added
exit_ratemetric in the dashboard Exit Pages > Details report28dand91davailable on both dashboard and in public APIcase_sensitive: falsemodifiers in Stats API V2 filters for case-insensitive searches.is notfor goals in dashboard Excluding goals in dashboard #4983["is", "segment", [<segment ID>]]filter in Stats APIengagementevent. These are reported assdandeinteger parameters to /api/event endpoint respectively. If you're using a custom proxy for plausible script, please ensure that these parameters are being passed forward.vparameter sent with each request.has_doneandhas_not_doneon the Stats API to allow filtering sessions by other events that have been completed.time_on_pagemetric is now graphable, sortable on the dashboard, and available in the Stats API and CSV and GA4 exports/importsRemoved
Changed
todayrather thanlast 28 days. On the next day, the default changes tolast 28 days.Tstill works for last 30 days.7dand30dperiods do not include today anymorefetchwith keepalive flag as default overXMLHttpRequest. This will ensure more reliable tracking. Reminder to usecompatscript variant if tracking Internet Explorer is required./api/healthhealtcheck is soft-deprecated in favour of separate/api/system/health/liveand/api/system/health/readychecks-instead of0for visit duration, scroll depth when hovering a data point with no visit dataengagementevents sent by plausible tracker script. We still use the old calculation methods for periods before the self-hosted instance was upgraded. Warnings are shown in the dashboard and API when legacy calculation methods are used.date_rangeshorthand options like30d,3mo.Fixed
visitors.csv(in dashboard CSV export) vs dashboard main graph reporting different results forvisitorsandvisitswith atime:minuteinterval./api/v2/queryno longer returns a 500 when querying percentage metric withoutvisitorsThis discussion was created from the release v3.0.0.
Beta Was this translation helpful? Give feedback.
All reactions