Releases: elliotttate/beatsaver-laravel
Releases · elliotttate/beatsaver-laravel
V.1.1.3 ~ Hotfix 3
V.1.1.2 ~ Hotfix 2
Changes from v1.1.1
- fixed bpm counter while importing/parsing songs
V.1.1.1 ~ Hotfix 1
Changes from v1.1
- fixed broken song list for users
- added compatibility for migrations on old MySql / MariaDB versions
- added new log channel for production environments (LOG_CHANNEL=production)
- added the song hashes to the API responses
- added the ability to search for a song hash via API
- removed API throttling (for now)
V.1.1 ~ Access Token Management / Themes
changes from v1.0
IMPORTANT: all existing API tokens will be deleted if you update from v1.0
- Removed old votekey from the user table. All access tokens will now be saved in access_tokens
- A user can now have up to 4 access tokens and can chose between readonly and read/write tokens
- Fixed voting via API call (now also requires a read/write token)
- The layout for views has changed in order to allow others to create themes or ui improvements more easily
V.1.0 ~ Basic feature Release
Basic features are in place.
Changes from the original beatsaver
- IMPORTANT: the API for plugins like the song downloader has changed! Use the latest version.
- emails are now stored in plain text (due to internal system structure)
- your account/email must now be verified in order to upload new songs
- you can now change your email and password from the profile page
- added "My Songs" to the menu after you are logged in
- you can now click the username in any song listing to see all songs from this user
- you can now edit and update your songs (keep in mind editing something other than the name and description may result in a new leaderboard!)
- you can now up and down vote a song
- added og meta tags to a songs detail page ( posting a link to discord now automatically creates a preview)
- automatically post new song uploads to a discord channel