Contributors: A-Z Index

A

Name	Photograph	Title / Role	Contributions / Notes
Allen Ellis		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		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		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		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 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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

Statistics

Forum statistics:	45 topics, 14 posts, 2 members Our newest member is test