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 do I set the correct file permissions for Composr?
Answer	If you're using the quick installer, it will handle file permissions automatically. On a suEXEC-style server, default permissions (744 for directories and 644 for files) are usually sufficient. However, _config.php should have 600 permissions for security. Without suEXEC, specific directories (e.g., caches, uploads) and files (e.g., _config.php) require 777 (full access) or 666 (read/write) permissions. The fixperms.php script can automate this process on Linux and Windows.

Question	How do I install Composr on Linux?
Answer	After ensuring your web host meets the requirements and you have a database ready, you can install Composr on Linux using the following steps: Upload the Composr files to your web directory. Navigate to the install.php file in your web browser. Follow the on-screen instructions, providing the required information, such as database details and administrator credentials. After the installation is complete, delete the install.php file for security reasons.

Question	What are the prerequisites for installing Composr?
Answer	Before installing Composr, ensure your web host meets the minimum requirements. Familiarize yourself with your web host's control panel (e.g., Plesk, cPanel), which you'll use to manage databases, subdomains, and other settings. Gather your SFTP/FTP credentials (hostname, username, password), usually emailed upon signup. Set up a MySQL database and note its details: hostname (often 'localhost'), username, password, and database name. Ensure the database user has full read/write/administer access to the database.

Question	What tools are available for debugging Composr code?
Answer	Composr offers a code quality checker addon that helps identify various types of errors, including parser errors, run-time errors, and logical errors. This tool can significantly reduce debugging time and enhance code reliability. It is available through the testing_platform addon.

Question	What are some key coding standards in Composr?
Answer	Composr emphasizes clean, well-structured code with a focus on readability and maintainability. Key standards include proper indentation, consistent use of comments, and clear function headers with type definitions. Remember: beautiful code leads to better functionality and collaboration!

Question	Where can I find resources for learning PHP programming?
Answer	While Composr documentation doesn't cover basic PHP, resources like the official PHP documentation ( PHP: Hypertext Preprocessor PHP is a popular general-purpose scripting language that powers everything from your blog to the most popular websites in the world. View ), online tutorials, and the Composr API guide can help you learn.

Question	What is the purpose of the Code Editor?
Answer	The Code Editor is a web-based tool for editing Composr code files directly on the server. It requires password authentication and automatically manages overrides within _custom directories. To access it, go to `yourbaseurl/code_editor.php`.

Question	How can I export and import custom addons?
Answer	Composr allows exporting addons as TAR files, containing all necessary files and an addon.inf file for metadata. You can import these addons to share and reuse them across different Composr installations. To do this, make your necessary files for the addon in the Composr installation, and then go under Admin Zone > Structure > Addons > Export addon. You can select the relevant files for the addon, provide information about the addon, and then download the TAR file (which can then be imported on other Composr sites).

Question	Can you give an example of creating a new module?
Answer	Imagine creating a "Testing" module to manage collaborative testing: Define purpose: Allow testers to add, assign, and track tests, with security and forum integration. Design database: Plan the necessary database tables and fields to store the module's data. Create module shell: Write the basic module structure based on standard Composr modules. Define screens: Identify the module's screens and code their corresponding functions. Utilize API functions: Use Composr's built-in API functions like create_table, add_privilege, and do_template to implement functionality.

Question	What are the different ways to extend Composr functionality?
Answer	You can extend Composr through: File overrides: Replacing existing source files with modified versions in _custom directories. New Modules/Mini-modules: Creating new modules for complex functionalities or mini-modules for simpler ones. New Blocks/Miniblocks: Adding reusable content blocks. New API code: Adding new PHP files to the sources_custom directory. Hooks: Writing hooks to add features to specific areas of functionality.

Statistics

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