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.

• Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug).
• Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication.
• Take backups before upgrading. This allows for easier recovery in case of problems.

• Check for duplicates: Make sure the bug hasn't already been reported.
• Report bugs individually: Each issue should be reported separately for better tracking and resolution.
• Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers.
• Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues.
• Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other

• Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness.
• Be respectful and patient: Remember that developers are volunteers and may not respond immediately.

• Site-wide Settings: You can configure default metadata for your entire site in the Admin Zone under Setup > Configuration > Site options.
• Content-Specific Settings: When adding or editing content like Comcode pages or news posts, Composr provides fields for customizing titles, descriptions, and keywords specific to that content under the "Metadata" section.
• Automatic Detection: Composr can automatically generate metadata by analyzing your content, but it's generally recommended to refine these suggestions manually for best results.