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 Can I use the calendar as a personal diary and keep my entries private?
Answer Yes. When adding an event to the calendar, you can choose to make it public or private. Private events are generally used when someone wants to use the calendar system as a diary.
Question How can I set up reminders for events?
Answer When adding or editing an event, you can enable reminders for yourself and specific user groups. You can also choose how much notice you want for each reminder.

Members can subscribe for reminders on an individual event screen. They can also personalize their reminder settings, including removing reminders or having multiple reminders at different times.

Members can also subscribe for notifications to specific event types to be notified whenever events under those types are scheduled.
Question How can I schedule Commandr commands to run automatically?
Answer To schedule commands, create an event with the "System command" event type. This option needs to be enabled in the configuration first. In the event details, you can specify either a URL for Composr to call or a snippet of Commandr code to execute. Be sure to disable the WYSIWYG editor for this type of event. You'll also need to have the system scheduler configured for the commands to run automatically.
Question Can I add external feeds to the calendar?
Answer Yes, you can add RSS or Atom feeds to your calendar. This lets you view time-based information from external sources alongside your calendar events.
Question What do I do if a recurring event needs to be changed or skipped?
Answer Composr has a "fixing an event" feature to handle changes to recurring events. This is useful if an event needs to be cancelled or rescheduled. You edit the event as if it were a new, standalone event and choose the "Edit with fixing past recurrences" option. This separates the past occurrences from the modified event, ensuring future recurrences reflect the changes.
Question What is the "recurrence pattern" and how does it work?
Answer The recurrence pattern is a powerful tool that defines how often an event repeats. While it might seem complex at first, it provides a lot of flexibility. Think of it as a binary code where each digit represents a time period (like a day or week). A "1" indicates the event occurs, and a "0" means it doesn't. This lets you create complex schedules like "every weekday" (daily with pattern 1111100 if it starts on a Monday) or "every other Tuesday" (weekly on Tuesday with the pattern 10).
Question What are the different views available in the calendar?
Answer The calendar has five views:
  • Year view: Displays an overview of the entire year.
  • Month view: Shows events within a specific month.
  • Week view: Displays events for a selected week.
  • Day view: Shows events scheduled for a specific day.
  • Event view: Displays the details of a single event.

You can easily navigate between these views to get different levels of detail and focus on specific periods or events.
Question How do I add events to the calendar?
Answer You can add events in several ways:
  • Through the Admin Zone or Content Management Zone: Go to Admin Zone > Content > Calendar.
  • Directly on the calendar: Click on a date box on the calendar view.
  • Using the "Add Event" button on any calendar view.

Deleting events can be done at the bottom of the event's edit form. You have options for recurring events, such as editing/deleting the specific occurrence, editing/deleting future ones, or all of them.
Question How do I categorize events?
Answer You categorize events using "Event types". Composr provides default types like "Anniversary", "Appointment", "Birthday", "General", "Public Holiday", "Task", "Vacation", and the special "System command" for executing Commandr commands. You can also add your own custom event types to suit your specific needs, such as "Appraisal Session" for a business website.
Question What is an "event" in the Composr calendar system?
Answer An event is any entry in the calendar. Importantly, an event isn't limited to a single point or range in time. Events can recur based on a schedule you define. This makes them very flexible – they can represent anything from one-time appointments to recurring birthdays or even weekly team practices.

Top 10 Entries

Question What is Tempcode, and how is it used in website themeing?
Answer Tempcode is a templating language used within Composr. It offers a powerful way to control the output of dynamic content and design elements on a website. It works by using:
  • Parameters: Placeholders for content passed to the template from Composr / PHP.
  • Symbols: Global functions that perform operations, calculations, or retrieve information.
  • Directives: Instructions that control the flow or logic of content, such as conditional statements and loops.
  • Language strings: References to pre-defined text stored in language files for easy translation.
  • Escaping: Ensures the content generated is properly escaped according to its use case.

