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

Top 10 Entries

Question	How can I ensure my website complies with email marketing laws?
Answer	Email marketing laws like CAN-SPAM protect recipients' rights to unsubscribe. Your website must include a clear 'List-Unsubscribe' header in every email, offer an easy unsubscribe process, and respect unsubscribe requests promptly. Composr provides built-in mechanisms, including an unsubscribe endpoint and support for the List-Unsubscribe header, to facilitate compliance.

Question	What are my responsibilities regarding user privacy?
Answer	You must have a comprehensive privacy policy that details the personal data you collect, its usage, and if it's shared with third parties. Laws like GDPR have strict requirements, including logging data access, data purging, and security measures. California law mandates specific elements in your policy, like handling "Do Not Track" requests and a clear process for communicating changes. Composr has an automatic Privacy Policy generator block to help you get started. This is used by default.

Question	How can I create effective website rules?
Answer	A well-defined rules page is crucial for setting expectations for user behavior and outlining consequences for violations. It should cover a range of offenses with appropriate punishments, reference relevant laws, and assign legal responsibility to users. Composr provides default rules pages that can be customized, and this page is displayed to users upon joining the site.

Question	What are the key legal considerations for running a website?
Answer	Several legal aspects need careful attention when operating a website, especially for large or corporate sites. These include establishing clear rules and terms of service, adhering to privacy laws like GDPR and California's regulations, managing personal data responsibly, complying with email marketing regulations like CAN-SPAM, ensuring website accessibility, addressing eCommerce regulations, and understanding liability for content and user actions.

Question	How do data-tpl and data-view behaviors work in Composr's JavaScript?
Answer	Composr uses data-tpl and data-view behaviors for associating HTML templates and JavaScript views, respectively. This facilitates clean separation of presentation and logic: data-tpl: Used with the $cms.behaviors.initializeTemplates function and PARAMS_JSON tempcode directive to bind JavaScript logic to HTML templates. data-view: Used with the $cms.behaviors.initializeViews function to associate JavaScript view classes (inheriting from $cms.View) with specific HTML elements.

Question	What are the advantages of using Composr's JavaScript libraries?
Answer	Composr's JavaScript libraries like $cms, $util, and $dom offer several advantages: Organization: They provide a structured way to access Composr-specific functionalities, avoiding global namespace pollution. Abstraction: They encapsulate common tasks, simplifying DOM manipulation, form handling, and interaction with Composr's UI. Consistency: They offer a consistent API across different parts of Composr.

Question	How does Composr implement the Model-View-Controller (MVC) pattern?
Answer	Model/API: The sources directory primarily houses scripts forming the Model/API, handling data logic and business rules. View: Templates in themes/default/templates represent the View, responsible for presenting data to the user. Comcode pages can also be considered part of the View. Controller: Entry scripts like index.php and site/dload.php act as front controllers, directing requests. Modules and blocks, residing in */pages/modules and sources/[mini]blocks, respectively, serve as controllers, managing user interactions and determining which View to render.

Question	Can I translate my content into multiple languages?
Answer	Yes, Composr supports multi-language content. You can enable this feature by: Installing multiple language packs: Make sure you have at least two language packs installed. Enabling the Conversr multi-language option: Go to Admin Zone > Setup > Configuration > Site options > Internationalisation. Running a Commandr command: Execute the necessary command to set up the database structure for multi-language content (unless you already enabled Support content translations when installing). Once enabled, you can translate your content into different languages and allow visitors to choose their preferred language.

Question	My language uses gendered descriptors. How can I handle this in Composr?
Answer	Composr offers solutions for languages with gendered descriptors: Template editing: You can modify templates to use different language strings based on user gender. This involves adding Tempcode logic to dynamically select the appropriate string. Custom Profile Fields: Create a Custom Profile Field for "Gender" and use it to conditionally display gendered language strings in templates. These methods allow for flexible handling of gendered language variations.

Question	What are language strings, and how are they used?
Answer	Language strings are phrases or pieces of text used throughout Composr. They're identified by unique codenames, like WELCOME_MESSAGE. These strings are stored in .ini language files and used to display text in the user interface. By translating language strings, you change the text displayed on your website without modifying the underlying code.

Statistics

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