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.

• CAPTCHA: A visual or audio test that humans can easily pass but bots struggle with. This helps prevent automated spam submissions.
• Heuristics: If Composr thinks an action is spam based off of configurable criteria, it can either flag the content for validation, block the attempt, or ban the IP address outright.
• Public block lists: Composr can utilize the Stop Forum Spam system or other block list systems to identify and block known spammers based on IP addresses, usernames, and email addresses.
• Link posting restrictions: Disallowing links in member profiles for users with no posts and adding "nofollow" attributes to links discourages spammers seeking backlinks.
• Black hole fields: Hidden form fields that should remain empty. Bots often fill these in, allowing Composr to identify them.
• Project Honey Pot integration: A system that places hidden links on pages, attracting and identifying spam bots.
• Content/post reporting: Users can report spam, enabling staff to take action.
• Guest posting limitations: Restricting guest permissions raises the bar for spammers.
• Advanced techniques: Developer addons like "antispam_question" or probation systems provide additional layers of protection.

• Generating menus.
• Creating the user-facing sitemap page.
• Generating the XML Sitemap for search engines.
• Providing a visual representation of your website structure in the Sitemap editor and Permissions tree editor.

• /pg/ (e.g., /pg/home)
• .htm (e.g., /home.htm)
• Simple unadorned URLs (e.g., /home)

• Improved user experience with more readable URLs.
• Potential SEO benefits, as some believe search engines favor cleaner URLs.
• Easier sharing on social media and other platforms.