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 I customize Composr without modifying the core files?
Answer Composr offers a robust override system. Instead of altering the original files, create a parallel structure within _custom directories. For example, to modify site/pages/modules/polls.php, place your customized version in site/pages/modules_custom/polls.php.

The tutorials outline additional information on how to utilise overrides.
Question What are the main components of the Composr framework?
Answer Composr consists of:
  • Modules: PHP files that provide related screens, forming the building blocks of addons.
  • Comcode: Text files containing content written in a simplified markup language.
  • HTML: Files containing standard HTML for web pages.
  • Sources: PHP code files for the core API and functionality.
  • Hooks: PHP files enabling addons to interact and extend each other's functionality.
  • Blocks/Miniblocks: Reusable components for displaying dynamic content within pages.
  • Themes: Folders containing images, CSS, and templates to define the look and feel.
  • Language files: Files holding text strings for multilingual support.
Question How can I embed third-party widgets into my Composr pages?
Answer Composr supports embedding widgets from various websites, like Google Maps, Vimeo, and YouTube, by simply pasting the URL. For manually embedding widget code, you can paste it into the HTML source view of the WYSIWYG editor or within Comcode html tags if not using the WYSIWYG editor.
Question What is the difference between blocks and boxes in Composr?
Answer Boxes are visual elements that provide a container for content, while blocks are functional units that generate and display dynamic content. Although blocks often appear within boxes in the default templates, they are not inherently tied to any visual representation.
Question Can I customize the appearance of blocks?
Answer Yes, you can style blocks by editing the associated templates and CSS. Templates are typically named after the block they represent. For example, the main_news block uses the BLOCK_MAIN_NEWS.tpl template.
Question How do I create custom filter forms for my content?
Answer The main_content_filtering block can help you generate filter forms automatically. You can use it to create a default form and then customize the generated Filtercode string to refine the filtering options. Once satisfied, you can either continue using the block or extract the HTML and modify it further.
Question Where can I use Filtercode and Selectcode in Composr?
Answer Filtercode is supported in various blocks, such as main_multi_content, main_gallery_embed, and main_cc_embed. It's also actively used in modules like catalogues, downloads, galleries, members, and news.

Selectcode is supported in blocks and Comcode tags that explicitly mention it, including the main_multi_content block and the if_in_group Comcode tag.
Question What is the difference between Filtercode and Selectcode?
Answer Filtercode is used for querying content based on properties and values, while Selectcode is used for directly specifying a list of IDs or categories to include or exclude. Filtercode offers more complex filtering options, while Selectcode is more straightforward for simple selections.
Question How can I filter content in Composr?
Answer Composr provides two filtering systems: Filtercode and Selectcode.
  • Filtercode is used for selecting content based on defined filters, such as field values, ratings, or keywords. It utilizes a syntax of comparisons, separated by commas, where each comparison specifies a field and a matching condition.
  • Selectcode is a simpler syntax for specifying a list of IDs or categories to include or exclude from the results. It uses a comma-separated list of match-specifier tokens, such as individual IDs, ranges, or wildcard characters.
Question What are blocks in Composr and how can I use them?
Answer Blocks are dynamic elements that can be inserted into Comcode pages to add interactive and data-bound functionality to your website. They are essentially reusable components that automatically generate content, such as recent forum posts or information about the logged-in user.

You can add blocks to your pages using the block construction assistant, which allows you to select from a list of available blocks, set their parameters, preview them, and generate the necessary Comcode.

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