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 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.
Question What is the purpose of "confirmed" and "non-confirmed" sessions?
Answer Composr distinguishes between confirmed and non-confirmed sessions for added security:
  • Confirmed: When you actively log in with your credentials.
  • Non-confirmed: When you return to the site and are automatically logged in via cookies.

You can configure zones to require confirmed sessions, preventing access from cookie-based logins alone. The Admin Zone uses this by default.
Question How can I enhance the security of my Composr installation on shared hosting?
Answer Shared hosting environments can be inherently less secure. Here are some tips:
  • Choose a Secure Host: Opt for hosts that offer suEXEC and open_basedir for better account isolation.
  • Test Security: Verify the host's security measures with the provided filesystem_browser.php script.
  • Restrict _config.php: Remove world-writable permissions from _config.php after installation.

Top 10 Entries

Question What is a "page-link," and how does it differ from a URL?
Answer A page-link is a Composr-specific way to reference a page or screen within your website. It's a simplified, local representation of a URL, independent of the URL scheme you might be using.

For example, the page-link site:downloads:browse:10 points to the download category with ID 10 in the site zone. This page-link remains consistent even if your URL scheme changes the way URLs are structured. Page-links also do not consider monikers, so if a URL moniker changes, page-links will stay the same.

This is a powerful feature as you can use the Comcode [page="page-link"]Page title[/page] tag to generate URLs of local content. And these will always work regardless of URL scheme or moniker.
Question How do menus work in Composr, and can I customize them?
Answer Composr has a flexible menu system that can be customized to your needs.
  • Default Menu: Generated automatically from the Sitemap, reflecting the structure of your content.
  • Editable Menus: You can create and fully customize these menus, adding links to specific content or external websites.

Menus can be added to panels (sidebars, headers, footers) or embedded directly within Comcode pages. The menu editor provides tools for adding branches, setting captions, tooltips, and URLs, and even defining context-sensitive behavior using "match-keys."
Question What are "zones" in Composr, and what are they used for?
Answer Zones are like sub-sites within your Composr website. They provide a way to organize content and apply different settings, like permissions, themes, and navigation. Some default zones include:
  • Welcome Zone: The initial landing page, often used for login/signup.
  • Site Zone: Your main website content, with features for viewing, submitting, editing, and deleting content on the member level.
  • Admin Zone: For site administrators to manage the website.
  • Content Management Zone: Where content is added, edited, and deleted, typically by site staff.
  • Forum Zone (if using Conversr): Houses the forum section of your site.
Question What are the different ways to control access in Composr?
Answer Composr offers a robust permission system with various methods for controlling access:
  • Zones, Pages, and Categories: Control which usergroups can view specific zones, pages, and categories (permissions).
    • Admin Zone > Security > Permissions Tree Editor, or on the UI for the Zone / Page / Category.
  • Global Privileges: Define permissions for actions like using advanced Comcode or bypassing the word filter, applicable across the entire site.
    • Admin Zone > Security > Global privileges
  • Module/Page Overrides: Tailor privileges for particular content types by overriding them on the controlling module or page.
    • Admin Zone > Security > Permissions Tree Editor [> Content permissions]
  • Category Overrides: Modify privileges for specific categories, allowing fine-grained control over actions within those categories.
    • Admin Zone > Security > Permissions Tree Editor
  • Match-key Permissions: Implement ad-hoc access control based on specific match-keys, offering flexibility beyond traditional permission structures.
    • Admin Zone > Security > Match-key page restrictions
Question What happens when I add a new usergroup to a third-party forum integrated with Composr?
Answer If you are not using Conversr as your forum, Composr won't automatically assign any permissions to the new usergroup. To rectify this, you can use the "Absorb usergroup-permissions" feature in the Admin Zone. This tool allows you to copy the permissions from an existing usergroup to the newly created one, ensuring consistent access and functionality.
Question What are some security considerations regarding super-moderators and super-administrators?
Answer While super-moderators have extensive access to manage your site, certain sensitive privileges are reserved for super-administrators. This includes the ability to impersonate other users, execute arbitrary code, and view private content. These restrictions help prevent potential privilege escalation and ensure the overall security of your website. Exercise caution when granting super-moderator status and trust only reliable individuals.
Question What are some useful tools for debugging permission issues?
Answer Composr provides a couple of tools to help pinpoint permission problems:
  • FirePHP: This browser add-on allows you to view detailed logs of permission checks performed by Composr. By analyzing these logs, you can identify which checks are failing and adjust your settings accordingly.
  • Permission Check Logging: Enable logging of failed permission checks to a file (data_custom/permission_checks.log). This provides a persistent record of permission issues that you can review and troubleshoot.
Question How can I test if my permission settings are working correctly?
Answer Composr's "SU" feature allows administrators to temporarily assume the identity of another user, enabling you to experience the site as they would. Simply enter the desired username in the "SU" box in the footer. You can also use "Guest" to browse as an unauthenticated visitor. Remember that using "SU" doesn't accurately reflect online status and retains administrator access to sensitive areas.
Question Can I display different content to different usergroups?
Answer Yes, you can achieve this by leveraging Tempcode within your templates. By using conditional statements like {$IS_IN_GROUP} and {$HAS_PRIVILEGE}, you can show or hide specific content sections based on the user's group membership or privileges. This technique allows you to "tease" premium content to non-paying users or tailor the user experience based on their access level.
Question What are match-key permissions and why would I use them?
Answer Match-key permissions provide a more granular level of access control beyond the standard zone, page, and category permissions. They allow you to restrict access based on specific "match-keys", which are unique identifiers for different actions or content within Composr. For instance, you could use match-key permissions to prevent guests from submitting banners or to restrict access to the member directory for all but specific usergroups. You can also specify custom access denied errors for each match-key.

A "match-key" is typically a page-link, such as cms:cms_banners:add.