• Enable mod_rewrite for URL Schemes or URL Redirects.
• Ensure AllowOverride All or at least AllowOverride Options FileInfo Limit is set in the server configuration.
• Recommended modules for optimal performance include mod_headers, mod_setenvif, mod_env, mod_deflate, and mod_filter.

• Don't disable default Feature Delegation for settings changed in the bundled web.config file.
• Install the URL Rewrite module, essential for URL Schemes, URL Redirects, and basic security.
• Configure IIS for additional mime-types if needed, as it doesn't serve unrecognized file types by default.

• GD2 (gd) with PNG and JPEG support
• MySQL extension (mysqli or pdo_mysql)
• XML extension (xml)
• Multibyte String (mbstring)
• cURL extension (curl)
• JSON support (usually available by default)
• Sodium (libsodium)
• ZIP extension (zip) if ZIP file support is needed

• posix extension for permission checks
• zlib extension for faster upgrades, compressed backups, and page compression
• ctype extension for slightly faster performance
• IMAP extension (imap) for managing newsletter bounces
• OpenSSL extension (openssl) for encrypted CPFs, DKIM, and SSL certificate expiry checks
• Pspell (pspell) or Enchant (enchant) extensions for spell checking

• File upload size limit of at least 5MB (or higher as needed)
• Maximum execution time of at least 30 seconds
• Memory limit of at least 128MB
• The installer will warn you if any critical functions have been disabled via disable_functions or other PHP modifications. Avoid web hosts that heavily restrict standard PHP functionality.

Absolutely! Frequent changes may be made to both bundled and non-bundled addons. Bundled addons will be updated via the upgrader. For non-bundled addons, you will have to update them through the addons management screen (Admin Zone > Structure > Addons). You will be informed which ones need updated.

Once version 11 reaches release candidate, we do not expect frequent updates to non-bundled addons anymore. But it is still good practice to check after every update.

Yes, for basic non-custom v10 sites. However, expect some issues to arise in the process. And please report those issues to the tracker.

For v10 sites with non-bundled addons or customisations, upgrading to v11 will likely break the site until you update the non-bundled addons or temporarily remove the customisations.

We aim to have the upgrader fully functional for a large majority of types of sites and for sites using non-bundled addons by the time version 11 reaches release candidate stage.

We do not recommend upgrading production v10 sites at this time until v11 reaches stable.

Yes (probably). Always remember especially during alpha and beta phases that things can break. Please make backups first. And let us know on the issue tracker if an issue occurs.
 

Note: You cannot upgrade from 11 alpha to 11 beta without first upgrading to 11.alpha4 (if you are not already on 11.alpha4).

As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site.

We will be releasing several beta versions in the beta phase.

We do not know when we will be able to release the first Release Candidate or stable versions at this time.

These plans are all subject to change without notice.