Contributors: A-Z Index

A

Name	Photograph	Title / Role	Contributions / Notes
Allen Ellis		Founder	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	View

C

Name	Photograph	Title / Role	Contributions / Notes
Chris Graham		Founder	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.	View
Chris Warburton		developer for ocProducts	Made some key contributions to ocPortal	View

H

Name	Photograph	Title / Role	Contributions / Notes
Haydn Maidment		project manager for ocProducts	None available	View

J

Name	Photograph	Title / Role	Contributions / Notes
Jim Davidson		contributor	written many tutorials via Arvixe	View

P

Name	Photograph	Title / Role	Contributions / Notes
Patrick Schmalstig		Lead Developer	Joined Chris Graham behind the scenes in the development of Composr CMS in 2016. Took on the lead developer role in 2023 when Chris Graham stepped back to attend to his new lifestyle changes. Spearheaded the development of Composr CMS v11 and the new website, Composr.app. Formed the company PDStig, LLC to take on professional support and development for Composr CMS users especially after the discontinuation of ocProducts, Ltd.	View
Philip Withnall		Early Developer	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	View

R

Name	Photograph	Title / Role	Contributions / Notes
Robert Goacher		Founder	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	View

S

Name	Photograph	Title / Role	Contributions / Notes
Steve Jarvis		project manager for ocProducts	Wrote many tutorials via Arvixe	View

Newest 10 Entries

Question	What are redirects and how can I use them for subsites?
Answer	Redirects let you create custom URL paths that point to different zones and pages within your site. Examples: 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. Go to Admin Zone > Structure > Redirects.

Question	What are virtual roots and how do I use them?
Answer	Virtual roots let you make a sub-category within a Composr module (e.g., downloads) appear as the top-level category. This is useful for creating separate "databases" of content for different subcommunities. To create a virtual root: 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.

Question	Can I have subsites and subcommunities within a single Composr installation?
Answer	Yes, Composr offers various tools to create subsites and subcommunities within a single installation: 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.

Question	What is the difference between a central site and a satellite site in an M.S.N.?
Answer	The central site hosts the shared forum, member database, and netlink system. It is the core of your M.S.N. Satellite sites are the additional websites within your network. They connect to the central site for member information and forum access.

Question	What are the advantages and disadvantages of using an M.S.N.?
Answer	Advantages: 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. Disadvantages: Configuration and maintenance: Setting up and maintaining multiple sites can be more complex.

Question	What is a multi-site network (M.S.N.) in Composr?
Answer	An M.S.N. allows you to run multiple Composr websites (installations) that share a common forum and member database. It's ideal for website networks with shared communities but segmented content, staff, or branding. In essence, members who join one site automatically have accounts on all sites within the network.

Question	What are the key classes and utilities provided by Composr Mobile SDK?
Answer	CMS SDK provides several classes with utility functions mirroring PHP and Composr APIs, including: 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.

Question	How do I set up Composr Mobile SDK in my iOS and Android projects?
Answer	iOS (Xcode): 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. Android (Eclipse): 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.

Question	What are some key concepts related to mobile app development with Composr?
Answer	Essential concepts include: 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.

Question	What other approaches exist for mobile integration with Composr?
Answer	Other approaches, in various stages of development, include: 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.

Top 10 Entries

Question	What is rate limiting and how can I enable it in Composr?
Answer	Rate limiting prevents server overload by restricting the number of requests allowed from a single IP address within a specific timeframe. To enable Composr's built-in rate limiting, add the following to your _config.php file: Code (`PHP`) $SITE_INFO['rate_limiting'] = '1'; $SITE_INFO['rate_limit_time_window'] = '10'; $SITE_INFO['rate_limit_hits_per_window'] = '5'; This configuration limits each IP to 5 requests every 10 seconds. This feature generates soft errors early in the process before Composr fully loads.

Question	How can I reduce disk activity to improve performance?
Answer	If your hard disk is slow, you can implement the following settings in your _config.php file to minimize disk access: $SITE_INFO['disable_smart_decaching'] = '1'; $SITE_INFO['no_disk_sanity_checks'] = '1'; $SITE_INFO['hardcode_common_module_zones'] = '1'; $SITE_INFO['prefer_direct_code_call'] = '1'; $SITE_INFO['charset'] = 'utf-8'; $SITE_INFO['known_suexec'] = '1'; $SITE_INFO['dev_mode'] = '0'; $SITE_INFO['no_extra_logs'] = '1'; $SITE_INFO['no_extra_bots'] = '1'; $SITE_INFO['no_extra_closed_file'] = '1'; $SITE_INFO['no_installer_checks'] = '1'; $SITE_INFO['assume_full_mobile_support'] = '1'; $SITE_INFO['no_extra_mobiles'] = '1'; Note: These settings override default behaviors and may have unintended consequences. Use with caution.

