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 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.

Top 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.

Statistics

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