Original developer of ocPortal, former lead developer of Composr CMS

Masters degree in Computer Science from The University Of Sheffield

Undertaken work for over 15 FTSE-100 companies, as well as many small and mid-sized organisations. Includes a number of banks and major brands.

@gamerevolt

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

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.

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).

Versatile: You can strip down to a core system, or build up with 3rd-party addons.

Full API documentation

High coding standards: No PHP notices. Type-strict codebase. MVC framework.

Free online developer's guide book (in the tutorials)

Custom field filters: For example, restrict news posts to a minimum length.

Stack traces for easy debugging

Synchronise data between staging and live sites using Resource-fs

Breadcrumb overrides

Advanced banning: Set your own banning rules for different hack attack codes. Even create your own ban pages (e.g. to mimic law enforcement bans for spammers).

Code overrides: Implement modifications to the Composr code without directly editing the original code by creating _custom files. This makes upgrading much easier. Also supports contentious_overrides hooks and the override_api for more advanced overriding.

Many different hook types allowing for modifying or extending Composr without modifying or overriding the code.

Convert from other software: See our importing tutorial for a list of importers.

Use an existing member system: See our download page for a list of forum drivers.

Convert an HTML site into Composr pages

LDAP support for corporate networks (Conversr only)

HTTP authentication: Tie into an existing HTTP authentication-based login system (Conversr only)

Proxying system: Programmers can integrate any existing scripts using our sophisticated proxying system (which includes full cookie support).

Minimodules and miniblocks: Programmers can port existing PHP code into Composr itself without having to strictly conform it to Composr's framework