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

Top 10 Entries

Question	What are redirects and how can I use them for subsites?
Answer	Redirects let you create custom URL paths that point to different zones and pages within your site. Examples: Sharing modules across zones: Create a redirect to make a module in one zone appear in another. Creating shortcuts: Use a redirect to point a short URL to a longer, more complex URL. Moving pages: Use a redirect to ensure old links still work after moving a page to a new location. Go to Admin Zone > Structure > Redirects.

Question	What are virtual roots and how do I use them?
Answer	Virtual roots let you make a sub-category within a Composr module (e.g., downloads) appear as the top-level category. This is useful for creating separate "databases" of content for different subcommunities. To create a virtual root: Enable "Virtual root links" in the Admin Zone > Setup > Configuration > Feature options > Advanced. Navigate to the desired category while logged in as staff. Click the rightmost link in the breadcrumbs (it will be an anchor for virtual root creation). Use the resulting URL in your menus to link to the "virtualized" category.

Question	Can I have subsites and subcommunities within a single Composr installation?
Answer	Yes, Composr offers various tools to create subsites and subcommunities within a single installation: Zones: Create separate sections under different URLs with their own pages and content. Redirects: Make modules appear in different zones without actually moving them. Categories & Virtual Roots: Organize content like galleries, downloads, and catalogs into sub-trees that appear as separate entities. Usergroups & Permissions: Group members into subcommunities and control their access to specific content. Themes: Customize the look of different zones.

Question	What is the difference between a central site and a satellite site in an M.S.N.?
Answer	The central site hosts the shared forum, member database, and netlink system. It is the core of your M.S.N. Satellite sites are the additional websites within your network. They connect to the central site for member information and forum access.

Question	What are the advantages and disadvantages of using an M.S.N.?
Answer	Advantages: Full control: You have complete control over each site's settings and content. Administrative separation: Managing staff and content for each site is more organized. Special M.S.N. features: Composr provides specific features like the 'netlink' system for easy navigation between network sites. Disadvantages: Configuration and maintenance: Setting up and maintaining multiple sites can be more complex.

Question	What is a multi-site network (M.S.N.) in Composr?
Answer	An M.S.N. allows you to run multiple Composr websites (installations) that share a common forum and member database. It's ideal for website networks with shared communities but segmented content, staff, or branding. In essence, members who join one site automatically have accounts on all sites within the network.

Question	What are the key classes and utilities provided by Composr Mobile SDK?
Answer	CMS SDK provides several classes with utility functions mirroring PHP and Composr APIs, including: CMS_Arrays: Array operations (e.g., implode, explode, list_to_map). CMS_Strings: String manipulation (e.g., strip_tags, html_entity_decode, strpos). CMS_Langs: Localization functions (e.g., do_lang). CMS_Preferences: User preference management. CMS_Timestamps: Timestamp functions (e.g., get_timezoned_date_time, time). CMS_HTTP: Web service interactions (e.g., rawurlencode, json_decode, http_get_contents). CMS_Users: User data and permission checks (e.g., has_page_access, is_staff). CMS_Flow: App flow control (e.g., access_denied, attach_message). CMS_Forms: Form building and management. CMS_Database: SQLite database access and manipulation. CMS_Notification: Push notification handling. CMSNetworkManager: Network request execution and response handling.

Question	How do I set up Composr Mobile SDK in my iOS and Android projects?
Answer	iOS (Xcode): Create a new project or open an existing one. Add a Prefix Header file (.pch) if you don't have one, following the provided instructions. Add required frameworks to your project's Build Phases. Add the CMS SDK to your project, then remove references to unwanted files. Set the header search path to the CMS SDK folder in build settings. Add a compiler option for the JsonKit library. Import CMS_SDK.h in your .pch file. Android (Eclipse): Create a new project or open an existing one. Import CMS SDK into your workspace as an Android project. Ensure "Is Library" is checked in the CMS SDK's "Android" properties tab. Add CMS SDK as a dependent library in your project's properties. Clean and rebuild your project.

Question	What are some key concepts related to mobile app development with Composr?
Answer	Essential concepts include: SDK (Software Development Kit): An API implementation, typically as a library. API (Application Programming Interface): A set of rules for software interaction. JSON (JavaScript Object Notation): A common language for structured data transfer over REST. REST (Representational State Transfer): An architectural style for web services. Push notification: A notification sent to a mobile device.

Question	What other approaches exist for mobile integration with Composr?
Answer	Other approaches, in various stages of development, include: Tapatalk: A third-party forum app with an official Composr addon, offering a high-quality "out-of-the-box" Composr app experience. Further Composr Mobile SDK development: Plans and issues relating to the SDK's evolution can be found on the Composr tracker, driven by commercial projects and feature sponsorship.

Statistics

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