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 do I report an emergency problem with my Composr site?
Answer	Emergency problems are events that have significantly and suddenly affected your website's functionality due to legitimate bugs or undocumented usability issues. To report these: Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug). Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication. Take backups before upgrading. This allows for easier recovery in case of problems. Remember that bug fixing is not a free service. While developers are committed to Composr's stability, maintaining backups and practicing restoration procedures is your responsibility.

Question	How can I get support for Composr?
Answer	The community forum is an excellent resource for support. Users can help each other out with various problems. However, please remember that there's no guarantee of free professional support. If you need immediate or guaranteed assistance, consider hiring a professional developer.

Question	I'm getting a lot of spam on my site. What can I do?
Answer	Composr offers various anti-spam measures. Refer to the Anti-spam settings tutorial for advice on configuring these settings. If you believe there's an issue with the anti-spam system itself, report it to the issue tracker. Do not report general spam incidents.

Question	My website is experiencing performance issues. What should I do?
Answer	If you are experiencing performance issues, first identify the specific problem with your web host's help. Composr provides tools to manage database size, bandwidth, and disk I/O. However, high request volume or CPU usage may require server upgrades like a VPS or dedicated server. If your web host complains about resource usage, gather detailed information from them, including specific URLs causing problems and resource usage metrics. If their limits are unreasonable, consider switching web hosts.

Question	How do I report a security problem?
Answer	Security problems must be reported privately. You can do this by marking the issue as 'Private' on the issue tracker (if you use the Report Issue Wizard, it will do that automatically when you select security-hole). Publicly disclosing security holes is irresponsible and may result in penalties. The core developer team will disclose the issue after a patch is released.

Question	How do I report a bug in Composr?
Answer	Every bug, no matter how small, should be reported. You can report bugs using the Report Issue Wizard or directly through the issue tracker. There is also a link to report bugs on your Admin Zone Dashboard where the version information is located. And when clicking that link, you can view open issues specific to your version of Composr. When reporting a bug, be sure to: Check for duplicates: Make sure the bug hasn't already been reported. Report bugs individually: Each issue should be reported separately for better tracking and resolution. Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers. Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues. Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other relevant details. Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness. Be respectful and patient: Remember that developers are volunteers and may not respond immediately.

Question	What is the role of robots.txt in SEO?
Answer	The robots.txt file provides instructions to search engine crawlers about which parts of your website they should and should not access. You can customize the robots.txt file to prevent sensitive content from being indexed or to guide crawlers toward the most important areas of your site.

Question	What is SEO and why is it important for my Composr website?
Answer	SEO is the practice of optimizing your website to rank higher in search engine results pages (SERPs). By improving your SEO, you increase the visibility of your website, driving more organic (non-paid) traffic to your content.

Question	How can I edit the metadata in Composr?
Answer	Composr provides several ways to customize your metadata: Site-wide Settings: You can configure default metadata for your entire site in the Admin Zone under Setup > Configuration > Site options. Content-Specific Settings: When adding or editing content like Comcode pages or news posts, Composr provides fields for customizing titles, descriptions, and keywords specific to that content under the "Metadata" section. Automatic Detection: Composr can automatically generate metadata by analyzing your content, but it's generally recommended to refine these suggestions manually for best results.

Question	Should I trust agencies that promise top search engine results?
Answer	No; be wary of agencies guaranteeing top rankings for any desired keyword. Achieving top results for competitive terms requires significant effort, expertise, and often, an ongoing strategy. Focus on agencies that prioritize ethical "white-hat" SEO techniques like creating valuable content, optimizing website structure, and building natural backlinks. Avoid those employing "black-hat" methods that can lead to penalties from search engines.

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