Question	What is static caching and how do I enable it?
Answer	Static caching drastically improves performance by serving pre-generated pages to bots and guests. This works because these users typically don't require dynamic content. To enable it: Go to the Installation Options editor (`yourbaseurl/config_editor.php`). You will need your maintenance password. Activate the static cache option. Composr intelligently determines what to cache, and you can further control this via options within the Installation Options. Be aware that enabling static caching may disable eCommerce features for guests unless specifically configured.

Question	What are Composr caches and how do they improve website performance?
Answer	Composr utilizes various types of caches to enhance performance by storing pre-calculated results and reducing repetitive tasks. These caches include: Language cache: Eliminates the need to parse language files on each page load. Template cache: Avoids reparsing template files repeatedly. Comcode page cache & Comcode cache: Reduces the need to parse Comcode pages and general Comcode usage. Block cache: Caches blocks based on their parameters, minimizing execution. Theme image cache: Prevents redundant searches for theme images. Values caches: Stores calculated values like member post counts. Persistent cache: Keeps frequently used data in memory for faster access. Advanced admin cache: Allows admins to view cached pages while the server generates updates. Static cache: Serves static pages to bots and guests, bypassing much of the framework. Self learning cache: Optimizes resource loading by learning which resources each page requires.

Question	How can I troubleshoot notification problems?
Answer	If you're having issues with notifications, here are some troubleshooting steps: Check Email Logs: View the email log (Admin Zone > Audit > E-mail queue/log) to see what notifications have been sent. Use the SU Feature: Impersonate a member using the SU feature (described in the "Testing access and privileges" tutorial) to view their notification settings and confirm they are set up correctly. Enable Carbon-copy Email: Configure a "Carbon-copy e-mail address" in the configuration settings to receive copies of all outgoing emails, including notifications. This helps you monitor email delivery. Verify System Scheduler: Ensure the system scheduler is configured correctly if members are not receiving digest emails. Check Digest Settings: Confirm that "Enable digest notifications" is enabled in the Messages configuration settings. Review "Safety listing limit": If a notification has too many categories, members might not see the full selection tree. Adjust the "Safety listing limit" in the configuration settings if necessary.

Question	Can I control which notifications members receive?
Answer	Yes, you can control notification settings through two mechanisms: Notification Defaults: You can set default notification preferences for all members. You can enable or disable specific notifications and choose the delivery method (Admin Zone > Setup > Notification defaults). Notification Lock-down: You can force members to receive or prevent them from receiving certain notifications (Admin Zone > Setup > Notification lock-down). This allows you to enforce specific notification policies and manage email volume.

Question	What notification options are available to members?
Answer	Members can choose from a wide range of notifications, including: Content Updates: Notifications for new or updated content, such as news articles, forum posts, and gallery images. Private Messages: Alerts for new private messages received. Friend Requests: Notifications for new friend requests. Administrative Actions: Alerts for actions taken by site administrators, such as account approvals or content moderation decisions. Members can choose to receive notifications via: Email: Notifications sent directly to their email address. Digest Email: Combined summaries of activity sent in batched emails. This requires the system scheduler and the digest e-mails configuration option to be enabled. Private Topics: Notifications delivered as private forum topics. SMS: Notifications sent as text messages (requires configuration and incurs costs). Web Notifications: Real-time alerts displayed within the Composr interface.

Question	Can I share content like news and banners across the M.S.N.?
Answer	Yes, you can share news by placing it on the central site and using RSS blocks on satellite sites to display it. Banners can be shared by adding them to the central site and configuring satellite sites to use the central site's banner.php script.

Question	What should I consider when managing usergroups for subcommunities?
Answer	Rank ladders: Use the default rank ladder for main site ranks and secondary usergroups for subcommunity memberships. New member status: Set default usergroups for new members to grant them initial access while allowing removal if necessary. Leadership: Assign leaders to usergroups to allow members to manage subcommunities. Clubs: Consider using Clubs for member-driven subcommunities with their own forums.

Question	What are Composr Clubs and how are they useful for subcommunities?
Answer	Clubs are special usergroups in Conversr (Composr's forum system) designed for creating subcommunities. They come with their own dedicated forums and are managed by members, taking pressure off site staff. Key features: No special permissions by default, simplifying permission management. Members can join and leave like regular usergroups. Provide a dedicated forum for the club.

Statistics

Forum statistics:	45 topics, 14 posts, 2 members Our newest member is test