Releases: wintercms/web-installer
Releases · wintercms/web-installer
v1.0.0-beta3
Bug fixes
- Hot-fix to disable Composer scripts on installation (such as those in
post-update-cmd
). Some shared hosting environments will not allow sub-processes to be run within PHP scripts.
v1.0.0-beta2
Changes
- All API calls and file downloads now use
curl
to execute the request, which should resolve problems with SSL certificates and people who do not haveallow_url_fopen
enabled in their PHP configuration. - Increased the execution time limits of several installation steps that may take longer to complete.
- Added logging of installation into an
install.log
file. - The final database check is re-run automatically if the user edits the database configuration.
- Improved validation of configuration values.
- Required fields are now marked with a red dot in the label.
Bug fixes
- PostgreSQL and SQL Server now use
utf8
as the default charset, asutf8mb4
is MySQL only. - Fixed some potential pathing issues with temporary files and installation files on Windows.
- Fixed issue where installer would error out if the database username and/or password were empty.
v1.0.0-beta1
First beta release of v1.0.0 of the new and improved Winter CMS Web Installer.
Installation
- Prepare an empty directory on the web server that will host your Winter CMS installation. It can be a main domain, sub-domain or subfolder.
- Download the install.zip file in the asset list below into this folder.
- Unzip the downloaded ZIP file.
- Grant write permissions to all files and folders that were extracted.
- In your web browser, navigate to the URL pointing to that folder, and include
/install.html
at the end of the URL. - Follow the instructions given in the installer.
Note: The web installer will install a production version of Winter CMS that does not contain files necessary for development of Winter CMS itself, like unit tests or Composer files. Should you require these, please use one of the other installation methods.