v3.2.0

[apata]

This release

• adds "Limit to segment" feature for shared links
• fixes a bug requesting tracker scripts in v3.1.0 (issue 5901)
• fixes Clickhouse low-memory settings that weren't actually applied (Fix low resources settings for Clickhouse community-edition#265)
• ...contains a few other fixes and changes, full details below

Upgrade

Checkout the branch plausible/community-edition:v3.2.0. Needed because Clickhouse profile settings in the community-edition repository have changed.

_console

$ git fetch origin v3.2.0:v3.2.0
$ git checkout v3.2.0

Re-apply any local changes to tracked files in the repository. If all configuration changes were in .env and compose.override.yml, this step isn't necessary.

_console

$ docker compose up -d

This will boot up the new version of the app.

Changelog

Added

• A visitor percentage breakdown is now shown on all reports, both on the dashboard and in the detailed breakdown
• Shared links can now be limited to a particular segment of the data

Changed

• Segment filters are visible to anyone who can view the dashboard with that segment applied, including personal segments on public dashboards

Fixed

• To make internal stats API requests for password-protected shared links, shared link auth cookie must be set in the requests
• Fixed issue with site guests in Editor role and team members in Editor role not being able to change the domain of site
• Fixed direct dashboard links that use legacy dashboard filters containing URL encoded special characters (e.g. character ê in the legacy filter ?page=%C3%AA)
• Fix bug with tracker script config cache that made requests for certain cached scripts give error 500

---

This discussion was created from the release v3.2.0.

[Olakeen]

Hello, I'm not sure I understand how to upgrade.
Is it no longer necessary to modify compose.yml with image: ghcr.io/plausible/community-edition:v3.2.0 ?

[apata]

Hi, @Olakeen! It's necessary to modify it, but 3.2.0 fixes also a bug with the Clickhouse database settings, so there are other changes as well in the compose file and a new support file. You can get all of these by checking out / downloading the branch v3.2.0 of the repository plausible/community-edition.

[apata]

If you're not interested in the other changes, you can just update the image name, as for previous releases. I suggest to give the other changes a try though. Apparently some of the settings that make Clickhouse work well with low resources weren't actually applied in previous versions.

[Olakeen]

Okay, thank you for clarifying that 👍.

[paskal]

I am happy claude code is around to read through the notes and update the configs, it was a bit tricky: paskal/terrty@13134b8

[SethFalco]

Just a note for others. I upgraded from v3.0.1 to v3.2.0 and it unfortunately prevented me from logging in. I'm not sure what went wrong, but an error would occur during 2FA! 😨

  plausible-1            | Server: 127.0.0.1:8194 (http)
  plausible-1            | Request: POST /2fa/verify
  plausible-1            | ** (exit) an exception was raised:
  plausible-1            |     ** (ArgumentError) errors were found at the given arguments:
  plausible-1            |
  plausible-1            |   * 1st argument: not an iodata term
  plausible-1            |
  plausible-1            |         :erlang.iolist_to_binary(:error)
  plausible-1            |         (crypto 5.5.3) crypto.erl:1202: :crypto.mac/4
  plausible-1            |         (nimble_totp 1.0.0) lib/nimble_totp.ex:173: NimbleTOTP.verification_code/3
  plausible-1            |         (nimble_totp 1.0.0) lib/nimble_totp.ex:241: NimbleTOTP.valid?/3
  plausible-1            |         (plausible 0.0.1) lib/plausible/auth/totp.ex:325: Plausible.Auth.TOTP.do_validate_code/3
  plausible-1            |         (plausible 0.0.1) lib/plausible_web/controllers/auth_controller.ex:388: PlausibleWeb.AuthController.verify_2fa/2
  plausible-1            |         (plausible 0.0.1) lib/plausible_web/controllers/auth_controller.ex:1: PlausibleWeb.AuthController.action/2
  plausible-1            |         (plausible 0.0.1) lib/plausible_web/controllers/auth_controller.ex:1: PlausibleWeb.AuthController.phoenix_controller_pipeline/2

I downgraded Plausible and had the same issue. I was no longer able to login even on the original version. 😨 😨

To resolve this, I kept Plausible running on the old version, then got a psql shell:

docker compose exec plausible_db psql -U postgres

Then in PSQL:

\c plausible_db
UPDATE users SET totp_secret = NULL, totp_enabled = false, totp_last_used_at = NULL WHERE email = 'seth@falco.fun';

Then exited the shell, and upgraded the Plausible server again, and all was fine. I was also able to re-enable 2FA just fine as well. 👍