Only force acceptance on new versions (functionality change?)

Created on 1 July 2025, 4 months ago

Problem/Motivation

Currently, any change to terms forces all users to re-accept, which isn't ideal for tiny changes like typo fixes. Users get potentially forced to re-accept identical terms just because someone fixed "teh" → "the".

The multilingual version/revision interface almost addresses this if you have multiple languages.

Steps to reproduce

1. Create Terms & Conditions
2. Have users accept them
3. Fix a typo and save
4. All users forced to re-accept despite no meaningful changes

Proposed resolution

Distinguish between:
- **Versions** - Significant changes requiring ALL users to re-accept
- **Revisions** - Minor fixes/language variants affecting only new users

**Changes:**
- Add checkbox: "Significant changes (require ALL users to re-accept)"
- Modify `legal_version_check()` to only compare versions, not revisions
- Simplify language/version UI to reduce confusion

This maintains audit trails while improving UX for minor updates.

Remaining tasks

- Add "significant changes" checkbox
- Update version checking logic
- Simplify multilingual interface
- Update documentation

User interface changes

- Add checkbox for controlling when re-acceptance is required
- Simplify language/version dropdowns
- Update help text

API changes

`legal_version_check()` would only check version matching, not revision matching. This is a breaking change.

Data model changes

None required - existing version/revision columns work as before.

Feature request
Status

Active

Version

4.0

Component

Code

Created by

🇬🇧United Kingdom littlepixiez

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @littlepixiez
  • Pipeline finished with Success
    4 months ago
    Total: 218s
    #536364
  • 🇬🇧United Kingdom robert castelo

    Good idea.

    Would be good to give an option between minor changes and material changes....

    Minor changes (e.g. fixing typos like “teh” to “the”): Usually considered non-material and do not require re-acceptance. They don’t affect the rights or obligations of the user, so courts typically won't view them as triggering the need for new consent.

    Material changes (e.g. changes to dispute resolution, data usage, fees, or cancellation rights): These can affect a user’s legal rights and obligations. In most jurisdictions, users must be notified and often required to affirmatively agree (e.g. by clicking “I Agree”) to remain bound by the new terms.

    I'll try and review at the weekend as part of a beta release for 4.0.1

Production build 0.71.5 2024