Contributors: A-Z Index

A

Name Photograph Title / Role Contributions / Notes
Allen Ellis Image 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 Image 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 Image 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 Image 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 How do I report an emergency problem with my Composr site?
Answer Emergency problems are events that have significantly and suddenly affected your website's functionality due to legitimate bugs or undocumented usability issues. To report these:
  • Open a tracker issue explaining the problem and providing as much detail as possible (mark it as a major bug).
  • Help the developers help you. Provide access to your site (see the software feedback tutorial for more information), describe the exact situation, and avoid protracted back-and-forth communication.
  • Take backups before upgrading. This allows for easier recovery in case of problems.
Remember that bug fixing is not a free service. While developers are committed to Composr's stability, maintaining backups and practicing restoration procedures is your responsibility.
Question How can I get support for Composr?
Answer The community forum is an excellent resource for support. Users can help each other out with various problems. However, please remember that there's no guarantee of free professional support. If you need immediate or guaranteed assistance, consider hiring a professional developer.
Question I'm getting a lot of spam on my site. What can I do?
Answer Composr offers various anti-spam measures. Refer to the Anti-spam settings tutorial for advice on configuring these settings. If you believe there's an issue with the anti-spam system itself, report it to the issue tracker. Do not report general spam incidents.
Question My website is experiencing performance issues. What should I do?
Answer If you are experiencing performance issues, first identify the specific problem with your web host's help. Composr provides tools to manage database size, bandwidth, and disk I/O. However, high request volume or CPU usage may require server upgrades like a VPS or dedicated server.

If your web host complains about resource usage, gather detailed information from them, including specific URLs causing problems and resource usage metrics. If their limits are unreasonable, consider switching web hosts.
Question How do I report a security problem?
Answer Security problems must be reported privately. You can do this by marking the issue as 'Private' on the issue tracker (if you use the Report Issue Wizard, it will do that automatically when you select security-hole). Publicly disclosing security holes is irresponsible and may result in penalties. The core developer team will disclose the issue after a patch is released.
Question How do I report a bug in Composr?
Answer Every bug, no matter how small, should be reported. You can report bugs using the Report Issue Wizard or directly through the issue tracker. There is also a link to report bugs on your Admin Zone Dashboard where the version information is located. And when clicking that link, you can view open issues specific to your version of Composr.

When reporting a bug, be sure to:
  • Check for duplicates: Make sure the bug hasn't already been reported.
  • Report bugs individually: Each issue should be reported separately for better tracking and resolution.
  • Verify it's a Composr bug: Issues with third-party addons and code should be reported to their respective developers.
  • Consult the FAQ and tutorials: Check for common problems and solutions, particularly server configuration issues.
  • Provide comprehensive information: Include a clear and specific title, detailed steps to reproduce the problem, your browser version, Composr version, error messages, stack traces (if available), and any other
relevant details.
  • Use clear and concise language: Write in proper English, use correct terminology, and avoid vagueness.
  • Be respectful and patient: Remember that developers are volunteers and may not respond immediately.
Question What is the role of robots.txt in SEO?
Answer The robots.txt file provides instructions to search engine crawlers about which parts of your website they should and should not access. You can customize the robots.txt file to prevent sensitive content from being indexed or to guide crawlers toward the most important areas of your site.
Question What is SEO and why is it important for my Composr website?
Answer SEO is the practice of optimizing your website to rank higher in search engine results pages (SERPs). By improving your SEO, you increase the visibility of your website, driving more organic (non-paid) traffic to your content.
Question How can I edit the metadata in Composr?
Answer Composr provides several ways to customize your metadata:
  • Site-wide Settings: You can configure default metadata for your entire site in the Admin Zone under Setup > Configuration > Site options.
  • Content-Specific Settings: When adding or editing content like Comcode pages or news posts, Composr provides fields for customizing titles, descriptions, and keywords specific to that content under the "Metadata" section.
  • Automatic Detection: Composr can automatically generate metadata by analyzing your content, but it's generally recommended to refine these suggestions manually for best results.
Question Should I trust agencies that promise top search engine results?
Answer No; be wary of agencies guaranteeing top rankings for any desired keyword. Achieving top results for competitive terms requires significant effort, expertise, and often, an ongoing strategy.

Focus on agencies that prioritize ethical "white-hat" SEO techniques like creating valuable content, optimizing website structure, and building natural backlinks. Avoid those employing "black-hat" methods that can lead to penalties from search engines.