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	How can potential conflicts between staff members be avoided (regarding content moderation)?
Answer	Composr incorporates "conflict detection" features to prevent staff from accidentally overwriting each other's work. When multiple staff members attempt to edit the same resource simultaneously, a warning message appears, prompting communication and coordination. Open communication and transparency are crucial. Encourage staff to share their ongoing tasks and plans with each other to prevent overlaps and potential conflicts. Utilizing shared tools like the staff checklist and private forums can further facilitate coordination.

Question	What should be considered when assigning roles and responsibilities to staff?
Answer	When assigning roles, it's recommended to start new staff with limited responsibilities and gradually increase their authority based on performance and dedication. This fosters a sense of progression and prevents discouragement among existing staff. Always consider the individual's skills and interests when assigning tasks. For example, someone with strong writing skills might be well-suited for managing content creation, while a technically-minded person could excel at site maintenance.

Question	How can staff be effectively managed in a Composr community?
Answer	Successful staff management requires a mindful approach that prioritizes fostering a positive and productive environment. Key recommendations include: Respect staff limitations: Avoid overwhelming staff with excessive workload or overly ambitious site expansions. Active involvement: Maintain active involvement in overseeing staff activities and ensuring their effective functioning. Open communication: Engage in regular communication, providing feedback, addressing concerns, and recognizing achievements. Foster teamwork: Encourage collaboration and information sharing among staff members. Lead by example: Ensure staff adhere to community rules and demonstrate expected behavior. Empowerment and trust: Grant sufficient freedom and control to enable staff to excel in their roles. By fostering a supportive and empowering environment, community managers can enable staff to contribute their best efforts and drive the community's success.

Question	How should staff members be chosen for a Composr-based online community?
Answer	Choosing staff for online communities differs from traditional hiring processes due to factors like unpaid positions, varying time commitments, and remote interactions. Focus should be placed on identifying individuals with: Genuine interest: Look for members passionate about the community and its goals. Available time: Ensure potential staff can dedicate sufficient time to fulfill their responsibilities. Relevant skills: Prioritize skills and experience aligned with the specific role requirements. Maturity and discipline: Seek individuals who demonstrate responsible behavior and commitment. Recruitment methods like directly approaching active community members or allowing the Composr points system (or the karma non-bundled addon) to identify dedicated contributors can be more effective than traditional advertising.

Question	How can content issues be reported and addressed by staff?
Answer	Composr's content reporting system, powered by the Tickets addon, allows users to report problematic content to staff. Key features include: Report links: "Report this" links embedded throughout the site enable users to flag content for review. Custom reporting interface: Forums offer a dedicated interface for reporting individual posts. Anonymous reporting: Logged-in users can choose to report content anonymously. Ticket-based management: Reports are automatically created as support tickets, facilitating staff collaboration and record-keeping. Comprehensive report details: Tickets include content title, type, ID, submitter information, an embedded rendering of the reported content, and the reporter's explanation. This system ensures efficient handling of content issues, allowing staff to address concerns effectively while maintaining a transparent record of actions taken.

Question	How can staff members collaborate effectively in Composr?
Answer	Composr offers various tools to facilitate staff collaboration: Private forums: Dedicated forums with restricted access enable staff to discuss site operations and coordinate activities. Composr installs a staff forum by default in Conversr. Conflict detection: When multiple staff members attempt to edit the same resource simultaneously, Composr displays warnings at the top to prevent accidental overwrites. Staff checklist & dashboard: The Admin Zone dashboard provides a shared checklist for task management, along with space for notes and links. Staff notifications and tickets system: Staff receive notifications about various site events, including support tickets from the "Contact Us" page, allowing for efficient issue handling. Content notes: Staff can embed notes within Comcode or use dedicated "staff notes" fields for various content types to share information and context. Validation and workflows: Content can be intentionally left unvalidated even by staff, enabling secondary checks before publishing. A dedicated workflows addon allows for complex approval processes with multiple stages involving different staff groups.

Question	What defines a staff member in Composr?
Answer	There are two ways to define "staff" in Composr: System-defined staff: This includes administrators and super moderators who have specific privileges within the forum/member system (Conversr). Privilege-based staff: Anyone granted the necessary permissions for a particular situation is considered staff for that context. Composr prioritizes flexibility by utilizing privileges over fixed roles, allowing for customized staff responsibilities. However, certain features like "staff reply" in tickets inherently rely on a pre-existing understanding of "staff."

Question	What steps should I take if my website has been hacked?
Answer	If you suspect a security breach, take immediate action: Identify the Cause: Analyze access logs for suspicious activity and pinpoint the vulnerability. Clean and Restore: Restore your website from a clean backup and thoroughly remove any malicious code. Address Vulnerabilities: Patch security holes, update software, and strengthen security configurations. Seek Expert Help: If needed, consult security professionals for assistance with cleanup and prevention.

Question	What additional security measures can I implement for my Composr website?
Answer	SSL: Enable HTTPS for encrypted communication and improved user trust. Secure Zones: Configure sensitive zones to require confirmed sessions. Restrict Logins: Enforce IP address confirmation for enhanced account security. Maintenance Scripts: Restrict access to maintenance scripts like upgrader.php via IP restrictions. Server Hardening: Disable unnecessary services, change default ports, enable automatic updates, and more. Robots.txt: Use the robots.txt file to prevent search engine indexing of sensitive areas.

Question	How does Content Security Policy (CSP) contribute to Composr security?
Answer	CSP adds a layer of protection by controlling the resources the browser is allowed to load. It helps prevent: XSS Attacks: By restricting inline scripts and limiting script sources. Data Injection Attacks: By controlling the allowed origins for data requests. Clickjacking: By specifying allowed framing sources. Composr's CSP implementation utilizes "Trusted partner sites" and nonces for fine-grained control.

Statistics

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