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

Coded the chatroom, blogging support, the analytics system, and OcCLE (now Commandr)

Masters Degree in Computer Science degree from The University Of Cambridge

Other work has included helping out with Firefox, and ongoing work on GNOME

Original designer for ocPortal

Also conceived and coded the Theme Wizard and Point Store

Son of one of the early inventors of Internet protocols (Usenet, aka Internet newsgroups)

Token non-brit

Ran some of the early websites where ocPortal came from

Technically the original developer of ocPortal, in that he wrote the first few lines of code

Heavily involved in the feature design process

Hosted some of our early meet-ups

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 (@[email protected]) - LinuxRocks.Online

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.