Tempcode empowers theme designers to create highly customizable and dynamic websites, allowing for logic, conditional rendering, and manipulation of various website elements.
Question What are some alternatives to Photoshop for web design?
Answer While Photoshop is a popular choice, there are other excellent options available, including:
  • GIMP/GIMPShop: These free, open-source image editors provide a robust set of features comparable to Photoshop.
  • Paint.NET: This free, Windows-only software offers a user-friendly interface and essential image editing tools.
  • Corel Paint Shop Pro: A more affordable alternative to Photoshop, Corel Paint Shop Pro delivers a good balance of features and ease of use.
Question How can design elements like dominance and attention to detail improve a website?
Answer Dominance and attention to detail are key to a balanced and engaging website. Important elements can be emphasized using techniques like larger text, unique colors, and increased spacing. Conversely, less crucial elements should receive less emphasis. This interplay helps guide the visitor's eye and ensures a visually harmonious layout.

Attention to detail involves eliminating inconsistencies and distractions, such as typos, misaligned elements, and low-quality images, that can detract from the overall aesthetics and message of the website.
Question What is the importance of color schemes in website design?
Answer Color schemes are crucial as they convey emotions and brand identity. Choosing colors that align with your website's purpose can evoke desired feelings in visitors. For example, a website selling chocolates might use shades of brown to subconsciously trigger associations with chocolate. However, an environmental website would be better suited using green, aligning with pre-existing perceptions of environmentalism.

It is also important to maintain consistency with your color scheme, limiting the number of colors used to avoid a conflicting and cluttered appearance.
Question Can I use Comcode / resource IDs directly when working with the repository?
Answer Using Comcode / resource IDs directly is not recommended as they may not match between different sites. Use GUIDs instead, which Composr automatically substitutes for IDs before parsing Comcode. You can use Commandr commands like find_guid_via_id to find the GUID for specific resources.
Question What precautions should I take when using the Composr Repository?
Answer Exercise caution when working with the repository:
  • Avoid using it as the sole backup method; rely on regular database backups.
  • Work primarily under the "var" meta-filesystem and copy specific folders/files rather than the entire repository.
  • Do not use tools like "rsync" or Git on the whole repository without careful consideration.
Question What are the limitations of the Composr Repository?
Answer While powerful, the repository has limitations:
  • Automatic syndication is not performed for content added via the repository.
  • Multi-language content translations are not retained.
  • Transferring complex data schemas between staging sites may have limitations.
  • Merging separate websites into one is not supported through the repository. You should use Composr's import tool instead.
Question How can I access the Composr Repository?
Answer You can access the repository using WebDAV (non-bundled addon), which allows you to view it as a folder on your computer. Composr uses the SabreDAV PHP library for WebDAV functionality. However, please be aware that SabreDAV is deprecated and may not function correctly on newer PHP versions.
Question How is the Composr Repository structured?
Answer The repository is structured as a filesystem with various meta-filesystems mounted under a root directory. These meta-filesystems include:
  • bin: Stores Commandr scripts.
  • database: Provides access to the raw database.
  • etc: Allows access to Composr configuration options.
  • home or filedump: Provides access to the File/Media Library.
    • home contains the files in a special JSON format with metadata
    • filedump contains the raw files
  • members: Lists registered members with their settings and user groups.
  • raw or root: Provides access to the Composr installation directory.
    • raw contains the raw files without overrides, and modifying any file modifies them directly without automatic override handling
    • root contains the files with applicable overrides applied automatically, and Composr will automatically handle overrides and utilizing _custom directories when these files are modified
  • var: Contains structured website resources and content.
Question What are the benefits of using the Composr Repository?
Answer The repository offers several benefits:
  • Opacity: Provides a clear view of Composr's content and resource data.
  • Tactility: Allows easy manipulation of data through drag-and-drop operations.
  • Data transfer: Simplifies transferring data between sites.
  • Desktop application integration: Enables using text editors and file-search tools for tasks like mass search and replace.
  • Configuration management: Tracks changes to options and facilitates transfer between sites.
  • Backups: Allows backing up portions of the repository.
  • Revision control: Supports built-in and advanced revision control.
  • Filesystem for Commandr: Acts as a file system for the Commandr command line.
  • Resource API: Offers an abstract resource API for programmers.
  • API for external apps: Provides an API for mobile apps and other external applications.