• Sharing modules across zones: Create a redirect to make a module in one zone appear in another.
• Creating shortcuts: Use a redirect to point a short URL to a longer, more complex URL.
• Moving pages: Use a redirect to ensure old links still work after moving a page to a new location.

• Enable "Virtual root links" in the Admin Zone > Setup > Configuration > Feature options > Advanced.
• Navigate to the desired category while logged in as staff.
• Click the rightmost link in the breadcrumbs (it will be an anchor for virtual root creation).
• Use the resulting URL in your menus to link to the "virtualized" category.

• Zones: Create separate sections under different URLs with their own pages and content.
• Redirects: Make modules appear in different zones without actually moving them.
• Categories & Virtual Roots: Organize content like galleries, downloads, and catalogs into sub-trees that appear as separate entities.
• Usergroups & Permissions: Group members into subcommunities and control their access to specific content.
• Themes: Customize the look of different zones.

• Full control: You have complete control over each site's settings and content.
• Administrative separation: Managing staff and content for each site is more organized.
• Special M.S.N. features: Composr provides specific features like the 'netlink' system for easy navigation between network sites.

• Configuration and maintenance: Setting up and maintaining multiple sites can be more complex.

• CMS_Arrays: Array operations (e.g., implode, explode, list_to_map).
• CMS_Strings: String manipulation (e.g., strip_tags, html_entity_decode, strpos).
• CMS_Langs: Localization functions (e.g., do_lang).
• CMS_Preferences: User preference management.
• CMS_Timestamps: Timestamp functions (e.g., get_timezoned_date_time, time).
• CMS_HTTP: Web service interactions (e.g., rawurlencode, json_decode, http_get_contents).
• CMS_Users: User data and permission checks (e.g., has_page_access, is_staff).
• CMS_Flow: App flow control (e.g., access_denied, attach_message).
• CMS_Forms: Form building and management.
• CMS_Database: SQLite database access and manipulation.
• CMS_Notification: Push notification handling.
• CMSNetworkManager: Network request execution and response handling.

• Create a new project or open an existing one.
• Add a Prefix Header file (.pch) if you don't have one, following the provided instructions.
• Add required frameworks to your project's Build Phases.
• Add the CMS SDK to your project, then remove references to unwanted files.
• Set the header search path to the CMS SDK folder in build settings.
• Add a compiler option for the JsonKit library.
• Import CMS_SDK.h in your .pch file.

• Create a new project or open an existing one.
• Import CMS SDK into your workspace as an Android project.
• Ensure "Is Library" is checked in the CMS SDK's "Android" properties tab.
• Add CMS SDK as a dependent library in your project's properties.
• Clean and rebuild your project.

• SDK (Software Development Kit): An API implementation, typically as a library.
• API (Application Programming Interface): A set of rules for software interaction.
• JSON (JavaScript Object Notation): A common language for structured data transfer over REST.
• REST (Representational State Transfer): An architectural style for web services.
• Push notification: A notification sent to a mobile device.

• Tapatalk: A third-party forum app with an official Composr addon, offering a high-quality "out-of-the-box" Composr app experience.
• Further Composr Mobile SDK development: Plans and issues relating to the SDK's evolution can be found on the Composr tracker, driven by commercial projects and feature sponsorship.

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.