No longer using PHAR. Due to problems in a small but not insignificant number of hosts, we decided to abandon PHAR as the delivery format for the Kickstart application. We are going back to the single PHP file approach we were using up until Kickstart 8. New features introduced in Kickstart 9, such as the improved support for S3v4, custom S3 endpoints, security precautions about file naming, password protection, and PHP 8.5 compatibility have of course been kept going into version 9.1.
Easier CLI usage. Running Kickstart from the command line no longer requires renaming the file to restore.php or setting a password. You can now run it directly as kickstart.php from the CLI without any preconditions.
Changelog
Bug fixes
[LOW] PHP 9 deprecations: remove E_STRICT usage
Miscellaneous changes
No longer using PHAR
Running Kickstart in CLI mode no longer requires renaming the file or setting a password
- Catch PHAR errors and display a helpful message pointing to the documentation instead of a cryptic PHP error
- Detect suboptimal PHP OPcache settings and display a warning with the recommended configuration changes
- [HIGH] Files uploaded via FTP in ASCII mode are silently corrupted; Kickstart now detects this and shows a clear, actionable error message instead of cryptic PHP errors
- [HIGH] Servers with open_basedir restrictions could not use PHAR support; Kickstart now detects this and automatically falls back to the non-PHAR extraction method
- S3 import: auto-detect region option with graceful fallback for S3-compatible services
- S3 import: comprehensive AWS region list with custom region option
- S3 import: custom endpoint support for third-party S3-compatible services
- S3 import: signature method selection (v2/v4) with region support
- [HIGH] S3 import feature was broken due to missing AKEEBAENGINE constant definition