• General: Private messages are often combined into private topics.
• phpBB: Usergroup configuration and HTML entities may require manual adjustments after import.
• vBulletin: Calendar recurrences, ratings (karma), and 'goes to coventry' are not imported perfectly. Attachments may need to be extracted directly from the live database due to potential corruption in SQL dumps.
• Simple Machine Forum: Banning features may not import perfectly due to differences in how Composr handles bans.

• Forum Software: Invision Board, MyBB, phpBB, Simple Machine Forum, vBulletin
• Content Management Systems: WordPress
• Special Importers: HTML website importer, Composr merge (for merging another Composr site)

• On the old server, ZIP the entire Composr directory.
• Download the ZIP file to your computer.
• Upload the ZIP file to the new server using SFTP/FTP.
• On the new server, unzip the file.

• On the old server, create an SQL dump of your database using the mysqldump command or phpMyAdmin.
• Download the SQL dump file.
• If your URL is changing, search and replace the old URL with the new one in the SQL dump file.
• Upload the SQL dump file to the new server.
• Restore the database on the new server using the mysql command or phpMyAdmin.

• File Permissions: After transferring files, ensure correct file permissions are set on the new server. You can use the fixperms.php script, the upgrader script, or manually adjust them.
• Configuration: If database settings are different on the new server, update the _config.php file or use the config_editor.php script to change the settings for both the site and forum databases.
• Base URL: If your URL has changed, update the base URL setting in the Installation Options editor (config_editor.php).
• Caches: Clear the block cache using the upgrader.php script.

• Direct reference by URL: Include the library's URL in your theme's HTML.
• Composr's JavaScript API: Use Composr's API for organized inclusion and potential future compatibility benefits.
• Manual integration: Directly include the library's code in appropriate template files.

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.