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 is post history and why is it important?
Answer	Post history tracks changes made to forum posts, including edits and deletions. This feature helps monitor for inappropriate edits or attempts to cover up spam or rule violations. Staff can review the history, restore deleted content, or even permanently erase it.

Question	Can I moderate content in Composr forums?
Answer	Yes, Composr provides various moderation tools for managing forum content. Moderators can edit or delete posts and topics, move topics between forums, close or open discussions, and validate content submitted by users who require approval. These are done in an actions dropdown on a topic, or through buttons on individual posts.

Question	What is the "black hole" technique and how does it work?
Answer	The "black hole" technique involves adding hidden fields to forms. While invisible to human users, bots often detect and fill these fields, revealing their nature. Composr uses this information to flag and block suspected spam submissions.

Question	How can I report spam in Composr?
Answer	You can report spam using the "report this" link or "report" (forum post button) feature. This alerts staff to the issue, allowing them to investigate and take appropriate action, such as deleting the spam, warning the user, or banning them. It also creates a Support Ticket between the reporter and staff in case the staff need further information.

Question	What are Remote Block Lists (RBLs)?
Answer	RBLs are third-party lists that track IP addresses associated with spamming activity. Composr can be configured to consult these lists and block or flag requests from suspicious IPs. However, relying solely on RBLs may lead to false positives, as some lists are overly broad.

Question	What are CAPTCHAs and how do they work?
Answer	CAPTCHAs are tests designed to differentiate between human users and bots. Composr's unique CAPTCHA method uses CSS and JavaScript to generate images or audio challenges that are difficult for bots to solve. While effective, some spammers use human workers to bypass CAPTCHAs, leading to the need for additional anti-spam measures.

Question	How does Composr prevent spam?
Answer	Composr offers several tools and techniques to combat spam, including: CAPTCHA: A visual or audio test that humans can easily pass but bots struggle with. This helps prevent automated spam submissions. Heuristics: If Composr thinks an action is spam based off of configurable criteria, it can either flag the content for validation, block the attempt, or ban the IP address outright. Public block lists: Composr can utilize the Stop Forum Spam system or other block list systems to identify and block known spammers based on IP addresses, usernames, and email addresses. Link posting restrictions: Disallowing links in member profiles for users with no posts and adding "nofollow" attributes to links discourages spammers seeking backlinks. Black hole fields: Hidden form fields that should remain empty. Bots often fill these in, allowing Composr to identify them. Project Honey Pot integration: A system that places hidden links on pages, attracting and identifying spam bots. Content/post reporting: Users can report spam, enabling staff to take action. Guest posting limitations: Restricting guest permissions raises the bar for spammers. Advanced techniques: Developer addons like "antispam_question" or probation systems provide additional layers of protection.

Question	What is the "Sitemap" in Composr, and how is it used?
Answer	The Sitemap is a hierarchical representation of your website's content, including zones, pages, categories, and entries. Composr generates the Sitemap dynamically and uses it for various purposes: Generating menus. Creating the user-facing sitemap page. Generating the XML Sitemap for search engines. Providing a visual representation of your website structure in the Sitemap editor and Permissions tree editor. You can edit the sitemap under Admin Zone > Structure > Sitemap editor.

Question	Can I change the URL scheme after my website is already live?
Answer	Yes, you can enable or change a URL scheme on an existing website. Old URLs will redirect to the new format, ensuring that your SEO isn't negatively impacted. The canonical URL will also be specified in your website's HTML, further protecting your search rankings.

Question	How do URL schemes work, and what are the benefits of using them?
Answer	URL schemes allow you to control the structure of your website's URLs. Composr offers several schemes that create shorter, more user-friendly URLs: /pg/ (e.g., /pg/home) .htm (e.g., /home.htm) Simple unadorned URLs (e.g., /home) Benefits of using URL schemes include: Improved user experience with more readable URLs. Potential SEO benefits, as some believe search engines favor cleaner URLs. Easier sharing on social media and other platforms.

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