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	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	How can I customize Composr without modifying the core files?
Answer	Composr offers a robust override system. Instead of altering the original files, create a parallel structure within _custom directories. For example, to modify site/pages/modules/polls.php, place your customized version in site/pages/modules_custom/polls.php. The tutorials outline additional information on how to utilise overrides.

Question	What are the main components of the Composr framework?
Answer	Composr consists of: Modules: PHP files that provide related screens, forming the building blocks of addons. Comcode: Text files containing content written in a simplified markup language. HTML: Files containing standard HTML for web pages. Sources: PHP code files for the core API and functionality. Hooks: PHP files enabling addons to interact and extend each other's functionality. Blocks/Miniblocks: Reusable components for displaying dynamic content within pages. Themes: Folders containing images, CSS, and templates to define the look and feel. Language files: Files holding text strings for multilingual support.

Question	How can I embed third-party widgets into my Composr pages?
Answer	Composr supports embedding widgets from various websites, like Google Maps, Vimeo, and YouTube, by simply pasting the URL. For manually embedding widget code, you can paste it into the HTML source view of the WYSIWYG editor or within Comcode html tags if not using the WYSIWYG editor.

Question	What is the difference between blocks and boxes in Composr?
Answer	Boxes are visual elements that provide a container for content, while blocks are functional units that generate and display dynamic content. Although blocks often appear within boxes in the default templates, they are not inherently tied to any visual representation.

Question	Can I customize the appearance of blocks?
Answer	Yes, you can style blocks by editing the associated templates and CSS. Templates are typically named after the block they represent. For example, the main_news block uses the BLOCK_MAIN_NEWS.tpl template.

Question	How do I create custom filter forms for my content?
Answer	The main_content_filtering block can help you generate filter forms automatically. You can use it to create a default form and then customize the generated Filtercode string to refine the filtering options. Once satisfied, you can either continue using the block or extract the HTML and modify it further.

Question	Where can I use Filtercode and Selectcode in Composr?
Answer	Filtercode is supported in various blocks, such as main_multi_content, main_gallery_embed, and main_cc_embed. It's also actively used in modules like catalogues, downloads, galleries, members, and news. Selectcode is supported in blocks and Comcode tags that explicitly mention it, including the main_multi_content block and the if_in_group Comcode tag.

Question	What is the difference between Filtercode and Selectcode?
Answer	Filtercode is used for querying content based on properties and values, while Selectcode is used for directly specifying a list of IDs or categories to include or exclude. Filtercode offers more complex filtering options, while Selectcode is more straightforward for simple selections.

Question	How can I filter content in Composr?
Answer	Composr provides two filtering systems: Filtercode and Selectcode. Filtercode is used for selecting content based on defined filters, such as field values, ratings, or keywords. It utilizes a syntax of comparisons, separated by commas, where each comparison specifies a field and a matching condition. Selectcode is a simpler syntax for specifying a list of IDs or categories to include or exclude from the results. It uses a comma-separated list of match-specifier tokens, such as individual IDs, ranges, or wildcard characters.

Question	What are blocks in Composr and how can I use them?
Answer	Blocks are dynamic elements that can be inserted into Comcode pages to add interactive and data-bound functionality to your website. They are essentially reusable components that automatically generate content, such as recent forum posts or information about the logged-in user. You can add blocks to your pages using the block construction assistant, which allows you to select from a list of available blocks, set their parameters, preview them, and generate the necessary Comcode.

Statistics

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