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

Name	Philip Withnall
Title / Role	Early Developer
Contributions / Notes	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

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

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

Name	Chris Graham
Photograph
Title / Role	Founder
Contributions / Notes	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.
Links	gameRevolt (@[email protected]) - LinuxRocks.Online

Website	Earth & Sky
Screenshot
Short Description	Earth & Sky is a Composr v11 gallery website showcasing natural photography by Mark Brunner.

Website	Saving Wallden
Screenshot
Short Description	This is an informational website for a Visual Pinball X game in development called "Saving Wallden". The site features the planned game rules, development news, and a download of the game as it is so far.

Website	PDStig, LLC
Screenshot
Short Description	This is an informational site / portfolio for PDStig, LLC, the company run by one of Composr's lead developers, Patrick Schmalstig.

Website	Composr CMS: Content management meets social media
Screenshot
Short Description	This is the main website for Composr CMS version 11. It runs the latest build of v11. Currently it is just a placeholder but will soon replace compo.sr when v11 becomes stable.

Question

Should I use the bleeding edge releases or the git repository?

Answer

That depends on several factors. Here are some pros and cons of each:

Bleeding edge releases	Git repository (v11 branch)
Easier to set up and use, and does not require knowledge of git	Harder to set up and use unless you are familiar with git; must routinely run the file integrity check, database upgrade tool, and check database schema tools in the upgrader after pulling
More stable, but less frequent updates	Less stable, but more frequent updates (almost daily!)
Only contains core code and addons unless you manually install non-bundled addons; non-bundled addons must be manually updated	Contains all core code and non-bundled addons; non-bundled addons are updated with pulls (though you will need to check file/database integrity often and check blocks/modules for available upgrades)
Ability to test the upgrader / upgrading between new v11 versions	Not able to effectively test the upgrader because git pull might load in and update new code early before the release is available
Always contains the latest files.bin and db_meta.bin because these are compiled with every release	Does not always contain the latest files.bin and db_meta.bin. Therefore, file and database integrity may report false-positives.
Intended for general user testing	Intended for developers / developer testing: * special run-time checks are enabled for extra debugging (if the .git directory exists in the install) * contains the automated test suite for running tests

Click here to access the git repository.

Question	Can I switch a v11 install from git over to using the releases from composr.app?
Answer	It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well. It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.

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.

Statistics

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