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 the purpose of "confirmed" and "non-confirmed" sessions?
Answer	Composr distinguishes between confirmed and non-confirmed sessions for added security: Confirmed: When you actively log in with your credentials. Non-confirmed: When you return to the site and are automatically logged in via cookies. You can configure zones to require confirmed sessions, preventing access from cookie-based logins alone. The Admin Zone uses this by default.

Question	How can I enhance the security of my Composr installation on shared hosting?
Answer	Shared hosting environments can be inherently less secure. Here are some tips: Choose a Secure Host: Opt for hosts that offer suEXEC and open_basedir for better account isolation. Test Security: Verify the host's security measures with the provided filesystem_browser.php script. Restrict _config.php: Remove world-writable permissions from _config.php after installation.

Question	How does Composr protect against Cross-Site Scripting (XSS) attacks?
Answer	Composr utilizes multiple layers of defense against XSS attacks: HTML Filtering: Configurable levels of filtering prevent malicious script injection. Content Security Policy (CSP): Restricts the sources from which scripts and other resources can be loaded. Input Sanitization: Data is sanitized before being processed to prevent malicious code execution. Output Encoding: Data displayed to users is properly encoded to prevent interpretation as active code.

Question	What are the different types of security alerts in Composr?
Answer	Composr has a variety of hack-attack codenames that trigger security alerts and logging. Some common examples include: DODGY_GET_HACK: Suspicious URLs with potentially harmful characters. EVIL_POSTED_FORM_HACK: Possible CSRF attempts via malicious form submissions. SCRIPT_UPLOAD_HACK: Attempts to upload PHP scripts, potentially malicious. DOWNLOAD_PRIVATE_URL_HACK/TRY_TO_DOWNLOAD_SCRIPT: Attempts to download sensitive files. BRUTEFORCE_LOGIN_HACK: Repeated failed login attempts. SQL_INJECTION_HACK: Attempts to exploit SQL queries for data extraction. You can customize alert handling for each type in data_custom/xml_config/advanced_banning.xml (Admin Zone > Security > Configure advanced banning).

Question	What are some tips for secure website maintenance?
Answer	Avoid FTP: Use secure alternatives like SFTP or SSH for file transfer. Secure Email: Enable SSL for IMAP and POP3 email protocols. Strong Passwords: Use unique and complex passwords for different services. Secure Computers: Keep your own devices patched and secure. Maintenance Password: Remove the maintenance password from _config.php when not in use.

Question	What are the main security features of Composr?
Answer	Composr has a robust set of security features to protect your website, including: Passwords: Visual representation of password quality and enforcement of complexity rules. Password expiry and prevention of re-use. Secure password hashing, even if the database is compromised. Temporary passwords for staff setup. Login Restrictions: Two-factor authentication via IP address approval. IP address banning, including wildcard banning. Session locking to IP addresses. Configurable session expiry times. Ability to prevent privileged actions from auto-logged in sessions. Optional member approval process. Auditing Systems: Comprehensive audit logging of administrative actions. Logging of user actions and IP address history. Tools to analyze audit logs. Failed login logging. Hack attack detection, logging, and banning. Email notifications for changes to user credentials. Framework Security: Protection against CSRF attacks. Click-jacking prevention via CSP implementation. Secure coding standards and scanning techniques. Configurable HTML filtering to prevent XSS attacks. Secure code modularization standards. Other features: Granular privileges and access permissions. Content submission validation process. Rootkit detection system. Spam prevention systems. Web application firewall rules. Moderation systems.

Question	Why are my searches slow, and how can I improve search speed?
Answer	Slow searches can occur when dealing with large amounts of content. Here are some workarounds and solutions: MySQL timeout setting: For MySQL 5.7+, set a query timeout to prevent searches from locking up your database. Composr automatically sets this, but you can configure it manually if needed. Use InnoDB tables: Switching to InnoDB tables in MySQL can prevent slow queries from affecting other users on your website. Note that InnoDB is not officially supported by Composr yet. Enable the fast custom index: As mentioned earlier, the fast custom index is optimized for handling large datasets and filtered searches, potentially leading to significant speed improvements.

Question	How does the search engine handle different languages?
Answer	Composr's fast custom index supports multiple languages. Content is indexed based on its translated version, ensuring that you get relevant results even when searching in a different language.

Question	What are quoted phrases and how do they work?
Answer	Quoted phrases allow you to search for an exact sequence of words. For example, searching for "red apple" will only return results containing that exact phrase. Keep in mind that enabling quoted phrases can increase disk space usage.

Question	How do stop words affect search results?
Answer	Stop words are common words (like "the", "a", "is") that are ignored by the search engine because they add noise and don't contribute to the meaning of the search query. You can customize the list of stop words for the fast custom index. See the search tutorial for more information.

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