v0.5.0 Pre-Release #2
Pre-release
Pre-release
DaneEveritt
released this
07 Oct 21:10
·
4262 commits
to 1.0-develop
since this release
v0.5.0-pre.2 (Bodacious Boreopterus)
This is still a highly unstable version of Pterodactyl Panel. Normal users should continue to use v0.4.1
until a stable v0.5.0
release is out. This release is primarily for beta testers to play with new features and report bugs.
This release requires [email protected]
.
Added
- Added support for file copying through the file manager. #127
- Creating new files and folders directly from the right-click dropdown menu in the file manager.
- Support for setting custom
user_id
when using the API to create users. - Support for creating a new server through the API by passing a user ID rather than an email.
- Passing
?daemon=true
flag to/api/servers/:id
will return the daemon stats as well as thedaemon_token
if using HTTPS. - Small check for current node status that shows up to the left of the name when viewing a listing of all nodes.
Changed
- Support for sub-folders within the
getJavascript()
route for servers. - ALL API routes previously returning paginated result sets, or result sets nested inside a descriptive block (e.g.
servers:
) have been changed to return a single array of all associated items. Please see the updated documentation for how this change might effect your API use. - API route for
/api/users/:id
now includes an array of all servers the user is set as the owner of.
Fixed
- File manager would do multiple up-down-up-down loading actions if you escaped renaming a file. Fixed the binding issue. #122
- File manager actions would not trigger properly if text in a row was used to right-click from.
- File manager rename field would not disappear when pressing the escape key in chrome. #121
- Fixes bug where server image assigned was not being saved to the database.
- Fixes instances where selecting auto-deploy would not hide the node selection dropdown.
- Fixes bug in auto-deployment that would throw a
ModelNotFoundException
if the location passed was not valid. Not normally an issue in the panel, but caused display issues for the API. - Updated Socket.io client file to version
1.5.0
to match the latest release. Correlates with setting hard dependencies in the Daemon.