Contributors: A-Z Index

A

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

Top 10 Entries

Question What are some of the default endpoints available in the server-side API?
Answer Default endpoints cover various functionalities, including:
  • Account: join, login, lost_password, setup_push_notifications
  • Misc: contact_us
  • Content: commandr_fs

Specific details on parameters and response data for each endpoint can be found in the documentation.
Question How does authentication work with the server-side API?
Answer Authentication is handled automatically using cookies, similar to regular website requests. If cookies are not feasible, the response parameters device_auth_member_id_cn/device_auth_pass_hashed_cn/device_auth_member_id_vl/device_auth_pass_hashed_vl from the login endpoint can be resent as POST parameters in subsequent requests.
Question How do I access the server-side API for my mobile app?
Answer The server-side API can be accessed via HTTP calls to http://yourbaseurl/data/endpoint.php. Results are returned in JSON format. The API utilizes endpoints with a 'hook' name and a 'hook type' categorization. Both REST-style and GET-parameter style requests are supported, with the latter recommended for simplicity.
Question What is the purpose of the Composr Mobile SDK Toolkit?
Answer The Toolkit, part of the composr_mobile_sdk addon, aids in mirroring Composr website resources into a mobile app. It includes tools for generating iOS/Android string resources from language files and exporting theme images in a directory structure suitable for iOS/Android app image assets.
Question How can I obtain Composr Mobile SDK?
Answer The iOS/Android SDK can be found on GitLab at: Composr ecosystem / Composr Mobile SDK · GitLab.

To connect to a Composr site, you will need to install the composr_mobile_sdk addon, which is not bundled. This addon provides scripting to generate app assets from the Composr site.
Question What is Composr Mobile SDK?
Answer Composr Mobile SDK (CMS SDK) is a toolkit designed for experienced iOS and Android developers to build mobile apps that integrate with a Composr-powered website. It offers both Composr-specific integrations and a collection of standalone utilities for building apps, providing a common base between iOS and Android akin to the PHP and Composr APIs, enabling easier code porting while maintaining a native experience.
Question What is the Composr maintenance policy?
Answer Composr follows a rolling release model. This means:
  • New major/minor versions are released as they are ready.
  • Patch releases, primarily containing bug fixes, are only released for the latest supported major/minor version branch.
Users are responsible for staying updated to the latest release or applying necessary hotfixes.

This policy allows developers to focus resources on the latest versions and encourages users to leverage the ongoing improvements. You can find the release status on the Composr maintenance status page.
Question What are the general courtesy guidelines for interacting with the Composr community?
Answer
  • Understand that Composr is developed and maintained by volunteers who dedicate their time to the project.
  • Refrain from demanding free support or expecting developers to work on specific schedules.
  • Avoid placing undue pressure on volunteers or pushing them beyond their capacity.
  • Approach the community with respect and a collaborative spirit.
  • Remember that offering financial sponsorship for desired features can accelerate development.
Question How can I provide design feedback for Composr?
Answer Constructive design feedback is valuable. To provide effective feedback:
  • Be specific and detailed. Identify particular issues and provide clear examples.
  • Offer solutions. Suggest improvements or provide mockups demonstrating your ideas.
  • Avoid vague statements. General comments like "it looks dated" are unhelpful.
  • Understand design constraints. Consider factors like modularity, generality, feature density, compatibility, performance, and the subjective nature of design.
Directly reporting specific design bugs to the tracker or redesigning Composr interfaces yourself are excellent ways to contribute.
Question How do I make a feature suggestion for Composr?
Answer You can suggest features through the tracker or the Report Issue Wizard. When making a suggestion:
  • Be comprehensive and self-contained. Provide all necessary information and context for the developers to understand your suggestion.
  • Focus on widely beneficial features. Esoteric suggestions are less likely to be implemented.
  • Understand developer constraints. Feature development depends on factors like developer availability, funding, and project strategy.
  • Consider sponsoring features. Financial contributions can prioritize the development of desired features as it affords developers the time to implement it.