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 restore my Composr website from a backup?
Answer	Composr backups come as .tar or .tar.gz files. Extract the archive using an extraction program like 7-zip or your web hosting control panel. To restore a full backup: Upload the extracted files to your webserver, overwriting the existing files. Run the included restore.php script in your browser. This script will restore the database from the restore_data.php file. To restore incremental backups: Restore the initial full backup. Sequentially extract and overwrite files from each incremental backup over the restored full backup. The last extracted restore_data.php will contain the latest database state. Run restore.php to restore the final database version.

Question	What alternative backup strategies are available?
Answer	Many web hosting control panels include built-in backup features that operate at the system level, often offering higher reliability than web-based scripts. Ensure you back up both files and the database. For database backups, you can use tools like phpMyAdmin, which allows you to export your database as a .sql file.

Question	How do I create a backup of my Composr website?
Answer	Composr offers a built-in backup addon accessible from Admin Zone > Tools > Backups. You can choose between full, incremental, and database-only backups. Full backup: Backs up all files and folders within the Composr installation directory, including the database. Incremental backup: Backs up only new or changed files since the last backup, resulting in smaller backup files. Database backup only: Backs up only the database. The addon allows scheduled backups or manual backup generation. It is recommended to download backups to a location outside your web server for better security. Note: The Composr backup addon is limited by server-side PHP capabilities and might not always be reliable. Consider using alternative backup strategies offered by your web hosting control panel for increased reliability.

Question	Why are backups necessary for my Composr website?
Answer	Disasters like hard disk failures, data corruption, and unexpected errors can happen at any time. A good backup strategy helps you recover your website and its data in case of such events. Backups can also help you roll back to a previous state if needed, such as after a failed upgrade or accidental changes.

Question	How can I control the privacy of member profile fields?
Answer	You can control the privacy of member profile fields through the "Member privacy controls" configuration option. If you enable the "Extended privacy option control", you can fine-tune visibility settings for each field. Otherwise, you can set simple access levels (e.g., not at all, to members, to friends, to everyone) for each field.

Question	What is the difference between a Composr member and an author?
Answer	A member is someone who has created an account on your Composr website and can log in. They have a unique member ID and username, and can interact with the site's features. An author is someone who creates content for the site. They may or may not be a member. For example, you might have an author who submits articles via email but never actually visits or joins the website.

Question	What advanced techniques are available for dealing with persistent spammers who repeatedly create new accounts?
Answer	Composr's advanced banning features target sophisticated human spammers. Automatic bans can be configured to block users based on specific strings in their posts, while reasoned bans display customized messages to banned users, potentially deterring them. These measures, coupled with the ability to investigate users via IP address analysis, offer robust tools for managing persistent threats. You can configure advanced banning under Admin Zone > Security > Configure advanced banning.

Question	How does Composr handle user banning and what options are available?
Answer	Composr offers various banning mechanisms. You can ban members by editing their accounts (ban member tick box), preventing logins while still allowing guest access. IP address banning blocks access from specific IP addresses or ranges (Admin Zone > Security > Members > Investigate user to see their IP addresses and flag certain ones for banning). You can also restrict member submissions, or you can effectively "suspend" users by assigning them to a usergroup with minimal privileges (e.g. probation).

Question	What is the "Warn Member" form and how can I use it to handle rule violations?
Answer	The "Warn Member" form provides a centralized interface for addressing user misconduct. You can issue formal or off-the-book warnings, apply punitive actions like IP bans, usergroup changes, or probation, and even delete content or charge points. This form allows you to document reasons for actions, improving transparency and consistency in moderation. This tool can be accessed on a member's profile as staff, under Audit > Warn member. You can also review their warnings history on their "Standing" tab.

Question	How does Composr track user activity?
Answer	Composr logs IP addresses for various actions like guest posting, page views, and content submissions. This data helps identify potential spammers and track user behavior. The "Investigate user" module provides tools to analyze IP addresses and gather additional information about suspicious activity.

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