Skip to content

5.5.0
Compare
Choose a tag to compare
@Schlaefer Schlaefer released this 16 Nov 20:44
· 81 commits to master since this release
5.5.0
e849bf1

Changes

  • ＋ Adds CHANGELOG.md to keep track of changes
  • ＋ Rewritten and expanded permission system:
    • ＋ New, more fine grained permissions
    • ＋ Permissions are configurable
    • ＋ New role "Owner"
  • Uploader:
    • ＋ Shows progress-bar when uploading a file
    • ＋ Shows speed, time remaining and file size when uploading a file
    • ＋ Adds button for canceling the current file-upload
    • ＋ Cancel a running upload if the upload-dialog is closed
    • ＋ Checks that file with same name isn't uploaded before upload starts
    • ＋ Improved responsive layout
  • ✓ Fixes user's can't log-out if forum is installed in a subdirectory
  • ✓ Fixes login redirect issues if forum is installed in a subdirecotry
  • Δ Improves performance of background task runner
  • Internal code changes:
    • Δ Increases phpstan static code analysis from level 3 to 4
    • Δ Changes passing of current-user throughout the app
    • Δ Updates aura/di from 2.x to 4.x

Update Notes

Extended Permission System

Saito 5.0.0 introduced a new permission system which was rewritten and considerably extended in this release.

Configuration

The configuration is exposed at config/permissions.php now.

Want to allow moderators to contact a user no matter the user's contact-settings? You can do that. Want to disable new registrations? You can do that. Want to allow users to change their email-address? You can do that. And a lot more.

Permissions are intended to offer flexibility by tweaking the exiting forum behavior to your needs. While possible it is not recommended to start a brand new permission-configuration from scratch.

If you make changes in config/permissions.php don't forget to carry them over if you update to new releases in the future.

The Owner Account

This update introduces a new user-role Owner. The following changes apply to the default configuration:

  • On new installations the first account created is an Owner instead of an Administrator
  • The Owner lives "above" the Administrator inheriting all their rights
  • The "lower" roles are not allowed to change the role, block or delete an Owner
  • Only an Owner can promote (or demote) a user to Administrator or Owner

The update is not going to change accounts on existing installations and, because this is the whole point, it isn't possible to promote an account to Owner from an Administrator account. To promote an user on an existing installation execute manually in the database:

UPDATE users SET user_type='owner' WHERE username='TheUserName';
"Lock User" Setting

The setting for enabling user-locking is removed from the admin-backend and controlled by permissions now. The default behavior is unchanged: moderators may lock, locking status is visible to every user.

Assets 3
Loading