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

View

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.

View

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.

View

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.

View

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.

View

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.

View

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.

View

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.

View

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.

View

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.

View

Top 10 Entries

Question What web technologies does Composr use beyond HTML, CSS, and JavaScript?
Answer Composr relies on a wide range of web technologies (depending on what features and settings you use), including:
  • Protocols: HTTP/HTTPS, FTP, SFTP, SMTP, IMAP, POP3, DNS, and others
  • Data formats: XML, JSON, CSV, PHP's serialized format, iCalendar, and various image and archive formats
  • Standards: Accessibility standards (WCAG, WAI-ARIA), metadata standards (Open Graph, schema.org, Dublin Core), and microformats
  • Server-side technologies: PHP, SQL (for database interaction)
  • Composr-specific technologies: Tempcode (template system), Comcode (content language), Page-links, Filtercode, Selectcode, and Language packs

View

Question How does Composr ensure printed web pages look appropriate?
Answer Composr uses a combination of approaches to ensure printed web pages have a suitable layout:
  • Automatic browser behavior: Browsers typically disable background images when printing.
  • CSS print stylesheets: Composr utilizes CSS to define specific display rules for printed versions of pages, such as removing margins and hiding social media links.
  • wide_print parameter: This parameter, activated through specific links or specifying it in the URL, further influences page layout for printing.

View

Question How can I test my website's compatibility across different browsers and devices?
Answer Testing your website on different browsers and devices can be challenging due to operating system limitations and device availability. Here are some solutions:
  • Virtual Machines: Use virtual machines to run different operating systems and test various Internet Explorer versions.
  • Device Emulation: Use built-in device emulation features in browsers like Chrome to simulate mobile devices.
  • Online Testing Services: Employ commercial online testing services like BrowserStack to access a wide range of browsers and devices hosted in the cloud.
  • Real Devices: Conduct testing on physical mobile devices for a more realistic user experience.

View

Question What are the recommended desktop settings for viewing a Composr website?
Answer A minimum screen resolution of 1024x768 is strongly recommended for viewing a Composr website. This is the minimum resolution for which the default theme is designed. Using a lower resolution might lead to display issues or an unsatisfactory browsing experience. As of version 11, smaller resolutions will often trigger the mobile layout automatically (responsiveness) to ensure a better UI for smaller displays.

View

Question How does Composr handle browser compatibility?
Answer Composr aims to support all modern browsers, including the latest versions of Chrome, Firefox, Safari, Edge, and Internet Explorer 11. It is designed to work seamlessly with browsers that automatically update, like Chrome and Firefox. For browsers with manual updates, Composr generally supports the last two releases.

While not explicitly supported, Composr will often address bug reports for other popular browsers like Opera, Chromium, and Konqueror. Additionally, Composr strives to provide an accessible experience for text-mode browsers and those designed for users with disabilities.

View

Question What is CSS and how does it impact website design?
Answer CSS (Cascading Style Sheets) is a language used to describe the visual presentation of a web page written in HTML or XHTML. It controls aspects like:
  • Fonts and typography: Defining font families, sizes, weights, and styles.
  • Colors and backgrounds: Setting colors for text, backgrounds, borders, and other elements.
  • Layout and positioning: Controlling the placement and arrangement of elements on a page.
  • Visual effects: Adding shadows, gradients, transitions, and other visual enhancements.

By separating content structure (XHTML) from visual presentation (CSS), websites become easier to maintain and update. Changes to the design can be made without altering the underlying HTML structure.

Composr utilizes CSS extensively for theming, allowing users to manipulate the website's visual appearance.

View

Question Why is understanding XHTML important for website customization?
Answer XHTML (Extensible HyperText Markup Language) is the language used to structure web page content. It defines the various elements of a webpage, such as headings, paragraphs, images, and links.

Understanding XHTML is crucial for website customization because it allows you to:
  • Modify page layout: Change the arrangement and positioning of elements on a page.
  • Add new content: Insert additional text, images, or other multimedia elements.
  • Customize the appearance of existing elements: Change fonts, colors, sizes, and other visual styles.
  • Integrate interactive features: Embed JavaScript code for dynamic functionality.

Composr uses XHTML for its templates, allowing users to extensively customize the website's design and layout.

View

Question How does JavaScript enhance website interactivity?
Answer JavaScript is a programming language that runs in web browsers, allowing for dynamic and interactive elements on web pages. It enables features like:
  • Dynamic content updates: Modifying page content without requiring a full page reload.
  • User interface enhancements: Creating interactive elements like dropdown menus, image sliders, and form validation.
  • Animations and visual effects: Adding visual appeal and engaging user experiences.
  • Asynchronous communication: Fetching data from, or sending data to, servers in the background without disrupting user interaction.

Composr relies on JavaScript for its default theme and administrative features.

View

Question What is the difference between cookies and sessions?
Answer While both cookies and sessions are used for user identification and maintaining state, there are key differences:
  • Storage: Cookies are stored on the user's computer, while sessions are stored on the server.
  • Expiration: Session cookies expire when the browser is closed, while persistent cookies have a set expiration date. Sessions typically expire after a period of inactivity.
  • Data sensitivity: Sessions are generally used for more sensitive data, as the information is not stored on the user's computer and therefore less likely to be stolen by a hacker.

Composr uses both cookies and sessions. Session cookies are primarily used for user identification (such as anonymously matching a user to a session in the server database), while persistent cookies can be used for remembering login details if the user chooses.

View

Question What are cookies and how do they work?
Answer A cookie is a small piece of data that a website stores on a user's computer. It is sent from the user's web browser to the web server each time a page is viewed. Cookies are used for various purposes, including:
  • User identification: Cookies can be used to identify a specific user, even if they are not logged in. This allows websites to remember user preferences, shopping cart contents, and other information.
  • Tracking user behavior: Cookies can be used to track user behavior on a website, such as the pages they visit and the links they click. This information can be used to improve the website's design and content.
  • Advertising: Cookies can be used to deliver targeted advertising to users based on their browsing history.

There are two main types of cookies:
  • Session cookies: These cookies are temporary and are deleted when the user closes their web browser. They are often used to store information about the user's current session, such as the items in their shopping cart.
  • Persistent cookies: These cookies are stored on the user's computer for a longer period. They can be used to remember user preferences, such as their login details or language settings.

View