You are viewing the website for Composr CMS v11 alpha. This site is currently only a placeholder for v11 bleeding-edge releases, addons, and tutorials. Click here for the main Composr (v10) site, community, and issue tracker. This site will become the new Composr site when v11 reaches stable.

Version 11 alpha / beta

FAQs dealing with version 11 alpha and beta releases

Question	Why is there a separate website for version 11?
Answer	That is explained in detail in this news article on compo.sr including the migration plans and implications.

Question	What are the current release plans for version 11?
Answer	We plan to release a couple alpha versions of version 11 in March and April. Not all planned features will be finished yet. We plan to enter beta status in May 2024 where our focus will be switching to smashing bugs and stabilising the software. All planned features will be implemented fully by this point. We hope the upgrader will be working for non-custom v10 -> v11 sites by this point. We will be releasing several betas. We plan to release the first stable version of version 11 in July 2024. We hope everything is stable to our expectations and standards by this point especially the core software and upgrader. These plans are all subject to change without notice.

Question	Can I upgrade a previous version 11 release to a newer one using the upgrader?
Answer	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.

Question	Can I upgrade a version 10 site to version 11?
Answer	During the alpha stage, probably not. And we highly advise against trying this except on a test v10 site. The upgrader has not yet been fully reviewed and fixed to the point it would work correctly. During the beta stage, we hope to have the upgrader working to the point you can upgrade a basic version 10 site with only core / bundled addons installed to version 11. But you should still take backups before attempting this. 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.

Question	Should I update my non-bundled addons after updating to a newer release of version 11?
Answer	During the alpha and beta stages, 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 > Addon management). 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.

Question	Can I switch a v11 install from git over to using the releases from composr.app?
Answer	It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well. It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.

Question

Should I use the bleeding edge releases or the git repository?

Answer

That depends on several factors. Here are some pros and cons of each:

Bleeding edge releases	Git repository (v11 branch)
Easier to set up and use, and does not require knowledge of git	Harder to set up and use unless you are familiar with git; must routinely run the file integrity check, database upgrade tool, and check database schema tools in the upgrader after pulling
More stable, but less frequent updates	Less stable, but more frequent updates (almost daily!)
Only contains core code and addons unless you manually install non-bundled addons; non-bundled addons must be manually updated	Contains all core code and non-bundled addons; non-bundled addons are updated with pulls (though you will need to check file/database integrity often and check blocks/modules for available upgrades)
Ability to test the upgrader / upgrading between new v11 versions	Not able to effectively test the upgrader because git pull might load in and update new code early before the release is available
Always contains the latest files.bin and db_meta.bin because these are compiled with every release	Does not always contain the latest files.bin and db_meta.bin. Therefore, file and database integrity may report false-positives.
Intended for general user testing	Intended for developers / developer testing: * special run-time checks are enabled for extra debugging (if the .git directory exists in the install) * contains the unit test suite for running tests

Click here to access the git repository.