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	How are time zones handled in Composr statistics?
Answer	All times in Composr statistics are displayed according to the configured website time zone, regardless of visitor or user account time zones. While this is a limitation due to pre-computation, some graphs displaying hourly stats and country filtering offer insights into local times for manual analysis.

Question	What are the limitations of pre-computed statistics in Composr?
Answer	Pre-computed statistics introduce certain limitations: Filtering constraints: Limits filtering options to those incorporated in the data structure. Historical data limitation: To maintain site stability, statistics older than 31 days aren't pre-processed. This may lead to data gaps if the system scheduler malfunctions or statistical data is manually deleted.

Question	Why does Composr use pre-computed statistics?
Answer	Composr generates statistics from pre-computed data for several reasons: GDPR compliance: Prevents indefinite storage of raw (potentially personal) data while preserving historical statistics. Computational efficiency: Avoids real-time execution of complex calculations, ensuring optimal performance. Scalability: Handles vast amounts of data without performance degradation. Responsiveness: Enables quick and seamless statistics browsing and filtering. Data accessibility: Makes generated data readily available for other Composr components.

Question	What are KPIs and how are they used in Composr?
Answer	KPIs (Key Performance Indicators) are specific measurements selected for marketing analysis. In Composr, time-series graphs can be added as KPIs. They offer several benefits: Quick reference: Available on the Admin Zone dashboard staff checklist. Target setting: Allows setting targets against KPIs, visualized on graphs and in overview summaries. Notifications: Staff members receive regular notifications regarding target achievement status.

Question	How can I perform split testing in Composr?
Answer	Split testing in Composr involves combining tracking codes with events. The simplest approach utilizes Tempcode: Random tracking code: Choose a random tracking code from a set and activate it for the user session. Conditional output: Generate different content variations based on the active tracking code. Subsequently, you can analyze event success rates based on the assigned tracking codes, utilizing both inbuilt events and custom-created events.

Question	What is the purpose of tracking codes in Composr?
Answer	Tracking codes help you identify the sources driving user sessions to your website or associate specific split testing variations with users. Composr offers integrated referral tracking through various means: URL parameter: The _t URL parameter can contain any custom tracking code, automatically registered by the stats addon. Recommend addon: This addon automatically includes tracking codes for the referral source, referring member, and the referred page. Member joining: When a referred member joins, the referring member receives points and a friend request. Referrals addon: Allows manual tracking code input upon joining and facilitates a referrer reward system. Stats addon: Generates graphs of tracking codes, including conversion rate measurements. User lookup tool: Allows checking if a user accessed the site via a tracking code. Tempcode integration: Inject tracking codes into Tempcode using symbols like `{$SET_TRACKING_CODE,some code}` or `{$SPLIT_TEST,some code,some other code}`.

Question	What are the different ways to track events in Composr?
Answer	Composr offers various methods for tracking events: Inbuilt events: Automatically recorded for actions like form submissions, purchases, newsletter signups, etc. Tempcode symbol: Use the `{$LOG_STATS_EVENT,event}` symbol within your templates to track events when the template is displayed. JavaScript function: Employ the `$cms.statsEventTrack` JavaScript function to track events from within your JavaScript code. HTML data attribute: Add `data-click-stats-event-track="{ category: 'some event', nativeTracking: true }"` to HTML elements. This method acts as a wrapper for the JavaScript function. URL wrapping: Wrap URLs in links using the `{$STATS_TRACK_URL,URL,event}` symbol. This approach records events via a redirection script and doesn't rely on JavaScript. The JavaScript and HTML data attribute methods can also be integrated with Google Analytics events.

Question	How do I install geo-location data for Composr statistics?
Answer	Geo-location data installation is usually automatic during the Composr installation process. If not, you can manually install it by navigating to Admin Zone > Audit > Site statistics > Install geolocation data. This action will reschedule the installation task. If you don't see this option, the geo-location data is already installed.

Question	What are the key differences between Google Analytics and Composr statistics?
Answer	While there is some overlap, Composr statistics and Google Analytics are complementary tools. Google Analytics Pros: Offers sophisticated functionality for professional marketers. Integrates with other Google products like AdSense and Search Console. Provides insights based on Google's marketing data, such as visitor demographics. Google Analytics Cons: Limited to web visit data unless custom programming or complex configuration is implemented. Relies on JavaScript for tracking, which can be blocked by users. Uses tracking cookies, raising privacy concerns and potential GDPR compliance issues. Data is potentially sold to third-party data brokers or used for targeted advertising by Google. Closed-source platform. Composr Statistics Pros: Server-side tracking, independent of JavaScript and browser configurations. Contextual information and graphs for data beyond web visits (e.g., sales). Enhanced privacy as it only uses IP addresses, session IDs, and member IDs. Complete data control as it is hosted on your website. Open-source addon, fully customizable. Basic users may find Composr statistics sufficient, while expert marketers might prefer the power of Google Analytics.

Question	What tools and strategies can be used for staff training and development?
Answer	While Composr itself doesn't provide built-in training features, several approaches can be used for staff development: Documentation & Tutorials: Utilize the extensive Composr documentation and tutorials available online to familiarize staff with the platform's functionalities. Mentorship: Pair experienced staff with newcomers to provide guidance and support during the initial learning phase. Private Forums & Chat: Create dedicated communication channels where staff can exchange knowledge, ask questions, and share best practices. Regular Meetings: Conduct regular staff meetings to discuss updates, share information, and address any arising challenges. External Resources: Leverage external resources like online courses or workshops focused on relevant skills, such as content management or community moderation. By investing in ongoing staff training and development, communities can ensure their teams possess the necessary knowledge and skills to perform their roles effectively and contribute to the platform's overall success.

Statistics

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