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

Top 10 Entries

Question	What are "breadcrumbs," and how can I customize them?
Answer	Breadcrumbs are a navigation aid that shows the user their current location within the website's hierarchy. In Composr, breadcrumbs are customizable through an XML file. You can override default breadcrumbs using "match-keys" to target specific pages and define the desired breadcrumb structure. This allows you to adjust the breadcrumb trail to better match your website's organization. To edit, go to Admin Zone > Structure > Configure breadcrumb overrides.

Question	How can I control which panels are displayed on specific pages?
Answer	Panels are the areas around your main content area where you can place menus, blocks, and other dynamic elements. You can control panel visibility using display rules within your panel's Comcode: `{+START,IF,{$NEQ,{$PAGE},example_page_1,example_page_2,example_page_3}} ... panel content ... {+END}` This example prevents the panel from showing on pages named "example_page_1," "example_page_2," and "example_page_3."

Question	What is a "page-link," and how does it differ from a URL?
Answer	A page-link is a Composr-specific way to reference a page or screen within your website. It's a simplified, local representation of a URL, independent of the URL scheme you might be using. For example, the page-link `site:downloads:browse:10` points to the download category with ID 10 in the site zone. This page-link remains consistent even if your URL scheme changes the way URLs are structured. Page-links also do not consider monikers, so if a URL moniker changes, page-links will stay the same. This is a powerful feature as you can use the Comcode `[page="page-link"]Page title[/page] tag to generate URLs of local content. And these will always work regardless of URL scheme or moniker.`

Question	How do menus work in Composr, and can I customize them?
Answer	Composr has a flexible menu system that can be customized to your needs. Default Menu: Generated automatically from the Sitemap, reflecting the structure of your content. Editable Menus: You can create and fully customize these menus, adding links to specific content or external websites. Menus can be added to panels (sidebars, headers, footers) or embedded directly within Comcode pages. The menu editor provides tools for adding branches, setting captions, tooltips, and URLs, and even defining context-sensitive behavior using "match-keys."

Question	What are "zones" in Composr, and what are they used for?
Answer	Zones are like sub-sites within your Composr website. They provide a way to organize content and apply different settings, like permissions, themes, and navigation. Some default zones include: Welcome Zone: The initial landing page, often used for login/signup. Site Zone: Your main website content, with features for viewing, submitting, editing, and deleting content on the member level. Admin Zone: For site administrators to manage the website. Content Management Zone: Where content is added, edited, and deleted, typically by site staff. Forum Zone (if using Conversr): Houses the forum section of your site.

Question	What are the different ways to control access in Composr?
Answer	Composr offers a robust permission system with various methods for controlling access: Zones, Pages, and Categories: Control which usergroups can view specific zones, pages, and categories (permissions). Admin Zone > Security > Permissions Tree Editor, or on the UI for the Zone / Page / Category. Global Privileges: Define permissions for actions like using advanced Comcode or bypassing the word filter, applicable across the entire site. Admin Zone > Security > Global privileges Module/Page Overrides: Tailor privileges for particular content types by overriding them on the controlling module or page. Admin Zone > Security > Permissions Tree Editor [> Content permissions] Category Overrides: Modify privileges for specific categories, allowing fine-grained control over actions within those categories. Admin Zone > Security > Permissions Tree Editor Match-key Permissions: Implement ad-hoc access control based on specific match-keys, offering flexibility beyond traditional permission structures. Admin Zone > Security > Match-key page restrictions

Question	What happens when I add a new usergroup to a third-party forum integrated with Composr?
Answer	If you are not using Conversr as your forum, Composr won't automatically assign any permissions to the new usergroup. To rectify this, you can use the "Absorb usergroup-permissions" feature in the Admin Zone. This tool allows you to copy the permissions from an existing usergroup to the newly created one, ensuring consistent access and functionality.

Question	What are some security considerations regarding super-moderators and super-administrators?
Answer	While super-moderators have extensive access to manage your site, certain sensitive privileges are reserved for super-administrators. This includes the ability to impersonate other users, execute arbitrary code, and view private content. These restrictions help prevent potential privilege escalation and ensure the overall security of your website. Exercise caution when granting super-moderator status and trust only reliable individuals.

Question	What are some useful tools for debugging permission issues?
Answer	Composr provides a couple of tools to help pinpoint permission problems: FirePHP: This browser add-on allows you to view detailed logs of permission checks performed by Composr. By analyzing these logs, you can identify which checks are failing and adjust your settings accordingly. Permission Check Logging: Enable logging of failed permission checks to a file (data_custom/permission_checks.log). This provides a persistent record of permission issues that you can review and troubleshoot.

Question	How can I test if my permission settings are working correctly?
Answer	Composr's "SU" feature allows administrators to temporarily assume the identity of another user, enabling you to experience the site as they would. Simply enter the desired username in the "SU" box in the footer. You can also use "Guest" to browse as an unauthenticated visitor. Remember that using "SU" doesn't accurately reflect online status and retains administrator access to sensitive areas.

Statistics

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