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

Statistics

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